2,028 Open Skills

Free to get · One-click to use

✅ AI semantic search & keyword search
✅ Discussions & community interaction
✅ Version updates & multi-metric ranking
✅ Open SKILL.md standard

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
paperclipai paperclipai
from GitHub Development & Coding
  • 📁 references/
  • 📄 SKILL.md
frontend design not

design-guide

Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design tokens, typography, status/priority systems, composition patterns, and the /design-guide showcase page. Always use this skill alongside the frontend-design skill (for visual quality) and the web-design-guidelines skill (for web best practices). --- # Paperclip Design Guide Paperclip's UI is a professional-grade control plane — dense, keyboard-driven, dark-themed by default. Every pixel earns its place. **Always use with:** `frontend-design` (visual polish) and `web-design-guidelines` (web best practices). --- ## 1. Design Principles - **Dense but scannable.** Maximum information without clicks to reveal. Whitespace separates, not pads. - **Keyboard-first.** Global shortcuts (Cmd+K, C, [, ]). Power users rarely touch the mouse. - **Contextual, not modal.** Inline editing over dialog boxes. Dropdowns over page navigations. - **Dark theme default.** Neutral grays (OKLCH), not pure black. Accent colors for status/priority only. Text is the primary visual element. - **Component-driven.** Prefer reusable components that capture style conventions. Build at the right abstraction — not too granular, not too monolithic. --- ## 2. Tech Stack - **React 19** + **TypeScript** + **Vite** - **Tailwind CSS v4** with CSS variables (OKLCH color space) - **shadcn/ui** (new-york style, neutral base, CSS variables enabled) - **Radix UI** primitives (accessibility, focus management) - **Lucide React** icons (16px nav, 14px inline) - **class-variance-authority** (CVA) for component variants - **clsx + tailwind-merge** via `cn()` utility

⬇0 ❤11.8K 2天前 · 上传 Detail →
imbue-ai imbue-ai
from GitHub Development & Coding
  • 📁 scripts/
  • 📄 SKILL.md
changes not run

vet

Run vet immediately after ANY logical unit of code changes. Do not batch your changes, do not wait to be asked to run vet, make sure you are proactive.

⬇0 ❤115 2天前 · 上传 Detail →
bytemines bytemines
from GitHub Tools & Productivity
  • 📄 seed-test-db.ts
  • 📄 SKILL.md
not mycelium connecting

debug-mycelium

Use when mycelium sync fails, items not appearing in tools, enable/disable not working, MCP not connecting, config conflicts between levels, EACCES permission errors, or any unexpected mycelium CLI behavior.

⬇0 ❤17 9小时前 · 上传 Detail →
hamsurang hamsurang
from GitHub Development & Coding
  • 📄 SKILL.md
deepwiki-cli user not

deepwiki-cli

Use when the user asks questions about a GitHub repository's architecture, API, or internals, or mentions deepwiki-cli or DeepWiki. Activates when the user needs to understand a codebase they haven't cloned locally, or asks how a library or framework works. Do NOT activate for local codebases already accessible on disk or private repositories. --- # deepwiki-cli Skill deepwiki-cli provides AI-generated wiki documentation for GitHub repositories. Use the `deepwiki-cli` to query it directly — this keeps only the result text in Claude's context, avoiding MCP protocol overhead. ## When This Skill Activates - User references a GitHub repository by name (owner/repo format) - User asks how a library or framework works - User needs to understand a codebase they haven't read locally - User asks architecture or API questions about an open-source project ## How to Use Run via `Bash` tool: ```bash # Ask a question about a repository deepwiki-cli ask <owner/repo> "<question>" # List wiki topics for a repository deepwiki-cli structure <owner/repo> # Read full wiki contents deepwiki-cli read <owner/repo> ``` ## Examples ```bash deepwiki-cli ask facebook/react "How does the reconciler work?" deepwiki-cli ask vercel/next.js "What is the App Router architecture?" deepwiki-cli structure rust-lang/rust deepwiki-cli read tokio-rs/tokio ``` ## Prerequisites The `deepwiki-cli` binary must be installed: ```bash cargo install deepwiki-cli ``` If the binary is not found, inform the user to install it first. ## When NOT to Use - Repository is already cloned locally — use Glob/Grep/Read tools directly - Repository is private — deepwiki-cli only works with public repositories - User is asking about their own code in the current working directory ## Error Handling If `deepwiki-cli` is not installed or a command fails: 1. Check if the binary exists: `which deepwiki-cli` 2. If not found, tell the user to install: `cargo install deepwiki-cli` 3. If the repository is not found, verify the owner/repo

⬇0 ❤14 8小时前 · 上传 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 AI semantic + 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.

AI Semantic Search 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