validate-all — for Claude Code validate-all, x-deep-os, community, for Claude Code, ide skills, xdeep-engineering, auto-fix, enhancement, blueprint, scaffold

v1.0.0
GitHub

Об этом навыке

Подходящий сценарий: Ideal for AI agents that need /validate-all — run all x-deep validators. Локализованное описание: Multi-agent coordination, knowledge compilation, self-healing loops. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Возможности

/validate-all — Run all X-DEEP validators
Single entry point to verify the X-DEEP architecture is healthy.
Owned by the xdeep-engineering agent.
When this skill is invoked
Before any commit touching .agent/ or .claude/skills/

# Core Topics

for Claude Code xdeep-engineering auto-fix enhancement blueprint scaffold
ysgdepaula ysgdepaula
[0]
[0]
Updated: 4/14/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
49
Canonical Locale
en
Detected Body Locale
en

Подходящий сценарий: Ideal for AI agents that need /validate-all — run all x-deep validators. Локализованное описание: Multi-agent coordination, knowledge compilation, self-healing loops. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Зачем использовать этот навык

Рекомендация: validate-all helps agents /validate-all — run all x-deep validators. Multi-agent coordination, knowledge compilation, self-healing loops. This AI agent skill supports Claude Code, Cursor, and Windsurf

Подходит лучше всего

Подходящий сценарий: Ideal for AI agents that need /validate-all — run all x-deep validators.

↓ Реализуемые кейсы использования for validate-all

Сценарий использования: Applying /validate-all — Run all X-DEEP validators
Сценарий использования: Applying Single entry point to verify the X-DEEP architecture is healthy
Сценарий использования: Applying Owned by the xdeep-engineering agent

! Безопасность и ограничения

  • Ограничение: If a fix requires changing schemas: stop and propose, don't modify schemas autonomously
  • Ограничение: Requires repository-specific context from the skill documentation
  • Ограничение: Works best when the underlying tools and dependencies are already configured

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is validate-all?

Подходящий сценарий: Ideal for AI agents that need /validate-all — run all x-deep validators. Локализованное описание: Multi-agent coordination, knowledge compilation, self-healing loops. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install validate-all?

Run the command: npx killer-skills add ysgdepaula/x-deep-os/validate-all. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for validate-all?

Key use cases include: Сценарий использования: Applying /validate-all — Run all X-DEEP validators, Сценарий использования: Applying Single entry point to verify the X-DEEP architecture is healthy, Сценарий использования: Applying Owned by the xdeep-engineering agent.

Which IDEs are compatible with validate-all?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for validate-all?

Ограничение: If a fix requires changing schemas: stop and propose, don't modify schemas autonomously. Ограничение: Requires repository-specific context from the skill documentation. Ограничение: Works best when the underlying tools and dependencies are already configured.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ysgdepaula/x-deep-os/validate-all. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use validate-all immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

validate-all

Multi-agent coordination, knowledge compilation, self-healing loops. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows. /validate-all —

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

/validate-all — Run all X-DEEP validators

Single entry point to verify the X-DEEP architecture is healthy. Owned by the xdeep-engineering agent.

When this skill is invoked

  • Before any commit touching .agent/ or .claude/skills/
  • Before opening a PR with auto-fix, enhancement, or blueprint label
  • On demand when the user suspects drift
  • By /scaffold as part of its step 4

What it runs

Core validators (always)

bash
1node .agent/scripts/validate-all.mjs

This runs:

  • validate-state.mjs — checks .agent/state.json structure, no duplicates
  • validate-templates.mjs — all .agent/templates/*.yaml parse + schema + cross-ref state
  • validate-skills.mjs — all .claude/skills/*/SKILL.md frontmatter valid + unique names

Project checks (if relevant files changed)

  • telegram-bot/ changed → cd telegram-bot && npm run lint
  • dashboard/ changed → cd dashboard && npm run lint && npx tsc --noEmit && npm test
  • sales-tool/ changed → cd sales-tool && npm run lint

Expected output format

Success case:

✅ All validators passed

Core:
- state.json: OK
- templates: OK (10 agents)
- skills: OK (15 skills)

Projects checked: telegram-bot (lint OK)

Failure case:

❌ Validation failed (2 errors)

Core errors:
- .agent/templates/xdeep-sales.yaml: reports_to references non-existent agent
- .claude/skills/foo/SKILL.md: frontmatter missing required field 'name'

Project errors:
- telegram-bot lint: 3 warnings, 1 error in src/index.mjs

Suggested next step: fix errors above, then re-run /validate-all

Guardrails

  • NEVER commit if validation fails
  • If validator script itself errors (not a validation failure): escalate to the user
  • If a fix requires changing schemas: stop and propose, don't modify schemas autonomously

Связанные навыки

Looking for an alternative to validate-all or another community skill for your workflow? Explore these related open-source skills.

Показать все

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
Искусственный интеллект

widget-generator

Logo of f
f

Создание настраиваемых плагинов виджетов для системы ленты новостей prompts.chat

★ 149.6k
⑂ 0
Искусственный интеллект

flags

Logo of vercel
vercel

Фреймворк React

★ 138.4k
⑂ 0
Браузер

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Разработчик