Use when running or operating the Autoloop orchestration runtime, including starting new loops, resuming tasks, phase-scoped runs, troubleshooting stuck-looking runs, and interpreting run artifacts. Do not use for unrelated coding tasks.
Track multi-session work with beads_rust (br) issue tracker, including creating/updating/closing issues, managing dependencies, syncing JSONL/DB, configuring prefixes, and migrating bd workflows to br. Use when a project uses .beads/ with br or when converting bd instructions to br.
Review and resolve PR comments from GitHub. Validates each comment, fixes legitimate issues.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", "disallowedTools", "block tools", "agent denylist", "maxTurns", "agent memory", "mcpServers in agent", "agent hooks", "background agent", "resume agent", "agent teams", "permission rules", "permission mode", "delegate mode", "agent team", "team lead", "teammate", "multi-agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
Use when 需要分析小说站点并生成 Legado 书源，且要先判断登录、评估可生成性、对照官方规则与辅助文档，再输出可验证的书源结果
**sgrep** is a semantic and hybrid code search tool that understands what you mean, not just what you type.
Router skill for all MCS-MCP chart visualizations. Trigger this skill whenever any mcs-mcp analysis tool result is present in the conversation and the user asks to visualize, chart, plot, or show it. This router maps the tool that produced the result to the correct chart sub-skill. Do NOT attempt to build any chart ad-hoc — always read the sub-skill first. --- # MCS Charts Router This is the sole entry point for all MCS-MCP chart skills. When a chart request arrives, identify which analysis tool produced the data, then read and follow the matching sub-skill before writing any code. --- ## Step 1 — Identify the data source Look at the conversation for the most recent mcs-mcp tool result. Match it to one of the tools in the routing table below. --- ## Step 2 — Routing Table ``` Tool that produced the data Sub-skill path (relative to this file) ──────────────────────────────── ────────────────────────────────────────────── analyze_process_stability analyze_process_stability/s.md analyze_throughput analyze_throughput/s.md analyze_wip_stability analyze_wip_stability/s.md analyze_wip_age_stability analyze_wip_age_stability/s.md analyze_work_item_age analyze_work_item_age/s.md analyze_process_evolution analyze_process_evolution/s.md analyze_residence_time analyze_residence_time/s.md generate_cfd_data generate_cfd_data/s.md analyze_cycle_time analyze_cycle_time/s.md analyze_status_persistence analyze_status_persistence/s.md analyze_flow_debt analyze_flow_debt/s.md analyze_yield analyze_yield/s.md forecast_monte_carlo forecast_monte_carlo/s.md forecast_backtest forecast_backtest/s.md ``` Sub-folder names match the exact tool name as registered in the MCP server. --- ## Step 3 — Read the sub-skill, then build Use the `view` tool to read the matched
Routes Snowflake-related operations to Cortex Code CLI for specialized Snowflake expertise. Use when user asks about Snowflake databases, data warehouses, SQL queries on Snowflake, Cortex AI features, Snowpark, dynamic tables, data governance in Snowflake, Snowflake security, or mentions "Cortex" explicitly. Do NOT use for general programming, local file operations, non-Snowflake databases, web development, or infrastructure tasks unrelated to Snowflake.
>-
This skill should be used when the user asks about "AI security", "ML pipeline attacks", "prompt injection", "model deserialization", "unsafe model loading", "Jupyter injection", "LLM security", or needs to identify AI/ML-specific vulnerabilities in codebases that use machine learning frameworks.
Review and improve Kensa BDD tests written in Kotlin. Use this skill whenever the user shares a Kensa test file, asks you to review or improve a Kensa test, or mentions Given-When-Then tests in a Kensa project. Kensa tests use the KensaTest interface with given()/whenever()/then() DSL, @RenderedValue, @ExpandableSentence, Fixtures, and produce HTML reports with sequence diagrams.
Build a daily digest from curated sources. Follow the output contract strictly.
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:
