examples: Skill for Claude Code

.claude/skills/skills:validate/SKILL.md

skills:validate is a skill for Claude Code from rossoctl/examples. It costs 14 tokens per session (1,275 once invoked), scanned A, original, Apache-2.0.

A checker for skill files and their naming and formatting rules. Skill files are instruction files that teach a coding agent how to perform a task.

In plain words
What is it for?
Use it after creating or editing a skill, or when auditing many skills for frontmatter, headings, diagrams, command rules, and related-skill information.
Why use it?
It catches missing required sections, invalid names, unsafe command formats, and other problems before skills are committed or shared.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions Claude Code.

This is rossoctl/examples's own configuration. It tells Claude Code how to work on examples itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything examples configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rossoctl/examples. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/rossoctl/examples/main/.claude/skills/skills:validate/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rossoctl/examples

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for skills:validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/rossoctl/examples/skills-validate/github.svg)](https://agentmods.dev/skills/rossoctl/examples/skills-validate)
Your own site
<a href="https://agentmods.dev/skills/rossoctl/examples/skills-validate"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/skills-validate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for skills:validate

Your own site · 80×15
<a href="https://agentmods.dev/skills/rossoctl/examples/skills-validate"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/skills-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,275 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 9 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Agent Snooping · line 87
    Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.
    Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
  • high Agent Snooping · line 91
    Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.
    Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
  • medium Excessive Agency · line 53
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 56
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 59
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 71
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 109
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 31
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
  • medium Excessive Agency · line 48
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.01275
Opus 5.5 $0.00006 $0.00510
Sonnet 5.5 $0.00003 $0.00255
Haiku 4.5 $0.00001 $0.00128

Measured 1mo ago against content hash 288489e01cf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

skills:validate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/skills:validate/SKILL.md · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Validate Skill

When to Use

  • After creating or editing a skill
  • Before committing skill changes
  • When auditing all skills for consistency

Validation Checks

Required

  • Frontmatter: Has name: and description: fields
  • Colon naming: name: uses colon notation (e.g., tdd:ci not tdd-ci)
  • Directory match: Directory name matches frontmatter name: field
  • Title: Has # Skill Name as first heading
  • When to Use: Has "When to Use" or "Overview" section
  • Related Skills: Has "Related Skills" section at the end
  • Mermaid diagram: Workflow/router skills have an embedded mermaid diagram
  • Diagram colors: classDef colors match README color legend

Command Format (Required)

  • Sandbox classification: Skill is classified as sandbox or management (see below)
  • Single commands: Sandbox skills use one command per code block (no && chaining)
  • Auto-approve coverage: All commands in sandbox skills match a pattern in .claude/settings.json
  • No multiline bash: Sandbox skills avoid heredocs, multiline pipes, or for loops in commands

Recommended

  • TOC: Table of Contents present if skill > 50 lines
  • Placeholders: All commands are copy-pasteable (no unexplained placeholders)
  • Task tracking: TDD/RCA skills have "Task Tracking" section
  • Parent ref: Parent category SKILL.md references this skill
  • Imperative voice: Uses "Run X" not "You should run X"
  • Length: Leaf skills are 80-200 lines (300 max)
  • Diagram-text match: Diagram nodes correspond to textual flow steps

Sandbox vs Management Classification

Skills operate on either sandbox (safe) or management (requires approval) targets:

Type Target Auto-approve? Command format
Sandbox Local Kind cluster, custom HyperShift hosted cluster YES Single commands, one per step
Management Management cluster, AWS resources, git push, destructive ops NO Can chain commands (user approves anyway)

Read the full file on GitHub · 150 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 150 lines · 14 tokens per session scan A 288489e01cf9

Subscribe to this mod's changes

skills:validate is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 1,275 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.