Is capture-mcp-context-70e65d safe to install?

SaferSkills independently audited capture-mcp-context-70e65d (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.agents/skills/capture-mcp-context/SKILL.md · 1 file

.agents/skills/capture-mcp-context/SKILL.md2.0 KB · Markdown

name: capture-mcp-context

description:

"Record durable context from MCP servers and design or project tools into repository memory as

proposed. Use when working with an MCP server like Figma, Linear, Jira, or Sentry, or after

pulling design, ticket, or error context, to persist it for future sessions."

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 create when 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>.md does not exist, create it with persist 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.

capture-mcp-context-70e65d— agent skill

Is capture-mcp-context-70e65d safe to install?

Skill: Capture MCP Context

Purpose

Inputs

Required Reading

Output Files

Process

Stop Conditions

Quality Bar

Audit the pieces. Scan the whole. Decide.