adr-writer
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered,…
Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.
$ npx -y skills add oxbshw/LLM-Agents-Ecosystem-Handbook --skill mcp-security-reviewer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/mcp-security-reviewerContext preview
The summary Claude sees to decide when to auto-load this skill.
Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.
name: mcp-security-reviewer description: Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals. version: 0.1.0
| Name | Type | Required | Notes | |---|---|---|---| | `repo_url` | string | yes | the MCP server's source | | `version` | string | yes | tag or commit SHA being adopted | | `intended_use` | string | yes | one paragraph: what we'll let it do |
1. **Source review**: clone at the pinned version; check for unexpected files / scripts 2. **Capabilities**: list every tool and resource exposed; map to risk levels (`references/mcp-risk-matrix.md`) 3. **Network**: identify outbound endpoints; document and assess each 4. **Permissions**: minimum required scopes / tokens; document over-permissions 5. **Output handling**: confirm the agent treats tool output as untrusted (sanitization, no execution) 6. **Approvals**: define which tools require human approval 7. **Produce filled `MCP_SERVER.md`** in `mcp/<server>.md`
A practical operating manual for building, evaluating, securing, and shipping modern LLM agent systems. Modern agents are not "a prompt + a tool."
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered,…
Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors,…
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas)…
Use after an incident is resolved — drafts a blameless postmortem from timeline notes, alerts, and chat threads.
Use when opening a PR — produces a clean PR description (what / why / how to verify / risks) from a branch diff against base.
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.