Name: Skill Validation
Author: Skills Guide Bot

Automated summary

Checks one or all SKILL.md files in the repository against the authoring rules and quality checklist defined in CLAUDE.md, then reports per-skill results.

Strengths

Covers four explicit dimensions: spec validity, correctness, effectiveness, and naming convention
Produces a standardized table with ✅/⚠️/❌ statuses plus a list of individual issues
Can target a single skill via $ARGUMENTS or validate everything with `all`
Ends with an aggregate count such as X/Y skills passed

Limitations

Entirely dependent on CLAUDE.md: without that file the criteria stay undefined
Only reports problems, it does not fix them
Assumes the fixed layout `.claude/skills/<name>/SKILL.md`

When to use it

Use it before publishing or updating a skill to confirm it complies with the repository's authoring rules.

When not to use it

Not suitable for skills stored outside `.claude/skills/` or in a repository that has no CLAUDE.md.

Security analysis

Safe

Quality score82/100

The skill is a read-only validation workflow: it instructs the agent to inspect CLAUDE.md and skill files, then produce a structured report. It declares no tools, runs no shell/network/destructive commands, and does not exfiltrate data or disable safety controls.

No concerns found

How this analysis is made

Examples

Validate one skill

Validate the skill `pdf-extraction` against the rules in CLAUDE.md and list any issues.

Validate everything

Run the validation on all skills under .claude/skills/ and give me the X/Y summary.

Check naming

Check whether the skill named `PDF_Parser` follows our naming convention and report the result in the standard table.

Validate skill(s) in this repository using the authoring rules and quality checklist defined in CLAUDE.md.

If $ARGUMENTS is a skill name, validate only .claude/skills/$ARGUMENTS/SKILL.md.
If $ARGUMENTS is empty or all, validate every skill found under .claude/skills/.

For each skill, apply the four validation criteria from CLAUDE.md:

Spec validity - frontmatter fields per the agentskills.io + Claude Code spec.
Correctness - rules match code examples, numeric limits are consistent, all variables are declared.
Effectiveness - language-agnostic rules, checklist maps to rules, references present, no security gaps for the threat domain.
Naming convention - Name of the skill follow the convention defined in the CLAUDE.md.

Output format

For each skill:

`<skill-name>` — [PASS | ISSUES FOUND]

| Check | Status | Detail | |---|---|---| | Spec validity | ✅ / ❌ | … | | Correctness | ✅ / ⚠️ / ❌ | … | | Effectiveness | ✅ / ⚠️ / ❌ | … | | Naming convention | ✅ / ⚠️ / ❌ | … |

List each individual issue below the table. End with a summary: X/Y skills passed all checks.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/skill-validation-mrwakdvg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/skill-validation-mrwakdvg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/skill-validation-mrwakdvg/download' --output '.skill-downloads/skill-validation-mrwakdvg/SKILL.md.part' && mv '.skill-downloads/skill-validation-mrwakdvg/SKILL.md.part' '.skill-downloads/skill-validation-mrwakdvg/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/skill-validation-mrwakdvg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.