agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/help/SKILL.md

help

Skill4 starsChanged 6 days agoMITView on GitHub

Explains what the studio can do, lists skills and agents by category, and suggests what to do next based on project stage.

82 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

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 27
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 29
  3. Distinctive:

    If a skill or agent name is given, read its file and explain it in plain language with an example

    line 35

“Common” is measured: kept by at least 6 in 10 of the 63 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
<!-- Generated from .claude/skills/help/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/help — Help

Category: Onboarding · Primary agent: project-planning-specialist

Explains what the studio can do, lists skills and agents by category, and suggests what to do next based on project stage.

Arguments: whatever the user wrote after the command name.

Purpose

Explain what the studio can do: what a given skill or agent does, which skills fit the project's current stage, which specialists cover which areas, and what to do next. Every answer is based on the actual files in the studio, not on memory.

Use it when a user is unsure which skill or agent to use, or wants an overview.

Do not use it when the user already knows the workflow they want (/start routes new users).

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • .claude/skills/
    • .claude/agents/
    • production/stage.txt (optional) If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • project-planning-specialist — primary agent; coordinates the work and integrates results

Workflow

  1. If a skill or agent name is given, read its file and explain it in plain language with an example
  2. Otherwise detect the project stage and list the skills available at this stage
  3. Show the map of areas of expertise and the agents in each
    • Include the lego skills for working with models as plug-and-play sets
  4. Recommend next steps

Common pitfalls

  • Describing skills that do not exist
  • Overwhelming new users with the full list

Output

(conversation only)

The answer is given in the conversation, with references to the files it draws on.

Gate / verdict

  • The answer cites actual files; nothing is invented
  • Recommendations fit the detected stage

Suggested next steps

  • /start
  • /project-stage-detect

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.