Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI-coding power users, agent developers, automation builders, knowledge workers, technical writers, AI-curious readers, and any developer building a visual-artefact-generation workflow with an AI agent -- and who can pair effective-html with an Anthropic / OpenAI / DeepSeek / Xiaomi Mimo / Claude / GPT API key for the model surface, an SKILL.md-compatible agent (Claude Code, Codex, Curs
Who should use it
Who should skip it
Skip plannotator/effective-html if the source link, documentation, or setup requirements do not align with your current workflow or stack.
About this signal
plannotator/effective-html is tracked by RepoRadar as a 3 installable html skill primiti in the AI Agent Skills / Visual Artefact Generation section. It was first seen on 2026-07-06 and last updated on 2026-07-06. The current verdict is 'try now' with a Silver tier and easy setup difficulty. plannotator/effective-html leads on workflow potential (9.4) and setup ease (8.8); its lowest signal is maturity (5.8), so factor that in before investing setup time. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned plannotator/effective-html a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 1; 286* / 153 KB repo is at active maintenance but the maintainer is a small team (plannotator / backnotprop) -- treat the first evaluation cycle as a smoke test (install via `npx skills add plannotator/effective-html` + ask the agent to use the `html-plan` skill to render a plan as an HTML page + confirm the dark-mode primitive is applied + confirm the 20+ reference templates are available) before relying on the 3 skills in production; the dark-mode primitive relies on `prefers-color-scheme` and `localStorage` -- the consumer SHOULD test the dark-mode behavior in the consumer's environment; the `disable-model-invocation: true` frontmatter means the consumer MUST explicitly invoke the skill in their agent prompt (the agent will not auto-trigger the skill) -- the consumer SHOULD document the invocation pattern for their team.