Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
Read, create, search, and manage notes in Obsidian vaults using the napkin CLI. Works directly on markdown files and canvas files — no Obsidian app required. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, work with tasks, tags, properties, daily notes, templates, bases, bookmarks, aliases, or canvas files from the command line.
Hidden layer of structured git notes for agent collaboration. When working in any git repo, check for mycelium notes on objects you touch (files, directories, commits) before acting, and leave notes after meaningful work. Uses git notes directly — helper script available but not required. --- # Mycelium Structured notes attached to git objects via `refs/notes/mycelium`. **Before working on a file, check for its note. After meaningful work, leave a note.** That's the whole contract. How you work, what you build, how you talk to your user — that's your business. Mycelium just asks you to read the breadcrumbs and leave new ones. ## On arrival
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks to add a note, list notes, search notes, or manage note folders.
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
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
├─ ⭐ 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
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.
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.
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
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.
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.
Use these three together:
Note: file size for all methods should be within 10MB.
Typical paths (may vary by local setup):
One SKILL.md can usually be reused 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.
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
Most common reasons:
We try to avoid that. Use ranking + comments to surface better skills:
