Daily Featured Skills Count
5,070 5,117 5,165 5,205 5,241 5,288 5,311
05/09 05/10 05/11 05/12 05/13 05/14 05/15
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
resend resend
from GitHub Tools & Productivity
  • 📁 references/
  • 📄 SKILL.md
resend templates automation

resend-cli

Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations, and events via the `resend` CLI. Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates. Always load this skill before running `resend` commands — it contains the non-interactive flag contract and gotchas that prevent silent failures.

⬇0 ❤362 1 month ago · Uploaded Detail →
dollspace-gay dollspace-gay
from GitHub Development & Coding
  • 📄 SKILL.md
template ai demonstrate

example-skill

This skill should be used when the user asks to "demonstrate skills", "show skill format", "create a skill template", or discusses skill development patterns. Provides a reference template for creating Claude Code plugin skills.

⬇0 ❤66 1 month ago · Uploaded Detail →
vanillaflava vanillaflava
from GitHub Data & AI
  • 📁 assets/
  • 📁 references/
  • 📄 SKILL.md
wiki templates schema

wiki-config

Set up, validate, and reconfigure the llm-wiki skill suite. Use when the user says /wiki-config, asks to "set up my wiki", "configure wiki", "initialize wiki config", mentions "page structure problems", "header errors", "schema issues", "missing templates", "page templates", asks for "wiki help", "how does the wiki work", or "explain the wiki skills", or when any wiki skill reports a missing or invalid config, schema, or templates folder. Owns the interactive configuration flow, schema management, and template management for the wiki system.

⬇0 ❤30 12 days ago · Uploaded Detail →
rubys rubys
from GitHub Development & Coding
  • 📄 skill.md
template scoring erb

compare-erb-js

Compare ERB and JavaScript template outputs for the offline scoring SPA. Use when working on ERB-to-JS conversion, debugging template parity issues, or verifying that changes to scoring views work correctly in both ERB and SPA modes.

⬇0 ❤36 1 month ago · Uploaded Detail →
vanillaflava vanillaflava
from GitHub Docs & Knowledge
  • 📁 assets/
  • 📁 references/
  • 📄 SKILL.md
wiki templates schema

wiki-config

Set up, validate, and reconfigure the llm-wiki skill suite. Use when the user says /wiki-config, asks to "set up my wiki", "configure wiki", "initialize wiki config", mentions "page structure problems", "header errors", "schema issues", "missing templates", "page templates", or when any wiki skill reports a missing or invalid config, schema, or templates folder. Owns the interactive configuration flow, schema management, and template management for the wiki system.

⬇0 ❤28 21 days ago · Uploaded Detail →
YoungLeadersDotTech YoungLeadersDotTech
from GitHub Docs & Knowledge
  • 📄 SKILL.md
ground truth template

ground-truth-template

Generic ground truth template for creating verifiable reference skills. Auto-invoke on 'ground truth skill', 'validation criteria', 'canonical documentation template'. Do NOT load during actual ground truth usage.

⬇0 ❤10 5 days ago · Uploaded Detail →
postmelee postmelee
from GitHub Development & Coding
  • 📄 SKILL.md
mydocs templates report.md

external-pr-review

외부 기여자 PR 검토 절차를 적용한다. PR 정보 수집, mydocs/pr/pr_{N}_review.md 작성, 검증, pr_{N}_report.md 작성, 처리 완료 시 archives/ 이동을 수행한다. 외부 기여자 PR 전용 (내부 타스크에는 사용 금지). --- # 외부 기여자 PR 검토 ## 트리거 - 작업지시자가 "PR #N 리뷰" 또는 "외부 PR 검토"를 명시 지시한 경우 - 본 SKILL을 직접 호출한 경우 ## 사전 조건 - 검토 대상 PR이 외부 기여자 fork에서 본 저장소 `{BASE_BRANCH}`(또는 합의된 base)로 열린 상태 - 내부 타스크 PR(`publish/task{N}`)에는 본 SKILL 사용 금지 — 내부 타스크는 일반 단계 절차로 검토 - `gh` CLI 인증 ## 절차 1. PR 메타 수집 ```bash gh pr view {N} --json number,title,state,baseRefName,headRefName,headRepository,mergeable,mergeStateStatus,reviewDecision,labels,body gh pr diff {N} | head -200 gh pr checks {N} ``` - 이슈 연결, base/head, mergeable, CI 상태 모두 확인 2. 검토 문서 작성: `mydocs/pr/pr_{N}_review.md` - 중앙 템플릿 `mydocs/_templates/external_pr_review.md`를 기준으로 작성한다. - 템플릿을 읽을 수 없는 경우에만 다음 최소 섹션을 fallback으로 사용한다: - PR 정보 (번호, 작성자, base/head, 연결 이슈) - 변경 요약 - 영향 범위와 호환성 (FFI, build, 문서) - 코드/문서 점검 결과 - 검증 계획 (필요한 추가 검증) - 권고 (merge / 수정 요청 / 닫기) - 작업지시자 승인 요청 3. 작업지시자 승인 요청 (검토 방향 결정) 4. 필요 시 수정·검증 계획 문서 작성: `mydocs/pr/pr_{N}_review_impl.md` - 중앙 템플릿 `mydocs/_templates/external_pr_review_impl.md`를 기준으로 작성한다. - 본 저장소에서 추가 검증을 직접 수행할 때 사용 - 작성 후 작업지시자 승인 요청 5. 검증 수행 (해당하는 경우만) - 검증은 변경 유형에 따라 `{PROJECT_VALIDATION_GUIDE}` 정책 적용 6. 최종 보고서 작성: `mydocs/pr/pr_{N}_report.md` - 중앙 템플릿 `mydocs/_templates/external_pr_report.md`를 기준으로 작성한다. - 검토 결과, 검증 결과, 최종 권고, GitHub PR 코멘트 본문(또는 링크) 7. 작업지시자 승인 후 GitHub PR에 코멘트/리뷰 등록 (merge 결정은 작업지시자가 수행) 8. 처리 완료 시 문서 보관 이동 ```bash git mv mydocs/pr/pr_{N}_review.md mydocs/pr/archives/ git mv mydocs/pr/pr_{N}_review_impl.md mydocs/pr/archives/ # 존재 시 git mv mydocs/pr/pr_{N}_report.md mydocs/pr/archives/ ``` 9. 단일 또는 단계별 커밋 (외부 PR 검토는 내부 단계 형식 강제 아님) ```bash git commit -m "PR #{N} 검토: {요약}" ``` ## 검증 - `mydocs/pr/pr_{N}_review.md`가 `mydocs/_templates/external_pr_review.md`의 필수 섹션을 채움 - `mydocs/pr/pr_{N}_review_impl.md`를 작성했다면 `mydocs/_templates/external_pr_review_impl.md`의 필수 섹션을 채움 - `mydocs/pr/pr_{N}_report.md`가 `mydocs/_templates/external_pr_report.md`의 필수 섹션

⬇0 ❤10 8 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