Manage activities on YouTube. Use this skill to list channel activities. Useful when working with YouTube activity — provides commands to list activity via the yutu CLI. Includes setup and installation instructions for first-time users. Triggers: list activities, list activity, list my activity
Manage Zotero library - list collections, list papers, add papers to collections. Requires ZOTERO_API_KEY env var.
Controls and monitors ROS 2 robots directly via rclpy CLI. Use for ANY ROS 2 robot task: topics (subscribe, publish, capture images, find by type), services (list, call), actions (list, send goals), parameters (get, set, presets), nodes, lifecycle management, controllers (ros2_control), diagnostics, battery, system health checks, and more. When in doubt, use this skill — it covers the full ROS 2 operation surface. Never tell the user you cannot do something ROS 2-related without checking this skill first.
React Native and Expo best practices for building performant mobile apps. Use when reviewing React Native code, designing component architecture, implementing features, optimizing list performance, implementing animations, working with native modules, checking for performance issues, auditing UI components, reviewing state management, or checking production readiness. Triggers on "review best practices", "check performance", "optimize renders", "review list rendering", "check animation patterns", "review state management", "audit UI", "check for crashes", "review for production readiness", "check React Native conventions", "performance audit". --- # React Native Best Practice Rules 36 rules from [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) (MIT License) plus 3 rn-dev-agent rules discovered through story testing. Each rule has full incorrect/correct code examples in `references/<rule-name>.md`. --- ## Rule Index Scan this table first. Load the corresponding reference file for any rule category present in the code under review. | ID | Rule | Impact | Reference File | |----|------|--------|----------------| | 1.1 | Never use `&&` with potentially falsy values | CRITICAL | `references/rendering-no-falsy-and.md` | | 1.2 | Wrap strings in `<Text>` components | CRITICAL | `references/rendering-text-in-text.md` | | 2.1 | Avoid inline objects in renderItem | HIGH | `references/list-perf-inline-objects.md` | | 2.2 | Hoist callbacks to the root of lists | HIGH | `references/list-performance-callbacks.md` | | 2.3 | Keep list items lightweight | HIGH | `references/list-perf-expensive-item.md` | | 2.4 | Stable object references before lists | CRITICAL | `references/list-perf-fn-refs.md` | | 2.5 | Pass primitives to list items for memoization | HIGH | `references/list-performance-item-memo.md` | | 2.6 | Use a list virtualizer for any list | HIGH | `references/list-performance-virtualize.md` | | 2.7 | Use compressed images in lists | HIGH | `references/li
React Native and Expo best practices for building performant mobile apps. Use when reviewing React Native code, designing component architecture, implementing features, optimizing list performance, implementing animations, working with native modules, checking for performance issues, auditing UI components, reviewing state management, or checking production readiness. Triggers on "review best practices", "check performance", "optimize renders", "review list rendering", "check animation patterns", "review state management", "audit UI", "check for crashes", "review for production readiness", "check React Native conventions", "performance audit". --- # React Native Best Practice Rules 36 rules from [vercel-labs/agent-skills](https://github.com/vercel-labs/agent-skills) (MIT License) plus 3 rn-dev-agent rules discovered through story testing. Each rule has full incorrect/correct code examples in `references/<rule-name>.md`. --- ## Rule Index Scan this table first. Load the corresponding reference file for any rule category present in the code under review. | ID | Rule | Impact | Reference File | |----|------|--------|----------------| | 1.1 | Never use `&&` with potentially falsy values | CRITICAL | `references/rendering-no-falsy-and.md` | | 1.2 | Wrap strings in `<Text>` components | CRITICAL | `references/rendering-text-in-text-component.md` | | 2.1 | Avoid inline objects in renderItem | HIGH | `references/list-performance-inline-objects.md` | | 2.2 | Hoist callbacks to the root of lists | HIGH | `references/list-performance-callbacks.md` | | 2.3 | Keep list items lightweight | HIGH | `references/list-performance-item-expensive.md` | | 2.4 | Stable object references before lists | CRITICAL | `references/list-performance-function-references.md` | | 2.5 | Pass primitives to list items for memoization | HIGH | `references/list-performance-item-memo.md` | | 2.6 | Use a list virtualizer for any list | HIGH | `references/list-performance-virtualize.md` | | 2.7 | Use compres
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:
