Rewrite artifact UIP headers to Phoenix Protocol v13.0 compliance.
npx skills add https://github.com/Icebane84/Synarche_Workshop --skill reforge-icebane84
Please help me install this Agent Skill. Skill: reforge Source: https://github.com/Icebane84/Synarche_Workshop/tree/main/.agent/skills/reforge Command: npx skills add https://github.com/Icebane84/Synarche_Workshop --skill reforge-icebane84
Reforging prevents inconsistent or outdated artifact headers from breaking discovery, governance indexing, and protocol compliance across the v13.0 ecosystem.
Tell the AI to reforge artifacts to v13.0 by running the reforge_artifact tool on the target file you want standardized.
High-intent search queries and answers about installing and using this skill.
To standardize artifact headers to Phoenix Protocol v13.0, run the reforge_artifact tool on your target file. It reads the existing file, extracts current UIP fields, and rewrites it in place with a compliant v13.0 header containing integrity and provenance defaults.
Metadata rewriting for v13.0 protocol compliance updates artifact headers with canonical UIP metadata, including artifact id, official name, version, domain, evolution, status, and relations. This ensures consistent governance indexing and discovery across the v13.0 workspace.
Yes, v13.0 refactoring supports automatic domain inference from filepaths. It reads directory cues like governance, logs, philosophy, or creative, and normalizes the inferred domain into the allowed v13.0 domains during the header rewriting process.
The best way to normalize metadata for bulk documentation collections is using the reusable bulk tooling pattern. This supports deterministic reprocessing of documentation or protocol artifacts, allowing teams to standardize large collections consistently before indexing.
You do not need existing UIP fields to reforge a file to v13.0. The tool reads the existing artifact file, extracts any current UIP fields if present, and generates a fully compliant v13.0 header with default integrity and provenance metadata.
Inconsistent artifact metadata breaks governance indexing because outdated or non-canonical headers prevent proper discovery and protocol compliance across the v13.0 ecosystem. Reforging standardizes these headers to ensure deterministic indexing and consistent workspace governance.
Icebane84Audit Markdown and Python files against Phoenix Protocol v13.0 standards.
grtninjaIndex ultra-large repositories with sharded, budgeted mass-indexing and JSON run outputs.
ldilovLoad the canonical Go engineering skill surface for project governance.
antigravityos187-sketchExecutes manual quality and safety checks for the Taco Bell brand.
