Agent skill

A short, stable skill that teaches agents to assemble Pegma packages instead of regenerating sessions, identity, rate limits, mail, and audit. Package inventories and versions live incatalog.json — not in the skill.

Canonical raw markdown (copy or fetch):https://pegma.dev/skill.md

Install notes

There is no single universal skill registry. Use whichever path your tool supports; the document is plain markdown.

Project rules / skills directory

Copy the skill into the project agent directory under a name your tool expects (examples: .grok/skills/pegma/SKILL.md,.claude/skills/pegma/SKILL.md, .agents/skills/pegma/SKILL.md, or a project AGENTS.md / rules file that points at the same text).

mkdir -p .grok/skills/pegma
curl -fsSL https://pegma.dev/skill.md -o .grok/skills/pegma/SKILL.md
# or
mkdir -p .claude/skills/pegma
curl -fsSL https://pegma.dev/skill.md -o .claude/skills/pegma/SKILL.md

Many tools treat a directory containing SKILL.md (with YAML frontmatter) as an installable skill. Keep the frontmatter; do not strip it.

Paste into system / custom instructions

Open skill.md, copy the body into the agent’s custom instructions or project rules. Prefer linking the catalog URL so the agent re-fetches facts instead of caching versions in the prompt.

Plugin / marketplace wrappers

If your environment uses a plugin that only differs by install path, wrap this same markdown. Do not fork package facts into the wrapper — point athttps://pegma.dev/catalog.json.

Optional MCP surface

A thin public MCP server exposes the same catalog over Streamable HTTP. Tools return catalog facts only — no private data plane, no auth for reads. Endpoint: https://pegma.dev/api/mcp

Tools: list_components, get_component,list_recipes, get_recipe,plan_composition (rule-based over structuredcapabilityTags — not an LLM).

MCP config snippet

{
  "mcpServers": {
    "pegma": {
      "url": "https://pegma.dev/api/mcp"
    }
  }
}

Clients without native remote MCP can use a local proxy, for examplenpx mcp-remote https://pegma.dev/api/mcp. Prefer re-calling tools over caching package versions.

What the skill teaches

Assembly over generation
Explicit composition root; pin exact 0.x versions from the catalog
Refusals as hard constraints
Lookup: catalog → component → green recipe → fixture source
Prove with types and tests

Related:catalog.json ·examples ·llms.txt ·stack ·MCP