16,143 Open Skills

Free to get · One-click to use

✅ Keyword search & category filters
✅ Discussions & community interaction
✅ Version updates & multi-metric ranking
✅ Open SKILL.md standard

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
ControlNet ControlNet
from GitHub Tools & Productivity
json work skip-hooks

beads

Manages TODOs and long-horizon work using the bd (Beads) CLI: creates issues, links dependencies, finds ready work, and keeps the tracker synced via git and dolt. Use when tracking tasks across sessions, compaction, or multiple agents/branches. --- # Managing TODOs with Beads (bd) ## Quick start Prefer bd issues over ad-hoc markdown TODOs for any non-trivial workstream. 1) Ensure the repo is initialized: - Fresh clone / repair path: `bd bootstrap --dry-run --json`, then `bd bootstrap` - Human developer leading repo: `bd init --contributor --skip-hooks` - AI developer leading repo: `bd init --skip-hooks` - Human team collaboration repo workflow: `bd init --team --skip-hooks` - Legacy `.beads/issues.jsonl` repo: `bd init --from-jsonl --skip-hooks` 2) Load the live workflow context: `bd prime` 3) Find ready work with `bd ready --json`, and record new work with explicit context: `bd create "Short title" --description="Why this work exists" -t task -p 2 --json` 4) When you begin work on an issue, claim it atomically: `bd update <id> --claim --json` ## Default workflow - Start: `bd prime`, then `bd ready --json`; inspect with `bd show <id> --json` when needed. - Claim work with `bd update <id> --claim --json` instead of manually setting status flags. - During work: file discovered TODOs immediately as issues (bugs/tasks/features), include `--description`, and link provenance with `--deps discovered-from:<current-id>`. - Update issues non-interactively with `bd update` flags or `bd comments add`; do not rely on `bd edit` from an agent session. - End of session: close completed issues with `bd close <id> --reason "..." --json` (or `bd done <id> --reason "..." --json`), leave partial work open with fresh notes/next steps, and sync via Dolt (`bd dolt push` / `bd dolt pull`) or current hooks. If you initialized with `--skip-hooks`, install them later with `bd hooks install` when you want hook-managed sync/context injection. ## Reference - Commands: see [COMMANDS.md](COMMANDS.m

⬇0 ❤6 14 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.

Keyword Search Version Updates Multi-Metric Ranking Open Standard Discussion

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