agentleFS
starter-seriesstarter-series/create-starter/skills/create/SKILL.md

create

Skill2 starsChanged 2 months agoMITView on GitHub

Scaffold a new project from the Starter Series templates (MCP server, Discord/Telegram bot, VS Code / browser extension, Electron, React Native, Cloudflare Pages, npm package, Docker deploy).

  • Reads credentials

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use compare, publish and 3 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.
  • n24q02mSkill

    compare

    Structured comparison of 2+ alternatives with consistent criteria and decision matrix

    Also in 3 projects that use this

  • VercelSkill

    publish

    Publish a single demo to v0 and optionally create Typefully drafts. Use when the user says "publish", "publish to v0", or "create typefully draft" for a demo.

    Also in 4 projects that use this

  • genomewalkerSkill

    tasks

    Browse and resume tasks, threads, and background jobs across sessions

    Also in 3 projects that use this

  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 3 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 3 projects that use this

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 17 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:

    Pick a template: If the user named one explicitly, resolve it against the registry below.

    line 17
  2. Very specific:

    Call list_templates for the authoritative, up-to-date list with full metadata.

    line 36
  3. Very specific:

    Never invent template IDs.

    line 40
  4. Very specific:

    Never construct tarball URLs or shell commands yourself — always go through create_project.

    line 41
  5. Very specific:

    If the tool returns an isError: true response, surface the message verbatim and stop.

    line 42
  6. Very specific:

    After a successful scaffold, suggest reviewing .env.example if the output mentions environment variables, and remind the user that git init …

    line 43
  7. Distinctive:

    Keep your response concise: one line confirming the template + name, then the next-step commands as a code block.

    line 44

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

You are scaffolding a new project using the Starter Series templates via the create-starter MCP server.

How to invoke

The create-starter MCP server exposes two tools. Use them directly — do not shell out to curl, tar, or git clone.

  • list_templates — returns the full template table as JSON.
  • create_project — scaffolds a new project.

Workflow

  1. Pick a template. If the user named one explicitly, resolve it against the registry below. If not, call list_templates and ask the user to pick one.
  2. Collect required input:
    • name (required) — project name. Must match ^[A-Za-z0-9][A-Za-z0-9_-]*$ (alnum start, then [A-Za-z0-9_-] only). No dots, no spaces, no path separators.
    • description (optional) — one-line description that replaces the template default.
    • output_dir (optional) — where to create the project. Defaults to ./<name> relative to the MCP server's cwd.
  3. Call create_project with the gathered arguments. The server handles download, extraction, placeholder substitution, Python package renaming, and git init.
  4. Report the next steps from the tool's response (it returns a cd-then-install sequence tuned to the template).

Template registry

IDNameCategory
mcp-serverMCP Server (TypeScript)mcp
mcp-server-pythonMCP Server (Python)mcp
npm-packagenpm Packagepackage
browser-extensionBrowser Extension (MV3)extension
vscode-extensionVS Code Extensionextension
docker-deployDocker Deploy (language-agnostic)deploy

Call list_templates for the authoritative, up-to-date list with full metadata.

Rules

  • Never invent template IDs. Only use IDs returned by list_templates or present in the table above.
  • Never construct tarball URLs or shell commands yourself — always go through create_project.
  • If the tool returns an isError: true response, surface the message verbatim and stop; do not retry with a different name unless the user asks.
  • After a successful scaffold, suggest reviewing .env.example if the output mentions environment variables, and remind the user that git init has already run — they just need to add a remote.
  • Keep your response concise: one line confirming the template + name, then the next-step commands as a code block.

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.