Skip to content

gpsaggese/helpers / .claude/skills/skill.check_refs

skill.check_refs

Verified

Check the references in all the skill files

FileKindSize
SKILL.mdskill md1.3 KB
---
description: Check the references in all the skill files
model: haiku
---

# Goal
- Check that all the skill and rule files have references

# Workflow

## Find Files
- Find all markdown files: `SKILL.md` and `<TOPIC>.rules.md`
  ```bash
  > find .claude/skills -name "*.md"
  ```

## Read Context
- Read `.claude/skills/skill.rules.md` for context on rules

## Check Rules
- For each file, apply all the rules below and report violations as described

### Check Files Existence
- Make sure the file follows `.claude/skills/skill.rules.md`
  `# SKILL.md File Format`

### Check Header References
- Make sure the file follows `.claude/skills/skill.rules.md`
  `# References and Dependencies`

### Check for Other Violations
- Use the rules in `.claude/skills/skill.rules.md` to find clear violations
- Report a violation only when certain it is one

## Report Violations
- Report all violations in a file `cfile` using the format in
  `.claude/skills/cfile.rules.md`

## Ask the User Which Problems to Fix
- Ask which problems to fix by printing a numbered list of problems

# Verification
- [ ] Every file under `.claude/skills` matching `SKILL.md` or `<TOPIC>.rules.md`
      was checked
- [ ] `cfile` follows the format in `.claude/skills/cfile.rules.md`
- [ ] Every reported violation is one the reviewer is confident about
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: 471kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall