We split this skill into the rules it gives an agent

11 rules. 0 are common, 5 are distinctive, and 6 are very specific to this project.

• 0

  Common

  Most of the 49 edited versions we read keep these.

• 5

  Distinctive

  This author's own choices. Worth a look.

• 6

  Very specific

  Tied to their project's names, files or tools. Probably skip.

• Common
• Distinctive
• Very specific

1. Very specific:

   Search .lifecycle/plans/ for progress files with incomplete tasks ([ ] or [~])

   line 13
2. Distinctive:

   If multiple found: list with last-modified timestamps, ask user to select

   line 15
3. Very specific:

   If none found: "No in-progress plans found.

   line 16
4. Very specific:

   Look for .lifecycle/checkpoints/[feature]-checkpoint.md.

   line 28
5. Very specific:

   Read .lifecycle/activity.md if it exists.

   line 39
6. Very specific:

   Read .lifecycle/lessons/[relevant topics].md for applicable lessons.

   line 52
7. Distinctive:

   Read plan file ONLY for the next incomplete task's details

   line 56
8. Distinctive:

   Update progress as tasks complete — one line per task, no prose

   line 58
9. Distinctive:

   Do NOT ask between tasks — execute to completion

   line 59
10. Very specific:

    If context limit approaching: run /checkpoint, commit, /compact, resume

    line 60
11. Distinctive:

    If something goes sideways: STOP and re-plan

    line 61

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

• Other versions56 projects use a version of this.

  Word for word · 0

  None found.

  Edited · 0

  None found.

  Wrote their own version · 56

  1. H-mmer/pentest-agents★ 815same name
  2. bitwize-music-studio/claude-ai-music-skills★ 589same name
  3. EmeaAppGbb/spec2cloud★ 100same name
  4. thiagofinch/mega-brain★ 95same name
  5. thesun4sky/jobstack★ 50same name
  6. junjiezhou1122/ideascientist-claude-code★ 35same name
  7. nimadorostkar/Claude-Skills-collection★ 33same name
  8. wrg32786/aigent-os★ 25same name
  9. saksham10arora-dotcom/everything-claude-codex★ 24same name
  10. Hassaan146/claude-skills★ 18same name

  46 more not listed

  How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

• Used alongsideProjects with it also use pause, status and 10 more.

  Other files people use alongside this one.

  How we pick theseFiles found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 14 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 7 projects that use this

  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • MicrosoftSkill

    note

    Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.

    Also in 3 projects that use this

  • GitHubSkill

    state-management

    CoreAI Sandbox's TanStack Query + mock-JSON data layer. USE WHEN: editing data-fetching hooks (`app/hooks/use*.ts`), adding mock data in `app/data/`, or wiring a component to query state.

    Also in 3 projects that use this

  • +2 more from microsoft
• In this repository6 other files it gives its agents.

  • alignSkill
  • checkpointSkill
  • initSkill
  • planSkill
  • recoverSkill
  • reflectSkill