Skip to content

v0.7.0 — Block Runner ships a skill

Choose a tag to compare

View all tags
@noeltock noeltock released this 06 Aug 05:53
· 126 commits to main since this release
v0.7.0
5d14108

Block Runner now ships a skill. Agents get markedly better conversions when told how to
use the tool, so the instructions travel with the package instead of being rediscovered by
every consumer.

npx block-runner skill              # print the guide — nothing installed or written
npx block-runner skill --install    # install it as a skill

Measured on the project's own 53-fixture benchmark, the guide takes the corpus from 28 to
97, with 0 invalid and 0 fallbacks. Those figures come from a controlled harness rather than
a live session, so treat them as a ceiling.

Added

  • The skill, shipped in the package and readable by any harness. skill/GUIDE.md is the
    content; skill/SKILL.md is a thin wrapper over it. skill --install writes both into
    .claude/skills/block-runner/, with --dir for harnesses that keep skills elsewhere. The
    guide covers which command to reach for, the block mappings per section type, the
    validate/fix loop, and how to fail safely without stranding the user.
  • assemble — build blocks from a described structure, not from markup. The command the
    skill drives. Give it an intent tree (JSON naming which blocks go where) and it builds the
    result with createBlock, so the output cannot be invalid. Describing a structure suits a
    model far better than authoring block markup, which is where invalid output comes from.
    Also available as assemble / extractIntent / realize library exports.
  • A hint when a conversion falls back. A convert run that drops to Custom HTML now says
    so on stderr and in report.hint, pointing at the path that usually handles that input
    cleanly. It is advisory: it never affects the exit code, the summary counts, or --strict.

Changed

  • Media resolution and brand-token repair are shared by every path. convert and
    assemble now run the same finalization, so a tree built from intent resolves images and
    maps colours onto theme presets exactly as a converted one does.

Notes

  • --styling and --css-out do not apply to assemble and are rejected with an explanation:
    an intent tree carries structure and content, never the source CSS. Use convert when the
    styling matters.
  • Malformed or empty intent input is a hard failure (exit 1) naming what went wrong, rather
    than a successful run that produced nothing.
  • convert, validate, and fix are unchanged. Verified by running the benchmark at the
    previous release and at this one: identical scores across all 53 fixtures.
Assets 2
Loading