policy-html-explainer
/policy-html-explainer
Turns policy documents into self-contained, accessible HTML explainers with clear structure and intact mandatory language. Use this skill when the user wants a policy as a shareable HTML page or printable explainer. Do not use when/for story-led markdown rewrites without HTML (use policy-story-explainer) or general marketing landing pages.
- Author
- jagreehal ↗
- Repository
- jagreehal-claude-skills ↗
- Licence
- MIT
- Last repository change
- 30.07.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Turns policy documents into self-contained, accessible HTML explainers with clear structure and intact mandatory language. Use this skill when the user wants a policy as a shareable HTML page or printable explainer. Do not use when/for story-led markdown rewrites without HTML (use policy-story-explainer) or general marketing landing pages.
Original author description
Turns policy documents into self-contained, accessible HTML explainers with clear structure and intact mandatory language. Use this skill when the user wants a policy as a shareable HTML page or printable explainer. Do not use when/for story-led markdown rewrites without HTML (use policy-story-explainer) or general marketing landing pages.
How it works
- Critical rules
- Workflow
- Resources
- Validation
- Constraints
SKILL.md preview
--- name: policy-html-explainer description: >- Turns policy documents into self-contained, accessible HTML explainers with clear structure and intact mandatory language. Use this skill when the user wants a policy as a shareable HTML page or printable explainer. Do not use when/for story-led markdown rewrites without HTML (use policy-story-explainer) or general marketing landing pages. version: 1.1.0 --- # Policy HTML Explainer ## Critical rules - Accuracy outranks aesthetics. Never soften `must`/`shall`, invent thresholds, or widen exceptions in text or diagram labels. - Inherit every accuracy rule from `policy-story-explainer` before styling. - One self-contained `.html` file: no network CSS/JS/fonts/images; opens offline; prints cleanly. - Show seams: verbatim policy, explanation, scenario, and "why" are visually distinct. - Diagrams restate rules already in text; never the only place a rule appears. - Before building, read [references/output-format.md](references/output-format.md), [references/design-system.md](references/design-system.md), and [references/diagrams.md](references/diagrams.md). Copy [assets/policy-template.html](assets/policy-template.html); do not hand-roll CSS. ## Workflow 1. Read the three reference files and start from the HTML template (mandatory). 2. Do content work exactly as `policy-story-explainer`: themes with five blocks (situation, meaning, verbatim policy, what to do, why). 3. Add a diagram only when it earns one (branches → decision tree; tiers → ladder; allow/deny → do/don't; deadlines → timeline). 4. Fill template: header, executive summary (long policies), TOC, themes, exceptions, review flags, understanding checklist. 5. Save as `<policy-slug>-explained.html` and give an open command (e.g. `open …`). 6. Run Validation. ## Resources - [references/output-format.md](references/output-format.md) — page structure. Read before filling the template. - [references/design-system.md](references/design-system.md) — visual rules and block styles. Read before styling. - [references/diagrams.md](references/diagrams.md) — SVG/CSS diagram patterns and a11y. Read before adding diagrams. - [assets/policy-template.html](assets/policy-template.html) — starting HTML/CSS. Copy as the base file. ## Validation - [ ] Single offline file; no external asset requests - [ ] Verbatim blocks distinct; mandatory language intact in text and diagrams - [ ] No invented numbers/branches; exceptions not widened - [ ] Every diagram rule also appears in text - [ ] Keyboard nav, heading order, contrast, print preview OK - [ ] Closing checklist confirms understanding of specific rules, not attendance ## Constraints - Ask if audience, branding, or "friendlier" wording could change meaning. - Content sibling: `policy-story-explainer` (use its examples for fidelity traps).
Files in this package (5)
- SKILL.md 3 KB
- assets/policy-template.html 19 KB
- references/design-system.md 4 KB
- references/diagrams.md 5 KB
- references/output-format.md 3 KB
Versions
The database has no other skills named policy-html-explainer.
Database snapshot: 13.11.2026 · package version f4ebca501855 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100policy-story-explainer
Rewrites long policy, compliance, HR, legal, or governance documents into accurate story-led explanations. Use this skill when the user wants a policy made relatable and scenario-based without watering down obligations. Do not use when/for HTML page packaging (use… - 100v1-html-it
Use when creating a self-contained HTML page, report, or interactive explainer. Triggers on "one-page dashboard", "shareable page", or "interactive report". - 100html-artifact
Generate beautiful, self-contained single-page HTML artifacts with impeccable, anti-slop design taste — documents, reports, specs, code-review explainers, research explainers, design explorations, and throwaway interactive editors. Shareable and openable in any browser. Optional… - 100visual-explainer
Build offline, self-contained HTML visual explainers for technical systems — hand-drawn SVG diagrams, step players/animations, and multi-page suites. Use when asked for an HTML diagram page, interactive visualization, architecture/flow animation, or a visual version of a long document. - 100visual-explainer
Create self-contained HTML visual explainers from technical material. Use this skill when diagrams, matrices, timelines, or browser artifacts beat plain text. - 100visual-explainer
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts.…