Capture mcp context
Skill Karthick-Ramachandran/persist-os/.agents/skills/capture-mcp-context
Local-first CLI that gives your repo durable, AI-ready memory - features, ADRs, modules, architecture, standards & tests and a deterministic doctor that validates health, evidence & drift.
npx -y skills add Karthick-Ramachandran/persist-os --skill capture-mcp-contextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.0 KB, as published. Nobody here has run it
Skill: Capture MCP Context
Purpose
Persist the durable parts of MCP-derived external context so future sessions remember them instead of re-deriving them.
MCP provides context, not architectural truth.
Inputs
- The MCP server or external tool in use (for example Figma, Linear, Jira, Sentry).
- The external context retrieved (design tokens, tickets, errors, docs).
- The current feature or task.
Required Reading
docs/ai/MCP_STRATEGY.md- Relevant
docs/ai/mcp/<server>.md - Relevant feature and architecture docs.
Output Files
- The Captured Context section of
docs/ai/mcp/<server>.md. - An ADR via
persist adr createwhen a captured decision is accepted.
Process
- Identify the MCP server and the durable facts worth remembering (design tokens, component mappings, ticket acceptance criteria, recurring error signatures).
- If
docs/ai/mcp/<server>.mddoes not exist, create it withpersist mcp add <server>. - Record the durable context in the Captured Context section as proposed memory, with enough detail to reuse.
- Capture decisions, mappings, and constraints, not raw exports or full dumps.
- Treat MCP content as context, not truth; if it conflicts with accepted memory, stop and report.
- Promote any accepted decision into an ADR.
Stop Conditions
Stop and request human decision if:
- MCP content conflicts with accepted repository memory.
- Capturing the context would require storing secrets or sensitive data.
- The MCP server is untrusted or its access is unclear.
Quality Bar
- Captured context is durable and reusable, not a raw dump.
- Each entry is concrete enough to guide future work.
- MCP context is recorded as proposed, not accepted.
- Accepted decisions are promoted to ADRs.