- 📄 mapping.json
- 📄 README.md
- 📄 SKILL.md
goclaw-docs-audit
Detect which GoClaw docs pages need updating when source code changes.
23 days ago · Uploaded
Detail →
Daily Featured Skills Count
04/17
04/18
04/19
04/20
04/21
04/22
04/23
♾️ Free & Open Source 🛡️ Secure & Worry-Free
Import Skills
- 📁 agents/
- 📁 references/
- 📁 scripts/
- 📄 config.example.json
- 📄 CONTRIBUTING.md
- 📄 LICENSE
harness-engineering-orchestrator
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
23 days ago · Uploaded
Detail →
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
knowledge-base-audit
This skill should be used when the user asks to "audit a wiki vault", "check dead links or orphan pages", "inspect knowledge base structure", "审计 wiki", "检查知识库结构", "看看有没有死链或孤立页", or "检查导航、frontmatter 和噪音回流". It audits a markdown/wiki knowledge base by reading a vault profile first and then checking structure, navigation, metadata, boundary drift, noise regression, and stray markdown files at the vault root.
2 days ago · Uploaded
Detail →
- 📄 SKILL.md
audit
Run one or more codebase audits (evaluation, health, documentation) with parallel agent execution, producing intake docs for a single /pipeline run.
20 days ago · Uploaded
Detail →
- 📁 agents/
- 📄 SKILL.md
rdc-analyst
Public main skill for the incubating analyzer framework. Use when the user wants to analyze captures, reconstruct pass/resource relationships, infer engine or material structure, or build reusable render knowledge instead of directly debugging a defect. This skill is the future entry for analyzer requests and currently provides the minimum intake contract only.
23 days ago · Uploaded
Detail →
- 📄 SKILL.md
advise
Search team knowledge before starting work. Use when starting experiments, debugging unfamiliar errors, or before implementing features with unknowns.
24 days ago · Uploaded
Detail →
- 📁 scripts/
- 📄 SKILL.md
knowledge-graph
Use when user says "update/refresh knowledge graph", "graph status", "blind spots", "CLAUDE.md coverage", or "init knowledge graph". Also use when receiving a "[kg auto-trigger]" message injected by hooks. Do not use for regular coding tasks.
7 days ago · Uploaded
Detail →
- 📄 SKILL.md
add-material
创建或更新 Material 实体——标准化的材料录入流程，确保信息补全、边关系正确、可视化同步。由 knowledge-process、bootstrap、ito 待命模式等场景调用。
19 days ago · Uploaded
Detail →
- 📄 SKILL.md
release
Release workflow for anna Go CLI project. Create releases with semantic versioned tags, update changelog, and trigger automated CI/CD builds. Use when the user asks to "release", "create a release", "tag a version", "update changelog", "prepare release", "cut a release", or discusses versioning and release artifacts. --- # Release ## Tag Format Use semantic versioning with `v` prefix: `v0.1.0`, `v1.0.0`, `v1.2.3-rc.1`. GoReleaser auto-detects pre-release suffixes (`-rc.1`, `-beta.1`). ## Release Flow 1. Update `docs/content/docs/changelog.mdx` (see below) 2. Commit: `📝 docs: Update CHANGELOG for vX.Y.Z` 3. Tag: `git tag vX.Y.Z` 4. Push: `git push origin main --tags` 5. CI triggers `.github/workflows/release.yml` → GoReleaser binaries + Docker images ## Update Changelog The changelog lives at `docs/content/docs/changelog.mdx` (rendered on the docs site). It has YAML frontmatter — preserve it when editing. Only modify content below the `---` block.
19 days ago · Uploaded
Detail →
- 📄 SKILL.md
smalltalk-commenter
Generates CRC-style class comments for Smalltalk classes. Use after creating or modifying Tonel files to add or improve class documentation.
20 days ago · Uploaded
Detail →
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
chilly-cli
Use `chilly` to operate chill.institute from the terminal. Start here for shared agent-safe defaults, then load the nested reference docs for auth, reads, mutations, or contract discovery only when that workflow is relevant.
23 days ago · Uploaded
Detail →
- 📄 SKILL.md
mev-security
Guide for MEV concepts, common attacks, mitigations, and how to organize MEV-related resources in README.md.
23 days ago · Uploaded
Detail →
Skill File Structure Sample (Reference)
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
SKILL.md Requirements
├─ ⭐ 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
Why SkillWink?
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.
FAQ
Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.
1. What are Agent Skills?
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.
2. How do Skills work?
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.
3. How can I quickly find the right skill?
Use these three together:
- Semantic search: describe your goal in natural language.
- Multi-filtering: category/tag/author/language/license.
- Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
- Upload archive: .zip / .skill (recommended)
- Upload skills folder
- Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
- Claude Code：~/.claude/skills/
- Codex CLI：~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared 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.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
- Wrong folder path or nested one level too deep
- Invalid/incomplete SKILL.md fields or format
- Dependencies missing (Python/Node/CLI)
- Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills:
- Duplicate skills: compare differences (speed/stability/focus)
- Low quality skills: regularly cleaned up