Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →viryazheng/geo-review-html
Render an interactive, self-contained HTML companion for a GEO content brief (04-content-brief) or a publish-ready draft (05-production), so a NON-technical client reviewer (founder, organizer staff, the domain expert filling slots) can fill REQUIRED-FILL slots, leave section-level comments, and approve/return work in the browser instead of editing Markdown.
Passed 15 of 19 test cases with the skill, and 3 of 19 without it.
and 17 more in the full report
14 fixed3 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which file in the skill directory owns the browser state machine, localStorage auto-save, JSON export button logic, and progress counter for client reviews?
| Checked | Without skill | With skill |
|---|---|---|
| Locates fixed state machine and export logic inside templates/review.html | Missed | Passed |
The instructions your model reads when the skill loads.
The Markdown briefs/drafts are right for the GEO operator; they are awkward for the client side. This skill renders a companion HTML alongside the Markdown so non-technical reviewers can work in the browser. Battle-tested in the SEA-CICSIC 9-draft batch (see issue #1).
Division of labour (do not blur this):
templates/review.html owns localStorage
auto-save, JSON export, the progress counter, comment toggles, and the
approve/return state machine. It is correct as written; do not regenerate
it per run.frontend-design skill applies. When a client wants a branded or more
distinctive look, restyle the <style> block of templates/review.html
using frontend-design principles. --accent is already overridable per
client via brand_context (see below); deeper restyling edits the CSS.render_html.py only parses Markdown + meta into a payload and injects it.04-content-brief Step 7 — emit briefs/<id>.html (fill-form) next to the .md.04-content-brief Step 9 — ingest the reviewer's returned *.feedback.json.05-production Step 7 — emit drafts/<id>.html (review form) next to the .md.briefs/index.html entry page needs (re)building.SK=plugins/recomby-geo/skills/geo-review-html
# Flavor A — fill-form HTML for a brief with REQUIRED-FILL slots
python3 $SK/scripts/render_html.py --mode brief \
--md clients/<slug>/briefs/<id>.md \
--meta clients/<slug>/briefs/<id>.meta.json \
--brand clients/<slug>/brand_context.json \
--out clients/<slug>/briefs/<id>.html
# Flavor B — review HTML for a publish-ready draft (section comments + approve)
python3 $SK/scripts/render_html.py --mode draft \
test cases passed, vs 3 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.