Skip to content
SkillModel-led389 tokens in use

html-plan

Turns a plan, roadmap or rollout into one self-contained HTML file that keeps your commitments recognizable and shows sequence, owners and dependencies where they are real.

4,275 stars on the repository MIT Licenseplannotator/effective-html · skills/html-plan
npx skills add plannotator/effective-html
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing html-plan costs

60tokens idle
389tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Fair
  • Frontmatter12/15
  • Structure8/25
  • Examples0/15
  • Output15/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Fair
  • Development activity60
  • Maintenance24
  • Community48
  • Maturity24
  • Momentum40

html-plan is a specialist skill for plans people need to inspect and act on. It keeps the user’s scope, ordering, commitments and terminology, and improves hierarchy and structure without inflating an implementation plan into a strategy document.

The agent decides what the plan needs, such as phases, owners, dependencies, risks and acceptance checks, and adds nothing the source does not support. It delivers one responsive, accessible HTML file and notes any structural interpretation it introduced.

What You Get

  • One self-contained HTML plan with semantic headings, lists, tables and landmarks
  • Source commitments kept recognizable, with accepted decisions apart from assumptions and open questions
  • Sequence and dependency shown only where they exist in the source
  • A check that no commitment was dropped and stages stay in the intended order

Common Use Cases

  • Rendering an implementation plan so reviewers can see phases and owners at a glance
  • Presenting a rollout with risks and acceptance checks
  • Cleaning up a roadmap draft without changing what it promises
  • Giving a team a readable version of a long planning document

What Makes It Unique

It treats source material as binding. The skill forbids adding a timeline, progress percentage, status badge or dashboard summary unless the source supports it, and it keeps long prose readable without forcing every paragraph into a card. When design-artifact is installed, creative direction is allowed but cannot override traceability.

Under The Hood

The skill is a single instruction file with no scripts. The agent reads your plan and project files and writes one HTML file to your workspace, then inspects it in a browser at wide and narrow widths to check ordering, ownership and overflow. The instructions avoid external services and do not call the network.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers