Daily Featured Skills Count
4,524 4,564 4,605 4,651 4,689 4,727 4,738
04/24 04/25 04/26 04/27 04/28 04/29 04/30
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
wjt0321 wjt0321
from GitHub Tools & Productivity
  • 📁 .githooks/
  • 📁 agents/
  • 📁 assets/
  • 📄 .env.example
  • 📄 .gitignore
  • 📄 AGENTS.md
data team-first 东方财富仅做结构

china-stock-analyst

A股短线分析助手，聚焦“短线交易信号 + 营收质量”双轨研判。默认采用 Team-First 并行分析，主数据源为 Web Search，东方财富仅做结构化补充与复核。

⬇0 ❤21 28 days ago · Uploaded Detail →
onsails onsails
from GitHub Tools & Productivity
  • 📁 scripts/
  • 📄 SKILL.md
code automation automated

review-loop

Runs multi-pass automated code review with per-issue fix subagents. Triggers when preparing a branch for PR, reviewing code changes, or when thorough automated code quality review is needed.

⬇0 ❤21 29 days ago · Uploaded Detail →
gate gate
from GitHub Testing & Security
  • 📁 references/
  • 📁 scripts/
  • 📄 CHANGELOG.md
  • 📄 install.sh
  • 📄 README.md
data dex gate-dex-wallet

gate-dex-market

Gate DEX read-only market data skill. Use when the user asks for prices, K-lines, rankings, holders, or liquidity without signing a tx. Triggers on 'DEX price', 'token K-line', 'holder analysis'. Do NOT use for swaps or wallet auth — use gate-dex-trade or gate-dex-wallet.

⬇0 ❤21 1 month ago · Uploaded Detail →
YukiKazahana YukiKazahana
from GitHub Tools & Productivity
  • 📁 agents/
  • 📄 SKILL.md
entering cadence issue

cadence-execution

Cadence's execution phase. Advances implementation, validation, and status writeback based on existing and continuable issue files; entering this phase when directly requested by the user is also considered entering Cadence. If there is no clear issue file or the target is unclear, ask the user to specify.

⬇0 ❤21 1 month ago · Uploaded Detail →
hypurrquant hypurrquant
from GitHub Data & AI
  • 📁 references/
  • 📁 scripts/
  • 📄 package.json
  • 📄 SKILL.md
hyperliquid pacifica funding

perp-cli

Multi-DEX perpetual futures trading CLI for Pacifica (Solana), Hyperliquid (EVM), Lighter (Ethereum), and Aster (BNB Chain). Use when user asks to: trade perps, check funding rates, scan arbitrage (perp-perp or spot-perp), delta-neutral strategies, bridge USDC, manage positions/orders, deposit/withdraw, spot+perp hedge, HIP-3 DEX trading, or mentions perp-cli, hypurrquant, Pacifica, Hyperliquid, Lighter, Aster, HyperEVM, funding arb, U-token (UBTC/UETH/USOL).

⬇0 ❤21 1 month ago · Uploaded Detail →
pierreb-devkit pierreb-devkit
from GitHub Data & AI
  • 📄 SKILL.md
module names modules

create-module

Use this whenever the user asks to "create a module", "scaffold a feature", "add a domain", "new module called X", or starts work on a brand-new vertical (controller + service + repo + model + routes + tests). Duplicates the canonical `modules/tasks` template, applies kebab/Pascal/camel renames, and registers config-driven enums. Module stays self-contained — never modify shared `lib/` or `config/` to bolt on module logic. --- # Create Module Skill Create a new module by copying and renaming the `tasks` template module. ## Prerequisites - The canonical template module `modules/tasks` must exist - You need a name for the new module (kebab-case) ## Steps ### 1. Ask for the module name Prompt user for the new module name in kebab-case (e.g., `my-feature`, `user-settings`) ### 2. Derive naming conventions Follow `/naming` for the full reference. Quick summary from the module name (e.g., `my-feature`): - **kebab-case**: `my-feature` (folder names, file prefixes, routes) - **PascalCase**: `MyFeature` (Mongoose model names, class names) - **lowerCamelCase**: `myFeature` (variable names, function names, JS exports) - **UPPER_SNAKE_CASE**: `MY_FEATURE` (constants) ### 3. Duplicate the module ```bash cp -r modules/tasks modules/{new-module-name} ``` ### 4. Rename references

⬇0 ❤21 1 month ago · Uploaded Detail →
BrOrlandi BrOrlandi
from GitHub Tools & Productivity
  • 📁 references/
  • 📄 SKILL.md
jira when prs

jira-link

Link GitHub PRs to Jira tasks and vice-versa. Automatically triggered after creating a PR (via /pr) or when working on Jira task status updates. Adds the Jira issue key to the PR title and adds the PR URL as a remote link on the Jira issue. Only activates for repositories belonging to GitHub organizations that have a configured Jira project mapping. Use when creating PRs, linking PRs to Jira, or when the user mentions connecting a PR with a Jira task.

⬇0 ❤19 16 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