Claude Skill

reflect

Session retrospective and skill audit. Use when "/reflect", "session review", "retrospective", "what went wrong", "lessons learned", "what should we remember", or "what can we improve".

LLM Mart · 0 points · 8 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download iliaal-whetstone-distillery_generated-skills_reflect-bccd699.zip · 1 KB
Part of iliaal/whetstone — 62 skills

Install

skills CLI npx skills add https://github.com/iliaal/whetstone/tree/master/distillery/generated-skills/reflect
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install iliaal-whetstone@llmmart
Git git clone https://github.com/iliaal/whetstone.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole iliaal/whetstone collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Reflect

Success Criteria

  • Every mistake/friction point cites the specific moment and its impact
  • Improvements are actionable, prioritized, and <= 10 items
  • Each skill audit proposes measurable changes (not vague suggestions)
  • User is asked which items to persist to memory

Process

1. Session Review

Scan the full conversation. For each finding, cite the specific exchange (quote or paraphrase) and its impact.

Category Signal
Mistakes Wrong outputs, incorrect assumptions, hallucinated facts
Friction Repeated clarifications, verbose responses, misread intent
Wasted effort Work discarded, wrong approaches tried first
Wins Approaches worth repeating, smooth interactions

Skip one-time typos, external tool failures, and issues outside agent control.

2. Improvements

Numbered list of concrete improvements, ranked by impact. Each item: one sentence, imperative, actionable. Cap at 10.

Ask: "Which of these should I remember for future chats?"

Save approved items to memory files via the auto memory system.

3. Skill Audit (if skills were used)

For each skill invoked during the session:

A. Self-check gate — If the skill lacks success criteria + verification loop:

  • Add ## Success Criteria at top (3-5 measurable checks)
  • Add ## Self-Check at bottom: "Verify all success criteria are met before presenting output. If not, iterate (max 5 times)."

B. Token efficiency — Flag: redundant phrasing, mergeable sections, oversized examples, "Claude already knows this" content, inert frontmatter metadata.

C. Other — Missing edge cases, vague directives (rewrite as measurable criteria or remove), naked negations (add "do Y instead" or remove).

Present proposed changes as diffs. Ask: "Apply these? (all / pick / skip)"

4. Pattern Detection

If 2+ similar tasks appear that no existing skill covers, suggest a new skill (1-2 sentence description). Create only after confirmation.

Proactive Trigger

When the user corrects you, clarifies the same thing twice, or shows frustration — append:

Tip: Type /reflect when you're ready — I'll review what we can improve.

Self-Check

Before presenting output, verify all success criteria are met. If any fail, revise (max 5 iterations).

Files (whetstone)
  • manifest.json 736 B
    {
      "query": "session retrospective / reflect",
      "search_queries": [
        "reflect session review",
        "retrospective improvements",
        "self-review mistakes",
        "continuous improvement learning"
      ],
      "generated": "2026-02-16",
      "token_count": 754,
      "sources": [
        {
          "id": "softaworks/agent-toolkit/feedback-mastery",
          "installs": 1812,
          "sha1": "190c02b6c7ae2483c3437f7623aca57b958b2677"
        },
        {
          "id": "affaan-m/everything-claude-code/continuous-learning",
          "installs": 493,
          "sha1": "19464da8fe8ff6d7dd1a8dc17e3ae680f9e4c5a5"
        },
        {
          "id": "sickn33/antigravity-awesome-skills/kaizen",
          "installs": 223,
          "sha1": "963605d3881c9f85f33dcbb05d9c2ec3a610d59b"
        }
      ]
    }
  • SKILL.md 2.5 KB
    ---
    name: reflect
    description: >-
      Session retrospective and skill audit. Use when "/reflect", "session review",
      "retrospective", "what went wrong", "lessons learned", "what should we
      remember", or "what can we improve".
    ---
    
    # Reflect
    
    ## Success Criteria
    
    - Every mistake/friction point cites the specific moment and its impact
    - Improvements are actionable, prioritized, and <= 10 items
    - Each skill audit proposes measurable changes (not vague suggestions)
    - User is asked which items to persist to memory
    
    ## Process
    
    ### 1. Session Review
    
    Scan the full conversation. For each finding, cite the specific exchange (quote or paraphrase) and its impact.
    
    | Category | Signal |
    |----------|--------|
    | **Mistakes** | Wrong outputs, incorrect assumptions, hallucinated facts |
    | **Friction** | Repeated clarifications, verbose responses, misread intent |
    | **Wasted effort** | Work discarded, wrong approaches tried first |
    | **Wins** | Approaches worth repeating, smooth interactions |
    
    Skip one-time typos, external tool failures, and issues outside agent control.
    
    ### 2. Improvements
    
    Numbered list of **concrete improvements**, ranked by impact. Each item: one sentence, imperative, actionable. Cap at 10.
    
    Ask: *"Which of these should I remember for future chats?"*
    
    Save approved items to memory files via the auto memory system.
    
    ### 3. Skill Audit (if skills were used)
    
    For each skill invoked during the session:
    
    **A. Self-check gate** — If the skill lacks success criteria + verification loop:
    - Add `## Success Criteria` at top (3-5 measurable checks)
    - Add `## Self-Check` at bottom: "Verify all success criteria are met before presenting output. If not, iterate (max 5 times)."
    
    **B. Token efficiency** — Flag: redundant phrasing, mergeable sections, oversized examples, "Claude already knows this" content, inert frontmatter metadata.
    
    **C. Other** — Missing edge cases, vague directives (rewrite as measurable criteria or remove), naked negations (add "do Y instead" or remove).
    
    Present proposed changes as diffs. Ask: *"Apply these? (all / pick / skip)"*
    
    ### 4. Pattern Detection
    
    If 2+ similar tasks appear that no existing skill covers, suggest a new skill (1-2 sentence description). Create only after confirmation.
    
    ## Proactive Trigger
    
    When the user corrects you, clarifies the same thing twice, or shows frustration — append:
    
    > Tip: Type `/reflect` when you're ready — I'll review what we can improve.
    
    ## Self-Check
    
    Before presenting output, verify all success criteria are met. If any fail, revise (max 5 iterations).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related