verify-skills

<essential_principles>

1. Content, Not Structure. This skill checks whether what the skill says is still true. For structural validation, use audit-extensions instead. A structurally perfect skill with outdated API endpoints is still broken.

2. Dependency-Aware. Different skills depend on different things. An API integration skill needs endpoint verification. A CLI tool skill needs command syntax checking. Categorize first, then verify accordingly.

3. Cite Sources. When flagging something as outdated, provide the current correct information with a source. "Endpoint changed" is not useful. "Endpoint changed from /v2/users to /v3/users (per docs.example.com/changelog)" is useful.

4. Freshness Schedule. Not all skills need the same verification frequency. API-dependent skills need monthly checks. Process-dependent skills can go quarterly. Recommend an appropriate schedule.

</essential_principles>

<quick_start>

1. Provide the skill path to verify
2. The skill categorizes dependencies (API, CLI, framework, integration, process)
3. Each dependency is checked for currency
4. Outdated content is flagged with line numbers and current correct information
5. A freshness report is generated with pass/fail per section and re-verification schedule </quick_start>

<step_1> Read and Inventory Dependencies

Read the skill's SKILL.md and all workflows/references. Catalog every external dependency:

Dependency	Type	Location	Current Value	Source
Stripe API endpoint	API	references/stripe.md:15	/v1/charges	stripe.com/docs
npm create command	CLI	workflows/setup.md:8	npm create vite@latest	npmjs.com
React useEffect pattern	Framework	references/patterns.md:42	useEffect(() => {})	react.dev

Dependency types:

• API: Endpoints, parameters, auth methods, response formats, rate limits
• CLI: Command syntax, flags, subcommands, version requirements
• Framework: Patterns, best practices, deprecated features, version compatibility
• Integration: Connected service configs, environment variables, format requirements
• Process: Workflow steps, decision trees, methodology recommendations </step_1>

<step_2> Categorize the Skill

Determine the primary dependency type. Most skills have a dominant type:

Skill Category	Primary Dependencies	Verification Method	Frequency
API integration	Endpoints, params, auth	Check API docs, test endpoints	Monthly
CLI tooling	Commands, flags, versions	Check --help output, release notes	Monthly
Framework guide	Patterns, practices, APIs	Check official docs, changelogs	Quarterly
Service integration	Configs, formats, connections	Check service docs, status pages	Monthly
Process/methodology	Workflow steps, decision logic	Review against current best practices	Quarterly
Domain knowledge	Facts, rules, principles	Cross-reference authoritative sources	Semi-annually
</step_2>

<step_3> Verify Each Dependency

For each cataloged dependency, verify its current accuracy:

API dependencies:

• Check if endpoint URL is still valid
• Verify request/response format hasn't changed
• Confirm authentication method is current
• Check for deprecation notices
• Verify rate limits and quotas

CLI dependencies:

• Check if command syntax is still correct
• Verify flags and options still exist
• Confirm version requirements are current
• Check for deprecated commands or flags

Framework dependencies:

• Check if pattern is still recommended
• Verify API hasn't changed (hooks, methods, props)
• Check for deprecated features being used
• Confirm version compatibility ranges