Use when completing retro feature work, after implementation and tests pass, before creating PRs. Keywords: scenario tests, clean install, retro documentation updates.
Install wp-opencode on a VPS. Use this skill from your LOCAL machine to deploy a self-contained WordPress + OpenCode environment on a remote server.
Use this skill for ANY multi-pane or multi-agent terminal orchestration in cmux. Required when the user wants to: run things in parallel in separate terminal panes, split the terminal, spawn a sub-agent (Claude Code, Codex) in another pane, fan out tasks across splits, send keystrokes or text to another pane (including ctrl-c), read terminal output from another pane, update sidebar status or progress bar, open a URL in cmux's built-in browser pane, or display markdown preview alongside the terminal. The cmux CLI is the ONLY way to do these things — Bash cannot split panes or spawn agents. Trigger phrases: 'in parallel', 'split pane', 'spawn agent', 'fan out', 'new pane', 'browser pane', 'sidebar', 'send to pane', 'read from pane', 'show the plan', 'ctrl-c to', '分屏', '并行', '开个 pane'. NOT for: single command execution, basic bash operations, or questions about tmux.
Detect which GoClaw docs pages need updating when source code changes.
Manage container images, Helm charts, and build artifacts — registry organization, retention, promotion between environments.
Jest testing patterns, anti-patterns, and quality rules
Use when preparing Canadian tax review packets for T4 employment income, rental income, sole proprietorships, corporations, GST/HST, payroll, or slip season. Anchors the workflow in CRA source pages, uses Taxtips only for secondary checklist ideas, and produces human-review tax prep packages instead of compliance claims.
E2E test skill for validation
Triage and audit IDA binaries. Use when asked to analyze a binary, find suspicious behavior, detect crypto/network activity, review decompiled code against source, or run multi-table queries.
Repo-backed PRD-to-code orchestration for Claude and Codex. Use when the user wants a new app or existing repository run through discovery, architecture, milestones, execution, and validation instead of ad-hoc prompt-only delivery. Supports greenfield and existing codebases across web, iOS, Android, CLI, agent, API, and desktop projects, with first-class workspace-first support for Bun, npm, and pnpm repositories plus reference templates for additional ecosystems. --- # Harness Engineering and Orchestrator ## What This Skill Does This skill turns a project idea or an existing repository into a repo-backed delivery loop. - Planning is written into `docs/PRD.md` and `docs/ARCHITECTURE.md` - Execution state is written into `.harness/state.json` and `docs/PROGRESS.md` - Work is organized as `Project Plan -> Delivery Phase -> Milestone -> Task`, not just chat turns - Validation decides whether the project can actually advance Use it when you want Claude or Codex to operate inside a controlled engineering workflow rather than free-form prompting. ## Harness Levels The skill operates at three levels of ceremony, auto-detected or user-specified: | Level | When | Discovery Pacing | Active Guardians | Approval Stops | |-------|------|-----------------|------------------|----------------| | **Lite** | Small projects, quick prototypes | Batch 1-2 Qs/turn | Core (G1,G3,G4,G6,G8; G2/G10 warn-only; G5/G7 off) | Fast Path summary, delivery phase completion, blockers | | **Standard** | Most projects (default) | Groups of 2-3 Qs/turn | All (G1–G8,G10 active) | Overall plan approval, delivery phase completion, blockers | | **Full** | Enterprise / compliance projects | Sequential Q0-Q9 | All (G1–G8,G10 active) | Overall plan approval, delivery phase completion, blockers, deploy review | The level is stored in `state.projectInfo.harnessLevel` and can be upgraded mid-project. See [references/level-upgrade-backfill.md](./references/level-upgrade-backfill.md) for the backfill protocol when
Register bot commands with Telegram so they appear in the command menu
Discover edge cases and test coverage gaps through systematic analysis. Use when analysing test coverage, finding bugs, hunting for edge cases, reviewing code for robustness, or when code-reviewer identifies test gaps. Also use when the user says things like "what could go wrong", "is this well tested", "find holes in my tests", "what am I missing", or asks about edge cases for any function or module.
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:
