pharaoh-tailor-review

Validate .pharaoh tailoring files against YAML schemas and cross-file references.

24|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-tailor-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pharaoh-tailor-review
Source: https://github.com/useblocks/pharaoh/tree/main/skills/pharaoh-tailor-review
Command: npx skills add https://github.com/useblocks/pharaoh --skill pharaoh-tailor-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing and validating .pharaoh/project tailoring files against JSON schemas and cross-file references to ensure internal coherence and readiness for use.

Core Features & Use Cases

  • Structure validation against id-conventions, workflows, artefact-catalog, and checklists frontmatter.
  • Cross-file consistency checks (e.g., every lifecycle state referenced exists in workflows, every artefact prefix is declared).
  • Generates a machine-readable result to guide tailoring improvements and audits.

Quick Start

Run pharaoh-tailor-review on the target tailoring directory to validate its correctness.

Frequently Asked Questions about pharaoh-tailor-review

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

FAQPage Schema
How do I validate tailoring files for cross-file consistency?

Cross-file consistency validation checks structural coherence against JSON schemas, verifying that every lifecycle state referenced exists in workflows and every artefact prefix is declared in the catalog.

What is the best way to audit YAML workflows and artefact catalogs?

Auditing YAML workflows and artefact catalogs requires schema validation to check frontmatter completeness, identifying violations and generating a machine-readable JSON payload with status and guidance.

Why does my tailoring file audit report missing artefact prefixes?

Tailoring file audits report missing artefact prefixes when cross-file checks detect references to prefixes that are not declared in the artefact-catalog frontmatter, indicating a structural inconsistency.

Does schema validation work for manually edited tailoring files?

Schema validation works for manually edited tailoring files by auditing structural coherence and cross-file consistency, ensuring id-conventions, workflows, and checklists frontmatter remain complete and coherent.

When do I need to run a tailoring file consistency check?

A tailoring file consistency check is needed after filling or manually editing tailoring files, ensuring id-conventions, workflows, artefact-catalog, and checklists frontmatter are coherent and ready for use.