Free to get · One-click to use
Navigate campaign workspaces with `cgo` and `camp go`. Use when you need to move between projects/festivals/workflow directories, switch context quickly, or resolve script-safe paths with `camp go --print`.
Checks AGENTS.md and SKILL.md files against the actual codebase for drift. Surfaces references to packages, directories, commands, or patterns that no longer match reality.
Use this when you are working on file operations like reading, writing, scanning, or deleting files. It summarizes the preferred file APIs and patterns used in this repo. It also notes when to use filesystem helpers for directories.
Archive plan directories in .claude/plans/ for completed Jira tickets. Use this skill whenever the user asks to clean up plans, archive plan files, move completed plans, tidy the plans directory, or remove old ticket directories from .claude/plans/. Also applies when the user says a ticket is done and wants its plan archived, or asks for a bulk cleanup of the plans folder. --- # Archive Plan Files Moves completed ticket plan directories from `.claude/plans/` into `.claude/plans/archive/` based on live Jira status. Nothing is deleted — only moved. ## Procedure ### 1. Scan for Ticket Directories List directories in `.claude/plans/` that match the Jira ticket pattern (`PROJECT-NUMBER`): ```bash ls .claude/plans/ | grep -E '^[A-Z]+-[0-9]+$' ``` Ignore non-ticket directories (e.g., `deployment-confidence`, `sprint-25`, `archive`). These are not plan directories and should never be moved or modified. If the user names a specific ticket, still scan to confirm the directory exists before proceeding. ### 2. Query Jira for Live Status Always verify ticket status from Jira — even if the user says "it's done." Users sometimes misremember, or the ticket may have been reopened. Checking Jira takes seconds and prevents archiving active work. For each ticket directory, query Jira: ```
Scaffold a complete agent hackathon — generates PROJECT.md, phase kickoff YAMLs, and output directories from a few questions. Run this to spin up a new hackathon in seconds.
Use this skill when the user wants to share, install, inspect, publish, claim, or troubleshoot agent skills with Skilo links, refs, bundles, or tool-native skill directories.
Add documentation directories to ~/.prism/ontology-docs.json for prism_docs tools. Use when the user wants to add docs paths, register documentation directories, or configure ontology docs.
Project directory structure template — approved directories, depth limits, forbidden patterns
Read, write, and manage files and directories in the filesystem.
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:
