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

start

Skill4 starsChanged 6 days agoMITView on GitHub

First-time entry point. Asks what you want to model, detects project stage, and routes you to the right workflow.

137 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-engine, team-audio and 9 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.
  • CoralGameSkill

    setup-engine

    Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.

    Also in 13 projects that use this

  • CoralGameSkill

    team-audio

    Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.

    Also in 13 projects that use this

  • 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 11 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 11 projects that use this

  • +4 more from CoralGame
  • +3 more from lilangMax

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 124 edited versions we read keep these.

  • 1

    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:

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

    line 26
  2. Very specific:

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

    line 28
  3. Very specific:

    If the user brings a note, plan, objective or brief, recommend /research-plan first

    line 39
  4. Very specific:

    If the user brings code to move to another language or software, recommend /translate-code (or /code-inventory to look first)

    line 40
  5. Distinctive:

    Ask the model size class (small, medium, large), the audience and the deadline

    line 41
  6. Very specific:

    Run /project-stage-detect logic to see what already exists

    line 42
  7. Very specific:

    Write the choice to production/session-state/active.md

    line 45

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

/start — Start

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

First-time entry point. Asks what you want to model, detects project stage, and routes you to the right workflow.

Arguments: whatever the user wrote after the command name.

Purpose

Be the first stop for a new user: find out what they want to achieve (answer a question, build a model, produce a forecast, validate a model or adopt an existing one), the size of the work, the audience and the deadline, check what already exists, and recommend the first three skills with reasons. Nothing is written until the user chooses.

Use it when a user opens the studio for the first time or starts a new piece of work.

Do not use it when the user already knows which skill to run.

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • production/stage.txt (optional)
    • studio-config.yaml 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
  • economic-reasoning-specialist — Frames the economic question and tests whether results make economic sense
  • modeling-methodology-specialist — Chooses methods and architecture across model families, sets code and data standards, and resolves technical trade-offs between traditional, structural and AI approaches

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Workflow

  1. Greet the user and ask what they are trying to achieve: a question to answer, a model to build, a forecast to produce, a model to validate, an existing model to adopt, code to translate to another language, or a research note, plan or objective (in any form, with or without data) to turn into modeling work
    • If the user brings a note, plan, objective or brief, recommend /research-plan first
    • If the user brings code to move to another language or software, recommend /translate-code (or /code-inventory to look first)
  2. Ask the model size class (small, medium, large), the audience and the deadline
  3. Run /project-stage-detect logic to see what already exists
  4. Recommend the first three skills to run, with reasons, and wait for the user's choice
    • Mention existing lego sets that could be reused or extended
  5. Write the choice to production/session-state/active.md

Common pitfalls

  • Recommending a large model for an urgent, narrow question
  • Ignoring existing work in the project

Output

production/session-state/active.md

The session-state file records the user's goal, size class, audience, deadline and chosen path.

Gate / verdict

  • The user has chosen a path; nothing is written before the user agrees
  • Recommendations are explained with reasons

Suggested next steps

  • /scope-question
  • /research-plan
  • /adopt
  • /translate-code
  • /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.