meta-polisher-validator

Validate meta-skill integrity across .codex and .claude flavors with skill-polisher verify mode.

Updated Nov 30, 2025
One-click install
npx skills add https://github.com/poisontr33s/chthonic-archive --skill meta-polisher-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-polisher-validator
Source: https://github.com/poisontr33s/chthonic-archive/tree/main/.codex/skills/meta-polisher-validator
Command: npx skills add https://github.com/poisontr33s/chthonic-archive --skill meta-polisher-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Redirects meta-skill validation to the primary tool, enabling consistent checks through skill-polisher's verify mode.

Core Features & Use Cases

  • Delegates meta-skill validation to skill-polisher --mode verify for single-source consistency across flavors.
  • Ensures scope alignment, cross-flavor compatibility, and hook integrity via the polisher pipeline.
  • Documents provenance and equivalence to prior meta-polish validation approaches.

Quick Start

Run the polisher in verify mode to check meta-skill integrity across flavors.

Frequently Asked Questions about meta-polisher-validator

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

FAQPage Schema
How do I validate meta-skill integrity across multiple flavors?▼

To validate meta-skill integrity across flavors, run the polisher tool in verify mode. This enforces scope alignment and cross-flavor compatibility checks across both .codex and .claude skill sets.

What is the best way to ensure consistent scope checks for .codex and .claude skill sets?▼

Consistent scope checks for .codex and .claude skill sets are achieved by delegating validation to a single-source pipeline. Running skill-polisher in verify mode ensures hook integrity and equivalence across both flavors.

Can I use the polisher verify mode to check hook integrity and provenance?▼

Yes, polisher verify mode checks hook integrity and enforces REDIRECT provenance. It documents equivalence to prior validation approaches while applying cross-flavor checks to your meta-skills.

Why does meta-skill validation need to redirect to a primary tool?▼

Meta-skill validation redirects to a primary tool to enable single-source consistency. By using skill-polisher's verify mode, you ensure scope alignment and cross-flavor compatibility without relying on fragmented scripts.

Do I need any dependencies to run cross-flavor validation on meta-skills?▼

No dependencies are required to run cross-flavor validation on meta-skills. The process uses the built-in skill-polisher pipeline in verify mode to check scope alignment and hook integrity directly.