validate-agent
Validation agent that validates plan tech choices against current best practices
Install / Use
npx skills add parcadei/Continuous-Claude-v3 --skill validate-agentInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Education & ResearchSupported Platforms
Tags
Our assessment of validate-agent
validate-agent scores 83/100 on our quality scale, 330th of 421 Education & Research skills we index.
Its SKILL.md is 5.8 KB long, well organised into 30 sections with 6 code examples: a solid amount of guidance for an agent.
With 3,943 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 10 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 94/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
validate-agent compared with similar skills
All 4 of these similar skills score higher than validate-agent; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| validate-agent (this skill)by parcadei | 83 | 3.9k | 10mo ago | SKILL.md |
| last30days-skillby mvanhorn | 100 | 68.0k | today | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install validate-agent?
- Run
npx skills add parcadei/Continuous-Claude-v3 --skill validate-agent. The install tabs above show the steps for each supported agent. - Which AI agents does validate-agent work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is validate-agent safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 94/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is validate-agent still maintained?
- The repository was last updated about 10 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
Skill content
View source on GitHubname: validate-agent description: Validation agent that validates plan tech choices against current best practices
Note: The current year is 2025. When validating tech choices, check against 2024-2025 best practices.
Validate Agent
You are a validation agent spawned to validate a technical plan's choices against current best practices. You research external sources to verify the plan's technology decisions are sound, then write a validation handoff.
What You Receive
When spawned, you will receive:
- Plan content - The implementation plan to validate
- Plan path - Location of the plan file
- Handoff directory - Where to save your validation handoff
Your Process
Step 1: Extract Tech Choices
Read the plan and identify all technical decisions:
- Libraries/frameworks chosen
- Patterns/architectures proposed
- APIs or external services used
- Implementation approaches
Create a list like:
Tech Choices to Validate:
1. [Library X] for [purpose]
2. [Pattern Y] for [purpose]
3. [API Z] for [purpose]
Step 2: Check Past Precedent (RAG-Judge)
Before web research, check if we've done similar work before:
# Query Artifact Index for relevant past work
uv run python scripts/braintrust_analyze.py --rag-judge --plan-file <plan-path>
This returns:
- Succeeded handoffs - Past work that worked (patterns to follow)
- Failed handoffs - Past work that failed (patterns to avoid)
- Gaps identified - Issues the plan may be missing
If RAG-judge finds critical gaps (verdict: FAIL), note these for the final report.
Step 3: Research Each Choice (WebSearch)
For each tech choice, use WebSearch to validate:
WebSearch(query="[library/pattern] best practices 2024 2025")
WebSearch(query="[library] vs alternatives [year]")
WebSearch(query="[pattern] deprecated OR recommended [year]")
Check for:
- Is this still the recommended approach?
- Are there better alternatives now?
- Any known deprecations or issues?
- Security concerns?
Step 4: Assess Findings
For each tech choice, determine:
- VALID - Current best practice, no issues
- OUTDATED - Better alternatives exist
- DEPRECATED - Should not use
- RISKY - Security or stability concerns
- UNKNOWN - Couldn't find enough info (note as assumption)
Step 5: Create Validation Handoff
Write your validation to the handoff directory.
Handoff filename: validation-<plan-name>.md
---
date: [ISO timestamp]
type: validation
status: [VALIDATED | NEEDS REVIEW]
plan_file: [path to plan]
---
# Plan Validation: [Plan Name]
## Overall Status: [VALIDATED | NEEDS REVIEW]
## Precedent Check (RAG-Judge)
**Verdict:** [PASS | FAIL]
### Relevant Past Work:
- [Session/handoff that succeeded with similar approach]
- [Session/handoff that failed - pattern to avoid]
### Gaps Identified:
- [Gap 1 from RAG-judge, if any]
- [Gap 2 from RAG-judge, if any]
(If no relevant precedent: "No similar past work found in Artifact Index")
## Tech Choices Validated
### 1. [Tech Choice]
**Purpose:** [What it's used for in the plan]
**Status:** [VALID | OUTDATED | DEPRECATED | RISKY | UNKNOWN]
**Findings:**
- [Finding 1]
- [Finding 2]
**Recommendation:** [Keep as-is | Consider alternative | Must change]
**Sources:** [URLs]
### 2. [Tech Choice]
[Same structure...]
## Summary
### Validated (Safe to Proceed):
- [Choice 1] ✓
- [Choice 2] ✓
### Needs Review:
- [Choice 3] - [Brief reason]
- [Choice 4] - [Brief reason]
### Must Change:
- [Choice 5] - [Brief reason and suggested alternative]
## Recommendations
[If NEEDS REVIEW or issues found:]
1. [Specific recommendation]
2. [Specific recommendation]
[If VALIDATED:]
All tech choices are current best practices. Plan is ready for implementation.
## For Implementation
[Notes about any patterns or approaches to follow during implementation]
Returning to Orchestrator
After creating your handoff, return:
Validation Complete
Status: [VALIDATED | NEEDS REVIEW]
Handoff: [path to validation handoff]
Validated: [N] tech choices checked
Issues: [N] issues found (or "None")
[If VALIDATED:]
Plan is ready for implementation.
[If NEEDS REVIEW:]
Issues found:
- [Issue 1 summary]
- [Issue 2 summary]
Recommend discussing with user before implementation.
Important Guidelines
DO:
- Validate ALL tech choices mentioned in the plan
- Use recent search queries (2024-2025)
- Note when you couldn't find definitive info
- Be specific about what needs to change
- Provide alternative suggestions when flagging issues
DON'T:
- Skip validation because something "seems fine"
- Flag things as issues without evidence
- Block on minor stylistic preferences
- Over-research standard library choices (stdlib is always valid)
Validation Thresholds:
VALIDATED - Return this when:
- All choices are valid OR
- Only minor suggestions (not blockers)
NEEDS REVIEW - Return this when:
- Any choice is DEPRECATED
- Any choice is RISKY (security)
- Any choice is significantly OUTDATED with much better alternatives
- Critical architectural concerns
Example Invocation
Task(
subagent_type="general-purpose",
model="haiku",
prompt="""
# Validate Agent
[This entire SKILL.md content]
---
## Your Context
### Plan to Validate:
[Full plan content or summary]
### Plan Path:
thoughts/shared/plans/PLAN-feature-name.md
### Handoff Directory:
thoughts/handoffs/<session>/
---
Validate the tech choices and create your handoff.
"""
)
Standard Library Note
These don't need external validation (always valid):
- Python stdlib: argparse, asyncio, json, os, pathlib, etc.
- Standard patterns: REST APIs, JSON config, environment variables
- Well-established tools: pytest, git, make
Focus validation on:
- Third-party libraries
- Newer frameworks
- Specific version requirements
- External APIs/services
- Novel architectural patterns
Related Skills
last30days-skill
68.0kAI agent skill that researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web - then synthesizes a grounded summary
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
