agentleFS
Sign inStart free
agamaroraagamarora/second-brain/.claude/skills/help/SKILL.md

help

Skill2 starsChanged 7 months agoMITView on GitHub

List all available skills with one-line descriptions. Use when the user asks "what can this brain do", "what skills are there", "list commands", or /help.

76 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files 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.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 9 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 57 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep output ≤ 40 lines total

    line 54
  2. Distinctive:

    Do not paginate or ask questions — just print

    line 55
  3. Distinctive:

    If a skill exists on disk but isn't in the groups above, append it under "OTHER"

    line 56
  4. Distinctive:

    If a skill from the groups above is missing on disk, omit its row silently

    line 57

“Common” is measured: kept by at least 6 in 10 of the 57 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Print the skill catalog. Short, scannable.

Steps

  1. Glob .claude/skills/*/SKILL.md
  2. For each, read the name: + description: from the frontmatter (first 10 lines is enough)
  3. Print the table below, sorted by suggested-workflow order

Output format

Second brain — available skills

SESSION
  /orient              Session-start briefing
  /help                This command

WRITE PATH
  /capture <text>      Drop a thought into inbox/ — no triage
  /ingest <path>       Process a source into the wiki with 3-layer provenance
  /new-page <kind>     Create a new entity or concept page

READ PATH
  /query "<question>"  Ask the brain — synthesized answer with citations

SUBSKILLS  (called by /ingest, rarely directly)
  /extract-entities    Scan a source, return entity list
  /absorb <ent> <src>  Write source reference into a wiki page

SYNC
  /quick-sync          Session end — process inbox, log decisions, commit
  /deep-sync           Weekly — /quick-sync + drift check + snapshot

MAINTENANCE
  /lint                Find orphans, broken links, stale claims, contradictions
  /publish-context     Export a read-only snapshot for cross-session use

IN-CONVERSATION SHORTCUTS (no slash needed)
  "capture this"       → runs /capture
  "log this decision"  → writes decisions/<date>-<slug>.md directly
  "ingest this"        → runs /ingest on the last-mentioned source

Type any command above. See individual .claude/skills/<name>/SKILL.md for details.

Rules

  • Keep output ≤ 40 lines total
  • Do not paginate or ask questions — just print
  • If a skill exists on disk but isn't in the groups above, append it under "OTHER"
  • If a skill from the groups above is missing on disk, omit its row silently

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free