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
tfriedel tfriedel
from GitHub Content & Multimedia
  • 📁 ooxml/
  • 📁 scripts/
  • 📄 docx-js.md
  • 📄 ooxml.md
  • 📄 SKILL.md
documents comments document

docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

⬇0 ❤461 1 month ago · Uploaded Detail →
tomascupr tomascupr
from GitHub Content & Multimedia
  • 📁 ooxml/
  • 📁 scripts/
  • 📄 docx-js.md
  • 📄 ooxml.md
  • 📄 SKILL.md
documents comments document

docx

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

⬇0 ❤430 27 days ago · Uploaded Detail →
Othmane-Khadri Othmane-Khadri
from GitHub Tools & Productivity
  • 📁 references/
  • 📄 SKILL.md
post comments linkedin

answer-linkedin-comments

Reply to comments on a LinkedIn post via Unipile — drafts thread-aware replies grounded in the user's voice and the conversation context, then sends on approval. Use when the user says 'answer comments on my post', 'reply to LinkedIn comments', 'respond to engagement on this post', 'draft replies to commenters', or 'answer the LinkedIn thread'. Side-effecting — calls Unipile to read + post replies.

⬇0 ❤146 11 days ago · Uploaded Detail →
mgratzer mgratzer
from GitHub Databases & Storage
  • 📄 SKILL.md
feedback comments address

forge-address-pr-feedback

Analyze and address unresolved feedback on a GitHub pull request. Use when the user has received PR review comments and wants to systematically address each piece of feedback, or when the user mentions PR feedback, review comments, or addressing reviewer concerns.

⬇0 ❤62 1 month ago · Uploaded Detail →
akiojin akiojin
from GitHub Data & AI
  • 📁 scripts/
  • 📄 LICENSE.txt
  • 📄 SKILL.md
comments reviewer threads

gh-fix-ci

Inspect GitHub PR for CI failures, merge conflicts, update-branch requirements, reviewer comments, change requests, and unresolved review threads. Create fix plans and implement after user approval. Reply to ALL reviewer comments with action taken or reason for not addressing, then resolve threads. Notify reviewers after fixes.

⬇0 ❤36 1 month ago · Uploaded Detail →
bostonaholic bostonaholic
from GitHub Data & AI
  • 📁 references/
  • 📄 SKILL.md
reflect data reviews

reflect

This skill should be used when someone needs to generate a brag document from GitHub activity, set up reflect for the first time, run reflect to fetch contributions, configure a GitHub token for reflect, filter contributions by organization or repository, choose between OpenAI and Anthropic providers, understand reflect output files, troubleshoot reflect not working, or debug brag doc errors. --- # Reflect Reflect is a CLI tool that fetches GitHub activity -- merged pull requests, closed issues, and PR reviews -- and uses LLM APIs to generate professional brag documents for performance reviews. It connects to the GitHub GraphQL API via Octokit to retrieve contribution data, then optionally passes that data through an LLM provider (OpenAI or Anthropic) to produce summarized and narrative-format documents. All output is written as structured Markdown files suitable for self-assessments, promotion packets, and manager reviews. ## First-Time Setup ### Prerequisites Ensure the following are available before running Reflect

⬇0 ❤36 1 month ago · Uploaded Detail →
microwind microwind
from GitHub Content & Multimedia
  • 📁 examples/
  • 📄 SKILL.md
market data commentary

a-share-market-commentary

Generate structured A-share market commentary for three fixed trading sessions using supplied market data: within 30 minutes after market open, after midday close, and after market close. Use this skill when the user wants factual market observation, intraday commentary, or end-of-day review content based on real A-share inputs. Do not use it for stock picking, trading advice, or fabricated commentary without data.

⬇0 ❤20 1 month 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