Use whenever a user shares or describes a 104 履歷 (resume) or LinkedIn profile and wants it reviewed, scored, or improved — even if they only paste a fragment or describe it verbally.
Resolve specific ESLint errors and warnings that appear in this project. Use when fixing lint failures, ESLint reported issues, or autofix conflicts (e.g. no-void, canonical/export-specifier-newline vs prettier, no-shadow trailing underscores, sonarjs/deprecation, you-dont-need-lodash-underscore, testing-library/prefer-screen-queries, testing-library/await-async-events, jest-dom/prefer-*).
>-
DEVORQ-DDD v1.0.0 — Skill de exploração de domínio para devorq_v3. Guia descoberta do modelo mental ANTES de escrever SPEC.md. Gera domain-model.json com entidades, contextos delimitados e invariantes.
Design safe unattended or long-running loops with explicit limits, checkpoints, and handoff artifacts.
Build a living AI model of your crush from chat logs, photos, and social media. Runs Bayesian memory tagging, attachment-style diagnosis, and generates a personalized Skill that talks like them. | 把你的 crush 蒸馏成 AI Skill，导入聊天记录，运行贝叶斯信号分析，诊断依恋类型，并模拟对话演习。
ALWAYS use this skill for code navigation, code search, finding references, understanding code structure, or exploring a codebase. This project has Scope CLI installed — use scope commands (via Bash) instead of grep, find, or reading files for navigation. Scope returns structural intelligence (class sketches, caller chains, dependency graphs, entry points) in ~200 tokens instead of ~4,000 for full source files. Check `scope status` first. If .scope/ exists, scope is available.
Extract clean markdown content from web pages using Defuddle CLI. ALWAYS use this instead of WebFetch when the user provides a URL to read or analyze. TRIGGER when: user provides any URL to a webpage, documentation, article, blog post, or any standard web content. DO NOT use WebFetch for these — use defuddle.
Stage changes, create conventional commit (no co-author), push to origin, and add detailed PR comment with session context
Link GitHub PRs to Jira tasks and vice-versa. Automatically triggered after creating a PR (via /pr) or when working on Jira task status updates. Adds the Jira issue key to the PR title and adds the PR URL as a remote link on the Jira issue. Only activates for repositories belonging to GitHub organizations that have a configured Jira project mapping. Use when creating PRs, linking PRs to Jira, or when the user mentions connecting a PR with a Jira task.
将用户想法转化为可确认的 design 文档并落盘。用于头脑风暴、新功能/需求定义、需求澄清、写 design/PRD 之前；在开始任何实现（写代码/改配置/改行为）前应先使用此流程。
- Wants to work on multiple branches simultaneously or in parallel
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:
