agentleFS
purpleeddypurpleeddy/cladding/skills/serve/SKILL.md

serve

Skill16 starsChanged 4 months agoMITView on GitHub

Boot cladding as an MCP server over stdio. Use only when the user wants to expose cladding's tools, resources, and persona prompts to a separate MCP client. Most users don't run this directly — the plugin's .mcp.json launches it automatically. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized projects.

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Run clad serve from the project root.

    line 7

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

Cladding serve

Run clad serve from the project root. Boots an MCP server over stdio that exposes:

  • Tools: the full development surface (feature/graph/context queries, checks, gate, changelog) plus the natural-language onboarding flow — clad_prepare_init / clad_stage_init / clad_init and the clarify pair. Before spec.yaml exists only the three onboarding bootstrap tools are exposed.
  • Resources: cladding://spec, cladding://events, cladding://audit.
  • Prompts: 5 personas (orchestrator, planner, reviewer, observability, developer).
  • Live audit notifications: notifications/resources/updated fires for cladding://audit whenever a new evidence entry lands — a subscribed client can live-tail the audit log without polling.

Registers itself in cladding's sampling context so the host adapters (generic-mcp, claude-code) route LLM dispatch through McpSamplingTransport instead of the Mock fallback.

clad serve --cwd /path/to/project

Most users don't run this directly. Cladding's plugin manifest (.mcp.json) launches clad serve automatically when the plugin is enabled. Invoke this skill only for debugging the MCP server in isolation.

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.