Scaffold a new capability primer under docs/primers/ and add the capability to the repo README taxonomy.
Scanned 8/30/2026
Install to Claude Code
npx -y skills add microsoft-foundry/model-releases --skill add-capability-doc --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Add Capability Doc?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/microsoft-foundry-add-capability-doc)More formats (shields.io, HTML) on the badges page.
---
kind: skill
name: add-capability-doc
description: Scaffold a new capability primer under docs/primers/ and add the capability to the repo README taxonomy.
inputs:
- name: capability
type: string
description: Canonical capability name (added to the taxonomy).
required: true
- name: slug
type: string
description: Kebab-case slug used as the filename and anchor.
required: true
- name: one_line
type: string
description: Short pitch used in the taxonomy table.
required: true
- name: learn_more
type: array
description: Up to 3 grounding resources (Learn URLs preferred).
required: true
produces:
- docs/primers/<slug>.md
- README.md
validates_against:
- .github/specs/schemas/primer.schema.json
depends_on: []
---
# add-capability-doc
Creates a new primer file with frontmatter validated by
[`primer.schema.json`](../../specs/schemas/primer.schema.json), and
appends a row to the **Capability taxonomy** table in the repo README.
Also updates the [`capsule.schema.json`](../../specs/schemas/capsule.schema.json)
`capabilities` enum so future capsules can tag themselves with the new
capability. (Author confirms this schema change explicitly.)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.