New Skill
I cannot write a factual description of this Claude Code item because the definition provided is a template outline rather than completed content. The skill name, purpose, inputs, outputs, and all substantive details remain unfilled. To produce an accurate description, the template would need to be populated with the skill's actual name, functionality, use cases, and technical specifications.
git clone --depth 1 https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook /tmp/new-skill && cp -r /tmp/new-skill/.github/ISSUE_TEMPLATE/new_ ~/.claude/skills/new-skillnew_skill.md
## Skill name (kebab-case) ## When to use (be specific) ## When NOT to use ## Inputs / outputs (high level) ## References you'd include - references/... ## Risk - Tools called: ... - Risk level of those tools: ... - Approval gates needed: ... ## Walked checklist - [ ] [skill_quality_checklist](../../checklists/skill_quality_checklist.md) - [ ] [skills/security_checklist](../../skills/security_checklist.md)
Use when capturing an architecture decision so it survives turnover — produces an ADR-NNNN.md from context, options considered, and the chosen path.
Use when reviewing a proposed REST or GraphQL API change before merge — checks contract clarity, backwards compatibility, errors, pagination, auth, and naming.
Use when first encountering a new dataset — produces a structured profile (schema, missingness, distributions, outliers, gotchas) before any analysis.
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.
Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.
Use before connecting a new MCP server to your agent — produces a structured security review covering source, permissions, tools, network, and approvals.