Converts the old flat skills.yaml format to the new per-group file format with variants. Use when a PR or branch still has a top-level "skills:" array instead of separate group files.
../../../skills/zio-reference/SKILL.md
../../../skills/claude-code/SKILL.md
Create a new SKILL.md via discovery recap, pattern selection, WebFetch spec fetch, knowledge delta discipline, skill-forge-judge + skill-forge-hitl quality gate. Triggers: create a skill, write a skill, new skill, SKILL.md, build a skill.
Analyze target project codebase and recommend relevant AIE-Skills to install. Use when installing, setting up, or copying ML skills to a new project, bootstrapping AI/ML workflow, or sharing skills across repos.
Master reference for sending emails that reach the inbox. Always load this skill first for any email-related task, it will orient you quickly and route you to the right sub-skill. Use it for: email sending setup, inbox placement, spam avoidance, domain reputation, email infrastructure, writing or reviewing email copy, diagnosing why emails go to spam, building email workflows, or advising on list management. If the task touches email in any way, start here before doing anything else. --- # Email Skills by AutoSend A modular skill set for AI agents writing, reviewing, or advising on email. The goal is inbox placement, not just sending. Every decision here connects back to that. This is the entry point. Read this first, then load the relevant sub-skill for deeper guidance on a specific topic. --- ## The Deliverability Stack Inbox placement depends on four pillars working together. A failure in any one of them can undo the other three. ``` 1. Authentication → Proves you are who you say you are 2. Sender Reputation → Proves you are a responsible sender 3. Content Quality → Proves your email is wanted 4. List Quality → Proves your recipients consented and are real ``` --- ## Sub-Skills (Load as Needed) | Topic | Sub-Skill | When to Use | | ------------------------------- | ------------------------------ | --------------------------------------------------- | | SPF, DKIM, DMARC, BIMI | `authentication/SKILL.md` | Setting up or debugging email authentication | | Subject lines, HTML, copy | `content/SKILL.md` | Writing or reviewing email content | | CAN-SPAM, GDPR, CASL | `compliance/SKILL.md` | Any question touching legal requirements or consent | | Validation, suppression, sunset | `list-hygiene/SKILL.md` | Managing contacts, bounces, or unsubscribes | | OTP, receipts, password reset | `t
../../../skills/marp/SKILL.md
Demo skill showing Claude Code compatible SKILL.md format
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:
