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

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
signnow signnow
from GitHub Tools & Productivity
  • 📄 SKILL.md
commit git type

git-commit

Use when preparing to commit changes or drafting a git commit message in this repo. --- # Git Commit & Commit Message (SignNow MCP Server) ## Critical rules * **NEVER commit directly to `main` or `master`.** Always work on a dedicated branch. * Do not commit unless **all required checks** pass (see below). * Keep each commit **one logical change** (single change type). * Commit message follows **Conventional Commits**. ## Workflow 0. **Create (or switch to) a feature branch — MANDATORY** * NEVER commit to `main` or `master` directly. * If not already on a feature branch, create one: * `git checkout -b <type>/<short-description>` (e.g., `feat/add-embedded-editor`, `fix/token-refresh`) * Branch naming: `<type>/<short-description>` using the same type vocabulary as commit types. 1. **Check what changed** * `git status -sb` * If changes are mixed, split into separate commits using `git add -p`. 2. **Review staged diff** * Stage what belongs to this commit. * Inspect: `git diff --cached` 3. **Run required checks (must be green)** ```bash pytest tests/unit/ -v ruff check src/ tests/ ruff format --check src/ tests/ ``` * If any command fails, fix the issue and rerun **all** checks. 4. **Compose the commit message** ### Subject format `<type>(<scope>)?: <subject>` ### Subject rules * Imperative mood ("Add", "Fix", "Remove", "Prevent", ...) * No trailing period * Prefer **≤ 72 chars** ### Body (optional) * Explain **why**, not just what. * Wrap lines at ~80 chars. ### Breaking changes (if applicable) * Add `!` after type/scope: `feat!: ...` or `feat(tools)!: ...` * Add footer: * `BREAKING CHANGE: <what breaks and migration notes>` 5. **Commit** * One-liner (no body/footer needed): * `git commit -m "..."` * Otherwise: * `git commit` and write subject + body in editor. 6. **Post-commit sanity** * `git show --stat` * Ensure no accidental files were committed. 7. **Push** * `git push` 8. **Create Pull Request (if none exists)** * After pushing, check whether a PR already exists

⬇0 ❤5 2 days ago · Uploaded Detail →
ZachRouan ZachRouan
from GitHub Data & AI
  • 📄 SKILL.md
windows click type

gui-tool

Interact with the desktop GUI — take screenshots, list/raise windows, move/click mouse, type text, press key combos. Use when you need to see the screen, find windows, click on things, type into applications, or automate any GUI interaction. All commands return JSON.

⬇0 ❤7 5 days ago · Uploaded Detail →
zachr-ux zachr-ux
from GitHub Data & AI
  • 📄 SKILL.md
windows click type

gui-tool

Interact with the desktop GUI — take screenshots, list/raise windows, move/click mouse, type text, press key combos. Use when you need to see the screen, find windows, click on things, type into applications, or automate any GUI interaction. All commands return JSON.

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