How do I install the Validate skill?

Run npx skillmds@latest add tomevault-io/validate-13 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Validate safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Validate?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Validate free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Validate?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Validate by tomevault-io — Agent Skill

Name: Validate
Author: tomevault-io

Validate

Activate when checking if work meets requirements, verifying completion criteria, validating file placement, or ensuring quality standards. Use before marking work complete to verify success criteria are met. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Validation Skill

Validate AgentTask completion against success criteria and project standards.

When to Use

Checking if work meets all requirements
Validating file placement rules
Ensuring quality standards before completion
Reviewing subagent work output

Required Checks

Success criteria satisfied
File placement rules followed
ALL-CAPS file names avoided (except allowlist)
Summary/report files only in summaries/
Memory updated when new knowledge created

File Placement Validation

File Type	Required Location
Summaries/Reports	`summaries/`
Stories/Epics	`stories/`
Bugs	`bugs/`
Memory	`memory/`
Documentation	`docs/`

NEVER place:

Summaries in docs/ or project root
Memory entries outside memory/
Reports anywhere except summaries/

ALL-CAPS Allowlist

These files ARE allowed to be ALL-CAPS:

README.md, LICENSE, LICENSE.md
CLAUDE.md, SKILL.md, AGENTS.md
CHANGELOG.md, CONTRIBUTING.md
AUTHORS, NOTICE, PATENTS, VERSION
MAKEFILE, DOCKERFILE, COPYING, COPYRIGHT

Summary Validation

Every summary/completion must include:

What changed - concrete list of modifications
Why it changed - rationale/requirements addressed
How it was validated - tests or checks performed
Risks or follow-ups - any remaining concerns

Validation Checklist

Before marking AgentTask complete:

- [ ] All success criteria met
- [ ] Changes match requested scope (no over-engineering)
- [ ] File placement rules followed
- [ ] Documentation updated as needed
- [ ] Git operations completed
- [ ] Summary is factual and complete

Validation Ownership

Executing subagent: Performs initial validation
Main agent: Reviews and confirms validation
Hook system: Enforces file placement automatically

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: validate-13description: Activate when checking if work meets requirements, verifying completion criteria, validating file placement, or ensuring quality standards. Use before marking work complete to verify success criteria are met. Use when this capability is needed.---# Validation SkillValidate AgentTask completion against success criteria and project standards.## When to Use- Checking if work meets all requirements- Validating file placement rules- Ensuring quality standards before completion- Reviewing subagent work output## Required Checks- [ ] Success criteria satisfied- [ ] File placement rules followed- [ ] ALL-CAPS file names avoided (except allowlist)- [ ] Summary/report files only in `summaries/`- [ ] Memory updated when new knowledge created## File Placement Validation| File Type | Required Location ||-----------|------------------|| Summaries/Reports | `summaries/` || Stories/Epics | `stories/` || Bugs | `bugs/` || Memory | `memory/` || Documentation | `docs/` |**NEVER place:**- Summaries in `docs/` or project root- Memory entries outside `memory/`- Reports anywhere except `summaries/`## ALL-CAPS AllowlistThese files ARE allowed to be ALL-CAPS:- README.md, LICENSE, LICENSE.md- CLAUDE.md, SKILL.md, AGENTS.md- CHANGELOG.md, CONTRIBUTING.md- AUTHORS, NOTICE, PATENTS, VERSION- MAKEFILE, DOCKERFILE, COPYING, COPYRIGHT## Summary ValidationEvery summary/completion must include:- **What changed** - concrete list of modifications- **Why it changed** - rationale/requirements addressed- **How it was validated** - tests or checks performed- **Risks or follow-ups** - any remaining concerns## Validation ChecklistBefore marking AgentTask complete:```- [ ] All success criteria met- [ ] Changes match requested scope (no over-engineering)- [ ] File placement rules followed- [ ] Documentation updated as needed- [ ] Git operations completed- [ ] Summary is factual and complete```## Validation Ownership- **Executing subagent**: Performs initial validation- **Main agent**: Reviews and confirms validation- **Hook system**: Enforces file placement automatically---> Converted and distributed by [TomeVault](https://tomevault.io/claim/intelligentcode-ai) — claim your Tome and manage your conversions.

Frequently asked questions