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
inboxapi inboxapi
from GitHub Development & Coding
  • 📄 SKILL.md
check inbox their

check-inbox

Check your InboxAPI email inbox and display a summary of recent messages. Use when the user wants to see their emails, check mail, or view their inbox.

⬇0 ❤10 11 days ago · Uploaded Detail →
originalrgsec originalrgsec
from GitHub Docs & Knowledge
  • 📄 SKILL.md
mobile inbox notes

mobile-inbox-triage

Process and triage notes captured on mobile into the Obsidian knowledge vault. Use this skill whenever the user says anything like "check the mobile inbox", "process mobile notes", "triage inbox", "what came in from mobile", "sync my mobile notes", or any reference to the research/mobile-inbox folder. Also trigger at the start of any session where the user has been away from their desk, or when the user says "I captured some ideas on mobile" or "I sent some notes from my phone." If research/mobile-inbox/ contains unprocessed notes, this skill handles routing them to the correct vault locations. --- # Mobile Inbox Triage This skill processes notes that arrived in the Obsidian vault's `research/mobile-inbox/` folder via mobile capture (iOS Shortcut from Claude mobile conversations, voice memos, or manual Obsidian mobile entry). Each note gets read, analyzed, and routed to the appropriate vault location, then archived. ## When This Runs The user triggers this explicitly ("process my mobile inbox", "triage inbox", etc.) or it can be invoked as part of a session startup routine. The skill is designed to handle anywhere from 1 to 20 notes in a batch. ## Vault Location The Obsidian vault (named "Vault") lives at `Claude Context/Obsidian/` relative to the workspace root. The mobile inbox is at `Claude Context/Obsidian/research/mobile-inbox/`. Processed notes get moved to `Claude Context/Obsidian/research/mobile-inbox/archive/`. ## Processing Steps ### 1. Scan the inbox List all `.md` files in `research/mobile-inbox/` excluding `_index.md` and anything already in `archive/`. If no files are found, tell the user the inbox is empty and stop. ### 2. Read and classify each note For each note, read the full content and determine its type based on the content and any frontmatter hints: | Classification | Route To | Description | |---|---|---| | **Project update** | `projects/<tier>/<project>/status.md` | Append to the relevant project's status file as a dated entry | | **New idea

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