hoavdc/CodexKit / skills/codexkit-skill-template
codexkit-skill-template
VerifiedReference implementation of a v2 CodexKit skill. Copy this folder as a starting point for new skills. Demonstrates all 10 required sections, 4C verification, and the tier-2 folder structure.
| File | Kind | Size |
|---|---|---|
| CHANGELOG.md | markdown | 217 B |
| SKILL.md | skill md | 4.2 KB |
| agents/openai.yaml | config | 238 B |
| examples/common-mistakes.md | markdown | 1.7 KB |
| examples/good-output.md | markdown | 1012 B |
| verification/checklist.md | markdown | 1.1 KB |
verification/checklist.md
View on GitHub# 4C Verification Checklist — Skill Template
> Use this checklist after generating any skill output. Answer each question honestly.
## Correctness — Is it right?
- [ ] Does the procedure follow established domain frameworks?
- [ ] Are all claims factual and verifiable?
- [ ] Does the output format match the specification?
## Completeness — Is it done?
- [ ] Are all required sections present?
- [ ] Are all required inputs accounted for?
- [ ] Is every procedure step actionable (not vague)?
## Context-fit — Does it match?
- [ ] Is the language appropriate for the target audience?
- [ ] Does it address the stated industry or domain?
- [ ] Is the level of detail proportional to the goal?
## Consequence — Is it safe to use?
- [ ] If sent to a stakeholder right now, would it be embarrassing?
- [ ] Could any part of this output cause material harm if followed literally?
- [ ] Are limitations and assumptions explicitly stated?
---
**Final question:** _If this output were used immediately in production, what is the single biggest risk?_
Write the answer here before considering the skill output complete.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |