aiskillstore/marketplace / skills/2025emma/claude-skills
claude-skills
VerifiedClaude Skills meta-skill: extract domain material (docs/APIs/code/specs) into a reusable Skill (SKILL.md + references/scripts/assets), and refactor existing Skills for clarity, activation reliability, and quality gates.
| File | Kind | Size |
|---|---|---|
| AGENTS.md | markdown | 1.9 KB |
| SKILL.md | skill md | 7.9 KB |
| assets/template-complete.md | markdown | 2.4 KB |
| assets/template-minimal.md | markdown | 926 B |
| references/README.md | markdown | 7.5 KB |
| references/anti-patterns.md | markdown | 3.0 KB |
| references/index.md | markdown | 1.3 KB |
| references/quality-checklist.md | markdown | 1.9 KB |
| references/skill-spec.md | markdown | 3.4 KB |
| scripts/create-skill.sh | script | 4.1 KB |
| scripts/validate-skill.sh | script | 5.4 KB |
| skill-report.json | config | 35.2 KB |
references/skill-spec.md
View on GitHubTRANSLATED CONTENT:
# Skill Spec (This Repo)
This document defines what a "production-grade Skill" means in this repository. Use it as the source of truth when creating or refactoring anything under `skills/`.
Keywords: MUST / SHOULD / MAY / MUST NOT / SHOULD NOT are normative.
## 1. Directory & Naming
- A Skill MUST be a directory under `skills/` named after its `name` field.
- The directory name MUST match `^[a-z][a-z0-9-]*$`.
- The Skill entrypoint MUST be `SKILL.md` at the root of the skill directory.
## 2. Frontmatter (Required)
`SKILL.md` MUST start with YAML frontmatter:
```yaml
---
name: skill-name
description: "What it does + when to use (activation triggers)."
---
```
Rules:
- `name` MUST match `^[a-z][a-z0-9-]*$`.
- `name` SHOULD equal the directory name.
- `description` MUST be decidable and operational:
- Good: "X development and debugging. Use when doing A/B/C."
- Bad: "Helps with X."
## 3. SKILL.md Structure
### 3.1 Required Sections
`SKILL.md` SHOULD follow this section order, and in strict mode it MUST:
1. `## When to Use This Skill`
2. `## Not For / Boundaries`
3. `## Quick Reference`
4. `## Examples`
5. `## References`
6. `## Maintenance`
Rationale:
- Activation reliability depends on explicit triggers and boundaries.
- Usability depends on short patterns and reproducible examples.
- Maintainability depends on sources and navigable references.
### 3.2 Quick Reference Rules
- Quick Reference MUST contain short, directly usable patterns.
- Quick Reference MUST NOT become a documentation dump.
- Long explanations SHOULD go to `references/`.
- A good target is <= 20 patterns, but large domains may justify more.
### 3.3 Example Rules
- The Examples section MUST contain reproducible examples.
- Each example SHOULD specify:
- input(s)
- steps
- expected output / acceptance criteria
- Pseudo-code MAY be used only if the platform is unavailable, and MUST be clearly labeled.
### 3.4 Boundaries Rules
- "Not For / Boundaries" MUST list:
- explicit out-of-scope items (to prevent misfires)
- required inputs and what to ask when missing (1-3 questions)
## 4. references/ (Long-form Docs)
- `references/` SHOULD exist when the domain has:
- long docs
- many edge cases
- extensive APIs/CLIs/config surfaces
- If `references/` exists, it SHOULD include:
- `references/index.md` as a navigation entrypoint
Guideline:
- `references/` is for evidence, depth, and navigation.
- `SKILL.md` is for execution: short patterns + examples + constraints.
## 5. scripts/ and assets/
- `scripts/` MAY contain helper automation (generators, validators, setup).
- Scripts MUST be non-interactive by default.
- Scripts MUST NOT require network access unless explicitly stated.
- `assets/` MAY contain templates, configs, or static resources.
## 6. Safety & Integrity
- Skills MUST NOT include secrets (API keys, tokens, credentials).
- Skills MUST NOT invent external facts.
- If uncertain, they MUST include a verification path (where/how to check).
- Potentially destructive commands MUST be explicitly labeled and gated.
## 7. Maintenance Metadata
Each Skill SHOULD include a `## Maintenance` section with:
- sources (docs/repos/specs)
- last-updated date
- known limits / non-goals
## 8. Quality Gate
Before shipping, run the checklist in `quality-checklist.md` and (if available) the validator:
```bash
./skills/claude-skills/scripts/validate-skill.sh skills/<skill-name> --strict
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |