Agent skill

Cross Validate Artifacts

by shep-ai in shep-ai/shep

Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions.

MITAuto-check passedAgent Workflows

Install Cross Validate Artifacts

skills CLI
$ npx skills add shep-ai/shep --skill cross-validate-artifacts -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install shep-ai/shep cross-validate-artifacts --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/shep-ai/shep.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cross-validate-artifacts .claude/skills/cross-validate-artifacts && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cross-validate-artifacts
GitHub stars
264
Token cost
~2k tokens
SKILL.md length
573 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
MIT

At a glance

Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions.

  • Works in 5 steps: Identify Documentation Sources → Break Into Validation Categories → Launch Parallel Subagents → …
  • Users ask to cross-validate
  • SKILL.md covers Trigger, Arguments, Validation Process and Fixing Process, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cross Validate Artifacts is an agent skill from shep-ai/shep. Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate", "validate docs", "check documentation consistency", "audit documentation", or find conflicts/contradictions in docs. Supports automatic fixing with "validate and fix" argument. Runs parallel subagents for efficient validation across categories (domain-models, agent-system, tech-stack, architecture, cli-commands). Part of the Shep autonomous SDLC platform —…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering Subagents. The repository describes itself as: Ship features 10x faster. Built In Auto: Memory, K8S Agent & Security (SDD+SDLC) . 😇. The licence is MIT.

When your agent uses it

  • Users ask to cross-validate
  • Check documentation consistency
  • Audit documentation
  • Find conflicts/contradictions in docs

Example prompts

  • “cross-validate”
  • “validate docs”
  • “check documentation consistency”
  • “/cross-validate-artifacts”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify Documentation Sources
  2. Break Into Validation Categories
  3. Launch Parallel Subagents
  4. Compile Results
  5. Present or Fix

What it can do on your machine

Read from SKILL.md and the folder at commit 0304cfc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cross Validate Artifacts loads about 2k tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 573 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~138
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from shep-ai/shep at commit 0304cfc, republished under its MIT licence (© shep-ai). 573 words, ~2,038 tokens.

Download SKILL.mdSave it as .claude/skills/cross-validate-artifacts/SKILL.md (or your agent's skills folder).
name
cross-validate-artifacts
description
Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Use when users ask to "cross-validate", "validate docs", "check documentation consistency", "audit documentation", or find conflicts/contradictions in docs. Supports automatic fixing with "validate and fix" argument. Runs parallel subagents for efficient validation across categories (domain-models, agent-system, tech-stack, architecture, cli-commands). Part of the Shep autonomous SDLC platform — https://shep.bot
metadata.version
1.0.0
metadata.author
Shep AI (https://shep.bot)
metadata.homepage
https://shep.bot
metadata.repository
https://github.com/shep-ai/shep

Cross-Validate Artifacts Skill

Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions.

Trigger

Use this skill when the user:

  • Asks to "cross-validate", "validate docs", "check documentation consistency"
  • Wants to find conflicts or contradictions in documentation
  • Asks to audit or review documentation for accuracy
  • Uses /cross-validate-artifacts command

Arguments

  • No arguments: Perform validation and present results summary table, then ask user if they want to fix
  • validate and fix or fix: Perform validation AND automatically fix all issues found
  • --category <name>: Validate specific category only (domain-models, agent-system, tech-stack, architecture, cli-commands)

Validation Process

Step 1: Identify Documentation Sources

Gather all documentation files to validate:

Root docs:
- README.md
- CLAUDE.md
- AGENTS.md
- CONTRIBUTING.md

docs/ folder:
- docs/architecture/*.md
- docs/concepts/*.md
- docs/guides/*.md
- docs/development/*.md
- docs/api/*.md
Step 2: Break Into Validation Categories

Split validation into parallel sub-tasks for efficiency. Each category should be handled by a dedicated subagent:

CategoryDescriptionKey Files to Compare
domain-modelsEntity definitions, fields, enumsCLAUDE.md, docs/api/domain-models.md, docs/concepts/*.md
agent-systemAgent names, tools, state schema, workflowAGENTS.md, docs/architecture/agent-system.md, docs/guides/langgraph-agents.md
tech-stackFramework versions, library referencesREADME.md, CLAUDE.md, docs/architecture/overview.md
architectureLayer descriptions, folder structure, patternsCLAUDE.md, docs/architecture/*.md, CONTRIBUTING.md
cli-commandspnpm scripts, paths, configurationCLAUDE.md, docs/development/.md, docs/guides/.md
Step 3: Launch Parallel Subagents

CRITICAL: Use the Task tool with subagent_type=Explore to run validation categories in parallel.

Launch 5 subagents simultaneously:
1. Domain models validation subagent
2. Agent system validation subagent
3. Technology stack validation subagent
4. Architecture validation subagent
5. CLI commands validation subagent

Each subagent should:

  1. Read all relevant files for its category
  2. Compare definitions, names, values across files
  3. Identify discrepancies with exact file:line references
  4. Return structured list of issues found
Step 4: Compile Results

Aggregate all subagent results into a summary table:

markdown
## Validation Results Summary

### Critical Violations (Must Fix)

| #   | Category | Issue | Files Affected | Details |
| --- | -------- | ----- | -------------- | ------- |
| 1   | ...      | ...   | file.md:line   | ...     |

### High Priority Violations

| #   | Category | Issue | Files Affected | Details |
| --- | -------- | ----- | -------------- | ------- |

### Medium Priority Violations

...

### Consistent Items (No Issues)

| Category | Status     |
| -------- | ---------- |
| ...      | Consistent |
Step 5: Present or Fix

If no "fix" argument provided:

  1. Present the summary table to the user
  2. Ask: "Would you like me to fix these violations?"
  3. Wait for user confirmation before proceeding

If "fix" argument provided:

  1. Present the summary table
  2. Automatically proceed to fix all violations using parallel subagents

Fixing Process

Launch Fix Subagents in Parallel

For each category with violations, launch a dedicated fix subagent:

Task tool with subagent_type=general-purpose for each fix task:
- Fix agent system references (CrewAI → LangGraph)
- Fix domain model definitions (add missing fields/entities)
- Fix package manager references (npm → pnpm)
- Fix architecture descriptions
- Fix path references

Each fix subagent should:

  1. Read the file(s) needing fixes
  2. Apply minimal, targeted edits using the Edit tool
  3. Preserve existing formatting and structure
  4. Report what was changed
Show full SKILL.md (235 more words)Show less
Safety Guidelines for Fixes
  1. Read before edit: Always read the full file before making changes
  2. Minimal changes: Only fix the specific discrepancy, don't refactor
  3. Preserve style: Match existing formatting, indentation, tone
  4. No new content: Don't add features or documentation beyond fixing inconsistencies
  5. Verify after fix: Ensure the fix doesn't introduce new conflicts

Validation Checks by Category

Domain Models Checks
  • Entity fields match across CLAUDE.md, api/domain-models.md, concepts/*.md
  • Enum values consistent (SdlcLifecycle, TaskStatus, ArtifactType)
  • All entities documented (Feature, Task, ActionItem, Artifact, Requirement)
  • Field types match (string, number, arrays, etc.)
Agent System Checks
  • Framework name consistent (LangGraph vs CrewAI)
  • Agent/node naming consistent (class names vs function names)
  • State schema fields match across docs
  • Tool names consistent (snake_case tool names, camelCase variables)
  • Workflow stages match
Tech Stack Checks
  • Framework versions specified consistently
  • Library names match (Next.js, Vite, Vitest, etc.)
  • Package manager consistent (pnpm everywhere)
  • Database technology consistent (SQLite, LanceDB)
Architecture Checks
  • Layer names and hierarchy consistent
  • Folder structure matches across docs
  • Dependency rules documented consistently
  • Use case names match (PascalCase vs kebab-case)
CLI Commands Checks
  • pnpm script names consistent
  • Command descriptions match
  • Data paths consistent (~/.shep/repos/...)
  • Config file paths consistent
  • Port numbers consistent (3030)

Example Output

markdown
## Documentation Cross-Validation Results

### Critical Violations (4 issues)

| #   | Category      | Issue               | Files              | Details                                             |
| --- | ------------- | ------------------- | ------------------ | --------------------------------------------------- |
| 1   | agent-system  | CrewAI vs LangGraph | CLAUDE.md:59,106   | Uses "CrewAI-style" but implementation is LangGraph |
| 2   | cli-commands  | npm vs pnpm         | building.md:20-358 | Uses `npm run` instead of `pnpm`                    |
| 3   | domain-models | Missing entity      | CLAUDE.md          | Requirement entity not documented                   |
| 4   | agent-system  | Wrong naming        | CLAUDE.md:110-113  | Uses class names instead of node functions          |

### Consistent Items

| Category          | Status     |
| ----------------- | ---------- |
| Database (SQLite) | Consistent |
| Build tool (Vite) | Consistent |
| Data paths        | Consistent |

---

Would you like me to fix these violations?

Notes

  • Always use subagents for both validation and fixing to maximize efficiency
  • Present results in clean markdown tables for readability
  • Prioritize fixes by severity (Critical > High > Medium > Low)
  • After fixing, optionally re-run validation to confirm all issues resolved

© shep-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/cross-validate-artifacts of shep-ai/shep.

Open the folder on GitHubat commit 0304cfc

Compare with similar skills

Cross Validate Artifacts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cross Validate Artifacts compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cross Validate Artifacts this skillshep-ai/shep264—~2kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0
Subagent Driven DevelopmentAsvarox/allkaraoke26138 repos~1.2kAutomated safety check: PassNone
Dispatching Parallel Agentsultralisp/ultralisp25841 repos~1.5kAutomated safety check: PassNone
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
Task Observerrebelytics/one-skill-to-rule-them-all3.2k1 repos~12kAutomated safety check: PassCC-BY-4.0

Similar skills

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Subagent Driven Development

    Asvarox/allkaraoke

    A skill your agent uses when executing implementation plans with independent tasks in the current session

    261 GitHub starsUsed in 38 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • Dispatching Parallel Agents

    ultralisp/ultralisp

    A skill your agent uses when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    258 GitHub starsUsed in 41 repos~1.5k tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • Task Observer

    rebelytics/one-skill-to-rule-them-all

    Monitors task execution for skill improvement opportunities.

    3.2k GitHub starsUsed in 1 repo~12k tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from shep-ai/shep

  • React Flow

    shep-ai/shep

    React Flow (@xyflow/react) for workflow visualization with custom nodes and edges.

    264 GitHub stars~2.8k tokensUpdated 3 days ago
    Auto-check passed
  • Shep Workstreams

    shep-ai/shep

    A skill your agent uses when a large body of work (a version milestone, an epic, a roadmap, a set of PRDs/design docs) needs to be broken into parallel workstreams and executed with the shep CLI.

    264 GitHub stars~2.5k tokensUpdated 3 days ago
    Auto-check passed
  • A skill your agent uses when making architectural decisions, planning features, designing new components, reviewing PRs, or validating that proposed changes align with Clean Architecture principles.

    264 GitHub stars~808 tokensUpdated 3 days ago
    Auto-check passed
  • Tsp Model

    shep-ai/shep

    A skill your agent uses when creating, modifying, or documenting TypeSpec domain models.

    264 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Cross Validate Artifacts

What does Cross Validate Artifacts do?

Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions. Cross Validate Artifacts is an agent skill from shep-ai/shep. Cross-validate documentation and artifacts across the codebase for consistency, conflicts, and contradictions.

When should I use Cross Validate Artifacts?

Cross Validate Artifacts fits situations like: users ask to cross-validate; check documentation consistency; audit documentation; find conflicts/contradictions in docs.

How do I install Cross Validate Artifacts in Claude Code?

Run `npx skills add shep-ai/shep --skill cross-validate-artifacts -a claude-code`. Or copy the skill folder (.claude/skills/cross-validate-artifacts in shep-ai/shep) into .claude/skills/cross-validate-artifacts in your project. Claude Code loads it when a task matches its description.

How do I install Cross Validate Artifacts in Codex?

Run `npx skills add shep-ai/shep --skill cross-validate-artifacts -a codex`. Or copy the skill folder (.claude/skills/cross-validate-artifacts in shep-ai/shep) into .agents/skills/cross-validate-artifacts in your project. Codex loads it when a task matches its description.

Can I use Cross Validate Artifacts in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add shep-ai/shep --skill cross-validate-artifacts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cross-validate-artifacts, .gemini/skills/cross-validate-artifacts, .github/skills/cross-validate-artifacts and .opencode/skills/cross-validate-artifacts in your project.

What does Cross Validate Artifacts need to run?

SKILL.md names no scripts, command-line tools or credentials: Cross Validate Artifacts is instructions for the agent only.

Does Cross Validate Artifacts access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cross Validate Artifacts safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cross Validate Artifacts use?

Cross Validate Artifacts is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cross Validate Artifacts use?

About 2k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cross Validate Artifacts?

Skills that share tags, products or a category with Cross Validate Artifacts: Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars), Subagent Driven Development (Asvarox/allkaraoke, 261 stars), Dispatching Parallel Agents (ultralisp/ultralisp, 258 stars) and Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cross Validate Artifacts?

shep-ai (a GitHub organization) maintains it in shep-ai/shep, which has 264 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 5, 2026.

Source: shep-ai/shep on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.