Map task types to the best agent, skill, model, and fallback. Route any task to the right tool. Use when: which agent, route task, agent for this, best agent, capability matrix.
Use when a Plan has a task breakdown and is ready for implementation. Dispatches subagent per task with review between tasks.
Intelligent task management via the `task` CLI. Invoke when users ask to: create/list/update/delete tasks, search tasks (text or semantic), track work items with due dates, organize tasks into projects, run batch operations, generate activity reports, or manage recurring tasks. Supports natural language dates and Google Calendar sync.
Proactively reminds Claude Code users about relevant available tools whenever a task could benefit from them. ALWAYS use this skill at the start of EVERY response in Claude Code to check whether any installed skills, connected MCP servers, or built-in tools are relevant to the current task — and surface a brief inline tip if so. Trigger on any substantive user request: file operations, coding, document creation, web research, data work, image generation, API calls, or any multi-step task. Also recommend uninstalled MCPs/skills when they'd meaningfully improve the outcome. Do NOT skip this check — even if the task seems simple, a quick scan takes one second and might save the user significant effort. --- # Tool Advisor Skill Helps users get the most out of their Claude Code environment by surfacing relevant tools at the right moment — briefly and without interrupting flow. ## Your Job At the start of handling any substantive task, do a quick mental scan: 1. **Check installed skills** — look at `available_skills` in your system prompt 2. **Check connected MCPs** — look at MCP server list in your context 3. **Check built-in tools** — bash, file read/write, web search, image gen, etc. 4. **Consider uninstalled tools** — if a well-known MCP or skill would meaningfully help, mention it If anything relevant is found that **isn't already being used**, prepend a 💡 tip to your response. --- ## When to Tip Tip when there's a **specific, actionable match** between the task and a tool the user may not be thinking of. Do NOT tip for every response — only when it adds value. | Task type | Potentially relevant tools to check | |---|---| | Creating/editing Word docs | \`docx\` skill | | Working with PDFs | \`pdf\` skill, \`pdf-reading\` skill | | Building presentations | \`pptx\` skill | | Spreadsheet / data work | \`xlsx\` skill | | Reading uploaded files | \`file-reading\` skill | | Web research / current events | \`web_search\` tool, browser MCP | | Code execution / scripting | \
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:
