在临时目录中用 uvx 或 uv tool run 安装 specify-cn 的 main 分支最新提交，对源码声明支持的 agent 执行 init，并校验版本、中文化、模板完整性、agent 文件落点与 ai-skills 安装结果。用于本地发布后验收。
Skill do Product Owner para especificação de features. Use quando precisar definir requisitos de negócio, escrever user stories, critérios de aceitação, priorização de backlog, ou qualquer documento de especificação de produto. Trigger em: "nova feature", "especificação", "user story", "requisito", "backlog", "PO", "definir escopo", "critério de aceitação", "MVP", "roadmap". --- # Product Owner - Especificação de Features O PO é o guardião do valor de negócio. Toda feature nova começa aqui. ## Governanca Global Esta skill segue `GLOBAL.md`, `policies/execution.md`, `policies/handoffs.md`, `policies/token-efficiency.md` e `policies/evals.md`. Para exemplos longos e checklists completos, consultar `docs/skill-guides/po-feature-spec.md` apenas quando necessario. ## Quando Usar - definir feature nova, escopo e prioridade - transformar necessidade de negocio em criterios testaveis ## Quando Nao Usar - para decidir implementacao tecnica detalhada - para substituir UI/UX, Backend, QA ou Reviewer ## Entradas Esperadas - objetivo de negocio - restricoes e dependencias conhecidas - contexto do usuario ou da operacao ## Saidas Esperadas - spec curta e acionavel - criterios de aceitacao testaveis - handoff claro para UI/UX e pipeline seguinte ## Responsabilidades 1. Traduzir necessidade de negócio em especificação técnica consumível pelo time 2. Definir prioridade e impacto 3. Escrever critérios de aceitação claros e testáveis 4. Validar que a entrega final atende o esperado ## Estrutura Minima da Feature Spec Toda nova feature deve cobrir, no minimo: - resumo do problema e da solucao proposta - user stories com criterios de aceitacao testaveis - regras de negocio e dependencias - escopo `IN` e `OUT` - prioridade e metricas de sucesso Para spec completa e exemplos extensos, consultar `docs/skill-guides/po-feature-spec.md`. ## Critérios de Aceitação - Boas Práticas Critérios de aceitação devem ser: - **Específicos**: sem ambiguidade - **Mensuráveis**: pode ser verificado como ve
skill-sample/ ├─ SKILL.md ⭐ Required: skill entry doc (purpose / usage / examples / deps) ├─ manifest.sample.json ⭐ Recommended: machine-readable metadata (index / validation / autofill) ├─ LICENSE.sample ⭐ Recommended: license & scope (open source / restriction / commercial) ├─ scripts/ │ └─ example-run.py ✅ Runnable example script for quick verification ├─ assets/ │ ├─ example-formatting-guide.md 🧩 Output conventions: layout / structure / style │ └─ example-template.tex 🧩 Templates: quickly generate standardized output └─ references/ 🧩 Knowledge base: methods / guides / best practices ├─ example-ref-structure.md 🧩 Structure reference ├─ example-ref-analysis.md 🧩 Analysis reference └─ example-ref-visuals.md 🧩 Visual reference
More Agent Skills specs Anthropic docs: https://agentskills.io/home
├─ ⭐ Required: YAML Frontmatter (must be at top) │ ├─ ⭐ name : unique skill name, follow naming convention │ └─ ⭐ description : include trigger keywords for matching │ ├─ ✅ Optional: Frontmatter extension fields │ ├─ ✅ license : license identifier │ ├─ ✅ compatibility : runtime constraints when needed │ ├─ ✅ metadata : key-value fields (author/version/source_url...) │ └─ 🧩 allowed-tools : tool whitelist (experimental) │ └─ ✅ Recommended: Markdown body (progressive disclosure) ├─ ✅ Overview / Purpose ├─ ✅ When to use ├─ ✅ Step-by-step ├─ ✅ Inputs / Outputs ├─ ✅ Examples ├─ 🧩 Files & References ├─ 🧩 Edge cases ├─ 🧩 Troubleshooting └─ 🧩 Safety notes
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Quick Start:
Import/download skills (.zip/.skill), then place locally:
~/.claude/skills/ (Claude Code)
~/.codex/skills/ (Codex CLI)
One SKILL.md can be reused across tools.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.
Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.
Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.
This keeps agents lightweight while preserving enough context for complex tasks.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused across tools.
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
