Weekly Reflectron

Guide a weekly reflection across Work, Health, Relationships, and Growth, then turn the review into one clear pattern plus Stop, Start, Continue, and one exp...

Security Scan

The skill's code and instructions are coherent with its stated purpose: a local, rules-based weekly reflection generator that reads only its own SKILL.md and the user's provided text, with no external network access or credential requirements.

Purpose & Capability

The name/description match the implementation. The handler implements a four-dimension weekly review, pattern detection, and Stop/Start/Continue/experiment outputs as described. It does not request unrelated platform access (no env vars, no binaries, no config paths).

Instruction Scope

SKILL.md instructs a purely descriptive reflection and explicitly says it does not sync calendars/devices. The code follows that scope: it only reads the SKILL.md file locally and processes the provided input text. There is a minor wording choice in DEFAULT_EVIDENCE/README lines that say 'pull one concrete example from memory' — implementation returns placeholder prompts for missing inputs rather than attempting any external retrieval, which is consistent with the non-networked design.

Install Mechanism

This is an instruction-only / small local Python skill with no install spec. No packages are fetched or executed from external URLs. No archive extraction or unusual installation behavior is present.

Credentials

The skill requires no environment variables, credentials, or config paths. It does not access system credentials or other skills' configuration.

Persistence & Privilege

The skill is not marked always:true and does not modify other skills or system-wide settings. It runs deterministically on the supplied input and returns text; it does not persist state or store credentials.

Assessment

This skill appears coherent and self-contained: it only processes text you provide and reads its own SKILL.md. Before installing, consider: (1) Review the handler.py locally (you already have it) and run the included tests to verify behavior. (2) Avoid pasting extremely sensitive personal data into the skill because whatever you submit will be echoed/transformed in the output. (3) Remember it's rule-based and may misclassify nuance — treat its suggestions as prompts, not clinical advice. If you want networked integrations (calendar, fitness, task apps), those are explicitly not implemented and would require additional, separate permissions.

Overview

Use this skill to review a week through four life dimensions instead of collapsing everything into work stress or generic self-judgment. It helps the user gather evidence first, spot one cross-cutting pattern, and convert insight into a small adjustment for the next week.

This skill is descriptive only. It does not sync calendars, task apps, fitness devices, or journals.

Trigger

Use this skill when the user wants to:

• do a weekly review that covers more than work
• capture wins and friction with concrete evidence
• reduce vague, harsh, or repetitive reflection
• produce Stop, Start, Continue actions for the coming week
• end a review with one experiment instead of a total reinvention

Example prompts

• "Help me do a weekly reflection without turning it into self-criticism"
• "Give me a five minute weekly review for work, health, relationships, and growth"
• "Turn this messy week into a useful reflection"
• "I want a weekly reset with one clear experiment for next week"

Workflow

1. Review the week through Work, Health, Relationships, and Growth.
2. Gather evidence first, including wins, slips, habits, and emotional highs or lows.
3. Label each dimension with a simple status.
4. Notice one pattern that touched multiple parts of the week.
5. Convert the pattern into one Stop, one Start, and one Continue action.
6. End with one experiment for next week.

Inputs

The user can provide any mix of:

• freeform notes about the week
• work progress or unfinished loops
• sleep, food, movement, or energy notes
• family, partner, or friendship moments
• learning, reading, journaling, or growth notes
• overall mood or stress level
• explicit weekly wins and friction points

Outputs

Return a markdown reflection with:

• snapshot of the week
• four-dimension review
• one pattern noticed
• Stop, Start, Continue, and one experiment for next week

Safety

• Use concrete evidence when available, not abstract self-judgment.
• During crisis or overload weeks, optimize for stabilization before ambition.
• Balance wins and friction. Do not turn the review into a problem-only narrative.
• Do not claim psychological certainty from limited notes.

Acceptance Criteria

• Return markdown text.
• Cover Work, Health, Relationships, and Growth.
• Include at least one actionable next-week adjustment.
• Keep the reflection concrete, balanced, and usable.