asae-render

Renders structured passes[] YAML frontmatter into canonical ASAE audit log prose sections.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill asae-render-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asae-render
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/asae-render
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill asae-render-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Audit logs that keep structured YAML frontmatter and hand-written prose sections can drift apart, breaking consistency and failing enforcement checks. This Skill generates the canonical prose body directly from the structured passes[] block so the two representations always match. ## Core Features & Use Cases - Canonical rendering: Converts a passes[] YAML frontmatter block into standardized Pass-section markdown with required-phrase markers for Tier 1b satisfaction. - Check mode: Compares an audit log's actual prose body against the canonical rendered output and emits a PASS/FAIL diagnostic. - Migration support: Helps convert legacy prose-pattern audit logs to the structured-frontmatter form by rendering replacement prose. - Use Case: When authoring a new ASAE gate audit log, write the passes[] block in frontmatter first, then run the render to produce the prose body and paste it into the log before committing. ## Quick Start Ask the assistant to run asae-render on a specific audit log file to generate its canonical Pass-section prose from the structured frontmatter.

Frequently Asked Questions about asae-render

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

FAQPage Schema
How do I render an ASAE audit log from structured YAML frontmatter?

Invoke the skill with the audit log path; it extracts the passes[] block from frontmatter and emits canonical Pass-section markdown to stdout. You then replace the existing prose section using an edit tool and commit.

How do I migrate a legacy prose-pattern audit log to structured form?

Hand-author a passes[] block in the frontmatter mirroring the existing prose, run the render to produce canonical output, diff it against the old prose, replace the Pass section, and commit so Tier 37 verifies equivalence.

What happens if an audit log has no passes[] block?

The renderer is a no-op for logs without a passes[] block: the library script emits an INFO-skip message and exits 0, and the skill reports that the legacy prose-pattern log has nothing to render.

Does asae-render modify audit log files automatically?

No. The skill only emits rendered prose to stdout or a PASS/FAIL diagnostic in check mode; the user applies changes manually with Edit or Write tools. Auto-modification is an explicit refusal.

What are the limitations of the v01 renderer?

The v01 library script renders stub-only prose with headers and required-phrase markers, not full per-item tables. There is no scaffold mode, check mode is line-normalized rather than full-fidelity, and no fixture-test corpus exists yet.