Instruction & rule draft check

Client

Paste a Markdown instruction file or project rule document to see frontmatter keys, ## section count, and length hints. Use with the prompt checklist when tuning instructions inside the body.

What we look for

Many files use name and description in YAML frontmatter. Rule-style drafts sometimes add globs (path patterns) or scope flags. The body should usually include ## sections so readers can scan quickly. Very long files are flagged so you can split or link out instead of pasting an entire policy in one place.

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

Nearby workflows on Toolcore

Common use cases

  • Sanity-check an instruction or rule document before saving—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 a fixed schema or my editor’s rules?

No. It only applies simple structure heuristics for typical Markdown instruction files. Your team or tool 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.

  • markdown instruction file structure check
  • agent rule draft validator offline

More tools

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