agentleFS
Jason-hub-starJason-hub-star/model-orchestrator/skills/agent-starter/SKILL.md

agent-starter

Skill0 starsChanged 2 months agoMITView on GitHub

Guide people who are new to coding agents through the next appropriate workflow stage, or help experienced users select and remix the included morning, aim, decision-sheet, converge, goal, phase-loop, audit, absorb, and harness-audit skills. Use for “what should I do next?”, “help me start with agents”, “에이전트 처음”, or “뭐부터 하지?”.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Treat runtime behavior and direct measurements as stronger evidence than old documentation.

    line 25
  2. Distinctive:

    Read the nearest project instructions and current status before editing.

    line 26
  3. Distinctive:

    Search for existing code, standard features, dependencies, and installed skills before creating anything.

    line 27
  4. Distinctive:

    Use the lowest effort that can close the task reliably.

    line 28
  5. Distinctive:

    Never treat an empty result as proof that nothing exists.

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Agent Starter

Choose one next stage. Do not run the whole chain by default.

Route

  1. Beginning a work session with existing repository history → morning-brief.
  2. A desired outcome exists, but current implementation status is unclear → aim-before-build.
  3. The target is still fuzzy and several decisions are open → decision-sheet.
  4. A costly or hard-to-reverse plan is still uncertain → converge-plan.
  5. Work needs multiple turns and an evidence-based finish line → goal-contract.
  6. An approved plan has three or more implementation phases → phase-loop.
  7. Work is ready to review or share → evidence-audit.
  8. Too many skills, or a skill never triggers → harness-audit; an external source to evaluate → absorb.

Simple questions and one-line edits need none of these. Handle them directly.

Shared habits

  • Treat runtime behavior and direct measurements as stronger evidence than old documentation.
  • Read the nearest project instructions and current status before editing.
  • Search for existing code, standard features, dependencies, and installed skills before creating anything.
  • Use the lowest effort that can close the task reliably.
  • Delegate only independent, bounded work; keep one writer unless paths are disjoint.
  • Never treat an empty result as proof that nothing exists.
  • Finish non-trivial work with one runnable check and an explicit remaining-risk statement.

Output

Return the selected stage, why it fits, the first artifact or check to inspect, and one next action.

Next

Hand off to the selected stage and stop; the chain continues from that stage's own ## Next.

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.