Evidence-backed validation framework for AI agents, Cursor skills, MCP orchestrations, subagent graphs, hooks, and agentic repos — before deployment, not after.
| Field | Value |
|---|---|
| Framework ID | FW-001 |
| Full name | BlankVisuals© Validator |
| Version | v1.0.2 |
| Date registered | 2026-05-20 |
| Domain package | cursor-skills |
| Method | precise & verify — every rule needs verified evidence or INCONCLUSIVE |
| License | MIT |
BlankVisuals© Validator is an open-source AI agent validation framework built as a Cursor Agent Skill.
When invoked, the agent:
- Discovers your target (repo or agent built on FW-001)
- Resolves validation rules (your spec → repo
VALIDATION.md→ built-in catalog) - Runs checks in parallel where safe, then dependent checks (topology, E2E)
- Records verified evidence per rule (commands, file citations, tool results)
- Delivers a validation canvas plus a short chat summary
It does not guess pass/fail. Unverified items are marked INCONCLUSIVE, not PASS.
Clone or copy this folder into your Cursor skills directory:
git clone https://github.com/cengicadis/blankvisuals-validator ~/.cursor/skills/blankvisuals-validatorCursor loads skills from ~/.cursor/skills/ automatically when the skill description matches your request.
Copy into a project:
your-project/.cursor/skills/blankvisuals-validator/
Commit SKILL.md, reference.md, and .gitignore with your project if the team should share the same validation workflow.
.vscode/launch.jsonand.vscode/*.code-workspace— local only (ignored via.gitignore).DS_Store— macOS metadata (ignored)
.vscode/settings.json— project-only keys; no personal editor prefs (v1.0.2+)
- Open the repo or agent you want to validate in Cursor.
- In chat, ask for validation, for example:
- "Run BlankVisuals validator on this repo"
- "Validate this agent against FW-001"
- "Validate this MCP orchestration against FW-001"
/validatethis orchestration workflow
- Review the canvas (
canvases/blankvisuals-validation-<target>.canvas.tsx) and the chat summary.
The agent stamps framework meta (FW-001) at the start and sets validation confirmation only after evidence is complete.
| Document | Purpose |
|---|---|
| docs/USAGE.md | Step-by-step usage, prompts, deliverables, custom rules |
| SKILL.md | Agent orchestration workflow (for the skill itself) |
| reference.md | Full rule catalog (STR, TOP, CON, SEC, RUN, …) |
Full documentation available on the GitHub Wiki:
| Page | What you'll find |
|---|---|
| Getting Started | Install, first run, example prompts |
| How It Works | Architecture, six domains, evidence standard |
| Rule Catalog | Every rule with check, pass, and fail conditions |
| Framework Types | How to classify your target |
| Custom Rules | VALIDATION.md format and examples |
| Troubleshooting | Common issues and fixes |
blankvisuals-validator/
├── SKILL.md # Cursor skill — orchestration & evidence standards
├── reference.md # FW-001 rule catalog & taxonomy (canonical)
├── VALIDATION.md # Repo verify spec (RUN-01)
├── scripts/
│ └── verify.sh # Structure verify command
├── docs/
│ └── USAGE.md # Human-facing usage guide
├── .gitignore
├── LICENSE
└── README.md # This file
Canonical rules: reference.md. Verify: bash scripts/verify.sh (see VALIDATION.md).
Validate any AI agent, prompt workflow, or agentic repo against a structured rule catalog with verified evidence per finding.
Supported targets:
- Skill chains (
SKILL.md, skill frontmatter) - Hook pipelines (
hooks.json) - Subagent graphs (Task tool, resume/interrupt)
- MCP orchestration
@cursor/sdkautomation- Plugin marketplace layouts (
.cursor-plugin, manifests)
See Framework taxonomy in reference.md.
Add a repo-level spec so validation matches your project:
VALIDATION.md(repo root), ordocs/validation.md, or.cursor/validation/
Format and examples: docs/USAGE.md#custom-validation-rules.
| Deliverable | Location / format |
|---|---|
| Validation canvas | canvases/blankvisuals-validation-<slug>.canvas.tsx |
| Chat summary | Markdown in chat (FW-001 meta, pass/fail counts, critical IDs) |
| Evidence | Per-rule YAML blocks (command / file / tool) |
- Claiming
PASSwithout command output or file citations - Setting
validation_confirmationbefore checks finish - Using markdown tables instead of a canvas for the main report
- Validating
~/.cursor/skills-cursor/(reserved)
Bump the patch version on each release (1.0.0 → 1.0.1 → 1.0.2 → …) in SKILL.md, reference.md, README.md, docs/USAGE.md, and VALIDATION.md. See CHANGELOG.md.
MIT — see LICENSE. Free to use, modify, and distribute with attribution.
BlankVisuals© Validator · Framework FW-001 · registered 2026-05-20.