Habit Stack Designer

Design a habit stack by choosing a reliable existing anchor, shrinking the new habit into a tiny first action, and adding friction reduction, reward, and a r...

Security Scan

The skill's code and instructions are consistent with its stated purpose (producing tiny habit-stack designs), request no credentials or external installs, and perform only local, deterministic text processing.

Purpose & Capability

The name/description, SKILL.md, and handler.py all align: the skill analyzes a user-provided habit description and returns a habit-stack design. It doesn't request unrelated credentials, binaries, or config paths. The included rule lists and templates are appropriate for generating the described outputs.

Instruction Scope

SKILL.md explicitly states the skill is descriptive only and does not create reminders or external automation. The runtime code only normalizes input, extracts keywords, and renders a markdown output. It reads its bundled SKILL.md (local file) for metadata but does not read other system files, environment variables, or transmit data externally.

Install Mechanism

There is no install spec; the skill is instruction/code-only and does not download or install third-party packages or binaries. No extract/download URLs or package registry installs are present.

Credentials

The skill requires no environment variables, credentials, or config paths. All data is derived from the provided input string and internal templates, so requested privileges are proportional to the functionality.

Persistence & Privilege

always is false and the skill does not request persistent system presence or modify other skills. disable-model-invocation is false (normal), but that is not combined with other risky behaviors here.

Assessment

This skill appears coherent and low-risk: it only analyzes text and emits a markdown habit-stack design, and it does not request credentials or access external endpoints. If you plan to enable autonomous invocation for agents generally, be aware the platform could call the skill without each explicit prompt (the skill itself is harmless). If you have strong operational security requirements, you can review the small handler.py (it only uses local templates and keyword matching) or run it in a sandbox before enabling it for production agents. Avoid sending highly sensitive personal data in free-form inputs (unnecessary for a habit design).

Overview

Use this skill to attach a new habit to an existing routine instead of hoping motivation will carry it. It helps the user find a stable anchor, make the first action tiny enough to start, and design friction removal plus a rescue version for bad days.

This skill is descriptive only. It does not create reminders or automation.

Trigger

Use this skill when the user wants to:

• build a new habit that actually sticks
• choose a strong anchor habit instead of relying on memory
• shrink a habit into a tiny under-two-minute version
• create an explicit habit stack formula
• add a rescue version for low-energy days

Example prompts

• "Help me stack a meditation habit onto something I already do"
• "Design a tiny reading habit after dinner"
• "I keep forgetting my new habit, can you attach it to a stable routine?"
• "Turn this big habit goal into a stack formula"

Workflow

1. Identify the target habit and why it matters.
2. Find an existing routine that already happens predictably.
3. Evaluate whether the anchor is frequent and reliable.
4. Shrink the new habit into a tiny first action.
5. Write the habit stack formula.
6. Add friction reduction, reward, and a rescue version.
7. Scale only after consistency exists.

Inputs

The user can provide any mix of:

• target habit
• reason or identity behind the habit
• daily routines that already happen
• time or place cues
• schedule constraints
• prior failure patterns
• desired reward or review rhythm

Outputs

Return a markdown habit stack design with:

• target habit and why it matters
• best anchor and why it is reliable
• explicit stack formula
• friction removal ideas
• reward loop
• rescue version for hard days

Safety

• Prefer anchors the user already performs several times per week.
• Start tiny enough to avoid negotiation.
• Avoid stacking many new behaviors onto one weak anchor.
• Irregular schedules may need place-based anchors rather than clock-based ones.

Acceptance Criteria

• Return markdown text.
• Include a clear anchor and explicit stack formula sentence.
• Keep the starting action tiny and realistic.
• Include both friction removal and a rescue version.