Daily Featured Skills Count
3,840 3,909 3,920 3,927 3,966 4,007 4,027
04/06 04/07 04/08 04/09 04/10 04/11 04/12
♾️ Free & Open Source 🛡️ Secure & Worry-Free

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
kirich1409 kirich1409
from GitHub Ops & Delivery
  • 📄 SKILL.md
review comments feedback

address-review-feedback

Use when the user has received review comments on a GitHub PR or GitLab MR and needs to process them — analyze, triage, coordinate fixes, respond, and resolve threads. This is THE skill for any post-review work on a PR/MR. Triggers on: "разберись с комментариями", "address review comments", "handle review feedback", "respond to reviewers", "fix review comments", "deal with PR/MR comments", "reply to review", "resolve review threads", "go through the feedback", "комментарии к PR/MR", "ревьюер оставил комментарии", "пройдись по комментариям", "тредов после ревью", "reviewer left comments", "got a review", "review feedback on my MR/PR", or any mention of processing, triaging, or responding to existing review comments on a pull request or merge request. Do NOT use for writing new reviews, creating PRs, or CI/CD monitoring — those are separate skills. --- # Address Review Feedback An orchestrator skill. Analyzes all review comments, categorizes them, detects cross-diff patterns, presents an action plan for user confirmation, then coordinates fixes, answers, and thread responses. Does NOT implement code changes itself — it produces task descriptions for implementation agents. **Core principle:** Fix what belongs to this PR. Push back when a suggestion is wrong. Never perform agreement — just act and show evidence. --- ## Phase 1: Fetch & Parse ### Platform detection ```bash REMOTE_URL=$(git remote get-url origin) # Contains github.com → GitHub (gh) # Contains gitlab → GitLab (glab) ``` ### Fetch PR/MR metadata and context Fetch both technical metadata and the PR/MR context — description, linked issues, labels, milestone. This context is essential for Phase 2: understanding the intent behind changes lets you judge whether a comment is in scope, whether a suggestion aligns with the goal, and what trade-offs matter. ```bash # GitHub — metadata + context in one call PR_INFO=$(gh pr view --json number,baseRefName,headRefName,title,body,labels,milestone,closingIssuesReferen

⬇0 ❤6 5 days ago · Uploaded Detail →
tim-hua-01 tim-hua-01
from GitHub Development & Coding
  • 📁 references/
  • 📁 scripts/
  • 📄 SKILL.md
comments documents word

comment-on-docx

Adds comments to a word doc following commenting guidelines. Use when the user asks for comments, reviews, or feedback on Microsoft Word (.docx) documents. Provides helper scripts and instructions for how to read documents, draft thoughtful comments, and add them programmatically.

⬇0 ❤5 5 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