skills.rest
AlexKapadia
AlexKapadiaCOMMUNITY
Explore all skills by this author →
GitHub

revalidate-all

Re-run Pixie validation across all tools and summarize pass/warn/fail results.

6|1|Updated May 17, 2026
Search Tags:#automation#validation#qa#quality-assurance#validate#pixie
One-click install
npx skills add https://github.com/AlexKapadia/Pixie --skill revalidate-all
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: revalidate-all
Source: https://github.com/AlexKapadia/Pixie/tree/main/.claude/skills/revalidate-all
Command: npx skills add https://github.com/AlexKapadia/Pixie --skill revalidate-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Re-runs the Pixie validator across EVERY tool under tools/ and surfaces a per-tool pass/warn/fail summary. Use when auditing after a Pixie or Python upgrade, or whenever a full repo-wide validation is needed. Do NOT use for a single named tool (debug-tool) or Pixie's own health (pixie-doctor).

Core Features & Use Cases

  • Executes the validator for every tool discovered under tools with a tool.json.
  • Aggregates per-tool results into a concise pass/warn/fail summary for quick remediation.
  • Supports audit workflows after upgrades or health checks to verify repository-wide consistency.

Quick Start

Run a full system revalidation across all tools and review the resulting summary.

Frequently Asked Questions about revalidate-all

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a bulk validation check across all Pixie tools after a Python upgrade?▼

Run a full system revalidation by executing the Pixie validator across every tool with a tool.json under tools/, aggregating per-tool pass/warn/fail outputs into a concise summary table for quick remediation.

What is the best way to audit repository-wide tool health using Pixie?▼

Auditing repository-wide tool health requires iterating every tool under tools/, running uv run pixie validate <tool_id> --json for each, and rendering aggregated pass/warn/fail results into a concise table for remediation.

Can I validate a single named tool instead of running a full repository-wide health check?▼

No, this bulk validation is designed for full repository-wide health checks after upgrades and should not be used for a single named tool or checking Pixie's own internal health, which require different processes.

Does the Pixie validator output detailed JSON for every tool under tools/?▼

Yes, the validator executes uv run pixie validate <tool_id> --json for each discovered tool, parsing the detailed JSON output to aggregate and surface concise pass, warn, and fail statuses.

When should I avoid using automated bulk Pixie validation?▼

Avoid bulk validation when debugging a single named tool or diagnosing Pixie's own platform issues, as this process targets full repository-wide consistency audits after upgrades rather than isolated debugging.

Related Skills

Explore More Software Engineering Skills→
AlexKapadiaAlexKapadia
6

import-tool

Install a Pixie tool from a ZIP by unpacking under tools/ and validating with uv sync.

Community
Intermediate
seiggyseiggy
57

summarize-eval-results

Summarize AI agent evaluation JSON results into a markdown report.

Community
Intermediate
AlexKapadiaAlexKapadia
6

convert-gradio-app

Convert Gradio app scripts into Pixie tool.json contracts and wrappers.

Community
Intermediate
AlexKapadiaAlexKapadia
6

pixie-doctor

Diagnoses Pixie installation health across server, database, ports, dashboard, venv, Python, and uv versions.

Community
Advanced