- 📄 SKILL.md
auto-pr-merge
Create PR, wait for checks, fix issues iteratively, and merge with --admin
6 days ago · Uploaded
Detail →
Daily Featured Skills Count
04/05
04/06
04/07
04/08
04/09
04/10
04/11
♾️ Free & Open Source 🛡️ Secure & Worry-Free
Import Skills
- 📄 SKILL.md
weather-checker
A simple weather checking skill that fetches current weather data.
10 days ago · Uploaded
Detail →
- 📁 onboarding-boilerplate/
- 📁 onboarding-prompts/
- 📁 references/
- 📄 context.fixtures.json
- 📄 context.ts
- 📄 README.md
checkly
Set up, create, test and manage monitoring checks using the Checkly CLI. Use when working with API Checks, Browser Checks, URL Monitors, ICMP Monitors, Playwright Check Suites, Heartbeat Monitors, Alert Channels, Dashboards, or Status Pages.
10 days ago · Uploaded
Detail →
- 📁 references/
- 📄 __init__.py
- 📄 SKILL.md
rdc-cli
Use this skill when working with RenderDoc capture files (.rdc), analyzing GPU frames, tracing shaders, inspecting draw calls, or running CI assertions against GPU captures.
10 days ago · Uploaded
Detail →
- 📁 references/
- 📄 SKILL.md
check-pr
Checks a GitHub or GitLab pull request (or merge request) for unresolved review comments, failing status checks, and incomplete PR descriptions. Waits for pending checks to complete, categorizes issues as actionable or informational, and optionally fixes and resolves them. Use when the user wants to check a PR/MR, address review feedback, or prepare a PR for merge.
7 days ago · Uploaded
Detail →
- 📁 .claude-plugin/
- 📁 .github/
- 📁 benchmark/
- 📄 .gitignore
- 📄 .mcp.json
- 📄 .npmignore
mem
Use when: querying past work, managing memories, checking project history, or saving session findings
11 days ago · Uploaded
Detail →
- 📁 references/
- 📄 SKILL.md
tsarr
Manage home media services through TsArr from OpenClaw. Use for Radarr, Sonarr, Lidarr, Readarr, Prowlarr, and Bazarr tasks such as checking health, inspecting queues and history, browsing libraries, searching, adding, editing, deleting items, viewing profiles, tags, and root folders, and checking TsArr configuration.
11 days ago · Uploaded
Detail →
- 📄 SKILL.md
claude-code-setup
Runs shell script quality checks. Use when checking shell script quality, linting bash code, or validating scripts. Covers formatting with shfmt, static analysis with shellcheck, and portability checks.
11 days ago · Uploaded
Detail →
- 📁 examples/
- 📄 reference.md
- 📄 SKILL.md
gg
Use git-gud (gg) to manage stacked diffs with GitHub PRs or GitLab MRs. Use this when creating stacks, syncing updates, checking CI/review state, and landing approved work safely.
11 days ago · Uploaded
Detail →
- 📁 agents/
- 📄 SKILL.md
renderdoc-mcp
Analyze RenderDoc GPU frame captures with renderdoc-mcp MCP tools. Use when Codex needs to inspect .rdc captures, diagnose black screens or visual artifacts, explain frame structure, inspect specific draw calls, or investigate GPU rendering and performance issues.
10 days ago · Uploaded
Detail →
- 📄 SKILL.md
chrome-devtools-cli
Uses the chrome-mcp-cli command-line tool to control Chrome DevTools from the terminal. Use when the user wants browser automation, page inspection, screenshots, network inspection, console inspection, or performance tracing through the CLI instead of MCP tools.
11 days ago · Uploaded
Detail →
- 📁 references/
- 📄 .gitignore
- 📄 README.md
- 📄 SKILL.md
enter
Use this skill to operate enter.pro through the verified enter-cli workflow. Trigger when the user wants to create, inspect, iterate on, publish, remix, or share an Enter project; inspect thread turns, messages, diffs, domains, workspace members, or project URLs; or recover from Enter CLI / API drift. Do not use for the local enter_agent_sdk or general local code execution.
7 days ago · Uploaded
Detail →
Skill File Structure Sample (Reference)
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
SKILL.md Requirements
├─ ⭐ 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
Why SkillWink?
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.
FAQ
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
1. What are Agent Skills?
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.
2. How do Skills work?
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.
3. How can I quickly find the right skill?
Use these three together:
- Semantic search: describe your goal in natural language.
- Multi-filtering: category/tag/author/language/license.
- Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
- Upload archive: .zip / .skill (recommended)
- Upload skills folder
- Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
- Claude Code：~/.claude/skills/
- Codex CLI：~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared 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.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
- Wrong folder path or nested one level too deep
- Invalid/incomplete SKILL.md fields or format
- Dependencies missing (Python/Node/CLI)
- Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills:
- Duplicate skills: compare differences (speed/stability/focus)
- Low quality skills: regularly cleaned up