- 📄 BEST_PRACTICES.md
- 📄 SKILL.md
- 📄 WORKFLOWS.md
semi-design-guide
使用 Semi Design 组件的完整指南,包括 MCP 工具使用流程、常见模式、最佳实践。当你需要查询 Semi Design 组件、生成组件代码或解决使用问题时,请使用此技能。
使用 Semi Design 组件的完整指南,包括 MCP 工具使用流程、常见模式、最佳实践。当你需要查询 Semi Design 组件、生成组件代码或解决使用问题时,请使用此技能。
Use when a workflow has repeated or should become permanent capability. Capture the workflow candidate first, ask for user confirmation before creating a new skill, and then scaffold the draft skill into the global Claude skills directory.
Opinionated JSDoc conventions for TypeScript SDK codebases. Use when: (1) Writing or reviewing JSDoc on public API exports, (2) Cleaning up over-documented code, (3) Auditing documentation for internal leakage, (4) Writing JSDoc for types, interfaces, and classes, (5) Deciding whether a function needs JSDoc at all. Principle: JSDoc should add value, not restate what TypeScript already shows.
>-
Evaluate and address a GitHub pull request review locally. Use when a PR review contains inline comments, suggestions, or requested changes that need to be implemented in the local workspace. Covers fetching review threads, triaging by severity, applying code fixes, running tests, and optionally replying to or resolving review threads.
Use this skill when the user says 'API integration', 'connect APIs', 'sync data', 'data mapping', 'rate limiting', or needs system-to-system connectors with authentication, rate limit handling, and error recovery. Generates API integration code with authentication (OAuth, API key, JWT), request/response mapping, rate limit handling, error recovery with circuit breakers, and sync monitoring. Do NOT use for visual n8n workflows or webhook receiving.
Agentforce session tracing extraction and analysis.
This skill should be used when understanding code structure, finding
Organizes repository documentation and keeps new docs in the correct location.
AWP (Agent Working Protocol) on-chain tooling skill. Provides contract addresses, API endpoints, bundled Python scripts, and EIP-712 signing for interacting with the AWP protocol across Base, Ethereum, Arbitrum, and BSC. Covers: staking (veAWP deposits, allocations), worknet management (register, pause, resume, cancel), governance (propose, vote), gasless relay operations (bind, unbind, delegate, allocate), and real-time WebSocket event monitoring. Load this skill when the user mentions AWP, Agent Working Protocol, awp-wallet, veAWP, AWPWorkNet, worknet staking, AWP governance, AWP emissions, or wants to perform any AWP on-chain operation. NOT for: Uniswap, Aave, Lido, Compound, or other DeFi protocols unrelated to AWP.
Content Analyzer — any content (URL, text, transcript) into structured analysis report with actionable insights. Use when user asks to analyze, summarize, or extract key takeaways from content.
LLM-compiled knowledge base manager. Activates when user works with wiki directories, mentions knowledge base management, asks knowledge questions in a project with a wiki, wants to ingest/compile/query/lint knowledge, or uses /wiki commands. Also activates when user says "wiki", "knowledge base", "ingest", "compile wiki", "add to wiki", "search wiki", "librarian", "scan quality", "article quality", "content review", or asks a factual question in a directory containing .wiki/ or when ~/wiki/ exists or the configured hub path exists (check ~/.config/llm-wiki/config.json for hub_path).
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: