Skill & rule draft check

Client

Paste a SKILL.md-style file or .mdc rule draft to see frontmatter keys, ## section count, and length hints. Use with the prompt checklist when tuning instructions inside the body.

What we look for

Skills often expose name and description in YAML frontmatter; rules often add globs or alwaysApply. The body should usually include ## sections so agents and humans can scan quickly. Very long files are flagged for splitting—consistent with keeping repository skills maintainable.

Draft file

?

This does not execute your skill or call a model. It reads structure only. Multiline YAML values (>- blocks) are not fully parsed—single-line values work best for the preview.

Summary

Frontmatter
name, description
Kind hint
skill
Body lines
12
## sections
2

Common use cases

  • Sanity-check a SKILL.md or project rule before committing—especially name, description, and sectioning.
  • Compare two drafts by pasting each and watching body line and ## counts change.
  • Pair with paste redact if the file might contain sample keys or internal paths.

Common mistakes to avoid

  • Trusting YAML parsing here for complex blocks

    Multiline folded scalars and lists are only partially recognized. Treat key detection as a hint, not a schema validator.

  • Pasting production secrets

    Even structure checks are safer on redacted copies—rotate anything that was ever exposed.

FAQ

Does this validate against Cursor’s exact schema?

No. It applies lightweight heuristics aligned with common SKILL.md and .mdc patterns. Your editor remains the source of truth.

Is my file uploaded?

No. Everything stays in your browser tab.

Common search terms

Phrases people search for that match this tool. See the full long-tail keyword index.

  • cursor skill md checker
  • agent skill file validator

More tools

Related utilities you can open in another tab—mostly client-side.