QingYunA/answer-me-with-html

Super Fast  |  ASD-STE100  |  Explainer Videos  |  One File, Offline
An agent skill. Ask a hard question, get a page you can actually read instead of a wall of text. The model writes about 1/8 of the tokens it would need to hand-write the HTML.
Website · Install · Examples · Videos · Always-on mode · Reference · 简体中文
Once installed, ask questions the way you always do:
The agent writes a short Markdown draft and hands it to the CLI that ships with the skill. About 50 ms later you have a page:
https://github.com/user-attachments/assets/d3063a28-5dfd-4c44-a562-be901c49b249
24-second demo. Turn the sound on for the music.
Why not just ask for HTML?
You can. Models write decent HTML now. But most of what they write is not content. We counted the tokens in 9 pages the model wrote by hand, 4,893 tokens on average:
| Part of the page | Share | With this skill |
| :--- | ---: | :--- |
| SVG diagrams: coordinates and paths | 47% | The CLI writes it |
| CSS | 15% | The CLI writes it |
| HTML tags | 17% | The CLI writes it |
| Text | 21% | The model writes it, as Markdown |
With this skill the model writes only a Markdown draft. For the same questions that was 612 tokens on average, **about 1/8 of the hand-written HTML**. Less to write means less to wait for (3 topics × 3 runs, medians, Claude Sonnet 5.5, a plain Claude Code setup):
| | Ask for HTML directly | Answer me with HTML | |
| :--- | ---: | ---: | :--- |
| Tokens the model writes | 4,893 | **612** | **8× fewer** |
| Time | 31 s | **12 s** | **2.6× faster** |
The same question, the same model, answered both ways. Both pages are usable.
The token counts are saved in bench/corpus/tokens.json, so node bench/corpus.mjs gives the same numbers every time. The pages themselves are a download. The bill drops less than the writing, about 15% here, because every turn also reads the system prompt, your question and the conversation, with or without the skill. See where the cost goes.
Explainer videos save even more: about 18× fewer output tokens and 12× faster in a small test.
Install
You need Node.js 20 or newer. There is no npm install step. The CLI is bundled inside the skill. No Node.js yet? With the recommended install below, your agent asks you and then installs it.
Let your agent install it (recommended)
Paste this into Claude Code, Codex, Cursor, OpenCode or any other agent:
> Install Answer me with HTML: read https://raw.githubusercontent.com/QingYunA/answer-me-with-html/main/INSTALL.md and follow it.
INSTALL.md is written for agents. It installs the plugin in Claude Code and the skill in other agents, keeps an existing install, asks you nothing unless Node.js is missing or older than 20, and ends with one report after checking the result with the TCP three-way handshake page. If your agent cannot open links, use npx -y skills add QingYunA/answer-me-with-html -g -y -a (for Claude Code, -a claude-code).
Claude Code plugin
Run this inside Claude Code:
DeepSeek Harness plugin
Run this in a terminal, with the profile you run in (web is the shipped one):
One command
It asks which agents to install into. The installer, vercel-labs/skills, supports more than 70 agents.
Manual install
Copy the skills/answer-me-with-html folder into your agent's skill folder. For Claude Code:
Skill folders for other agents: Codex ~/.codex/skills/, Cursor ~/.cursor/skills/, OpenCode ~/.config/opencode/skill/.
No setup is needed after install. **We recommend turning on always-on mode**: the agent then adds a page to every conclusion, not only the hard ones. It takes one rule in your rules file.
What you ask, what you get
| You ask | You get |
| :--- | :--- |
| "Explain the TCP three-way handshake" | A sequence diagram, a state diagram and a flag table |
| "How are the modules in this repo organized?" | A folder tree plus a call graph |
| "Redis or Memcached?" | A comparison table with ✓ and ✗, then a verdict |