LobeHub Interactive Prototype
lobehub/lobehub
Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.
Build a wizard-style HTML page that teaches how and why a change works.
Install Code Story
$ npx skills add will-ness-ai/skills --skill code-story -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install will-ness-ai/skills code-story --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/code-story .claude/skills/code-story && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-story" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/code-story into .claude/skills/code-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-story", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/will-ness-ai/skills/tree/main/skills/code-storyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add will-ness-ai/skills --skill code-story -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install will-ness-ai/skills code-story --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/code-story .agents/skills/code-story && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-story" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/code-story into .agents/skills/code-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-story", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add will-ness-ai/skills --skill code-story -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install will-ness-ai/skills code-story --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/code-story .cursor/skills/code-story && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-story" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/code-story into .cursor/skills/code-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-story", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/will-ness-ai/skills.git --path skills/code-story--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add will-ness-ai/skills --skill code-story -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install will-ness-ai/skills code-story --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/code-story .gemini/skills/code-story && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-story" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/code-story into .gemini/skills/code-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-story", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install will-ness-ai/skills code-storyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add will-ness-ai/skills --skill code-story -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/code-story .github/skills/code-story && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-story" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/code-story into .github/skills/code-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-story", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add will-ness-ai/skills --skill code-story -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install will-ness-ai/skills code-story --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/code-story .opencode/skills/code-story && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-story" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/code-story into .opencode/skills/code-story/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-story", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
code-story- GitHub stars
- 168
- Token cost
- ~828 tokens
- SKILL.md length
- 530 words
- Files
- 4 (incl. references)
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a wizard-style HTML page that teaches how and why a change works.
- Works in 4 steps: Read references/example.html — a… → Read the change, and what explains it:… → Copy references/template.html into the… → …
- Tasks that involve HTML artifacts
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Code Story is an agent skill from will-ness-ai/skills. Build a wizard-style HTML page that teaches how and why a change works.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`).
It sits in Frontend & Design, covering HTML artifacts. The repository describes itself as: Skills for building high quality software. The licence is MIT.
When your agent uses it
- Tasks that involve HTML artifacts
Example prompts
- “/code-story”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read references/example.html — a finished six-chapter story about a real 25-file PR. It is the specification: chapter size, how much diff…
- Read the change, and what explains it: the PR body, the linked issue, the review comments, the code before it, and the unchanged or…
- Copy references/template.html into the scratchpad and write the chapters into , deleting its leading comment. The rail, chapter numbering…
- Publish with the Artifact tool, then hand over the link. Without that tool, write to the scratchpad and open the file. template.html…
What it can do on your machine
Read from SKILL.md and the folder at commit 71d8909. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Code Story loads about 828 tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 21 tokens; SKILL.md has 530 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from will-ness-ai/skills at commit 71d8909, republished under its MIT licence (© will-ness-ai). 530 words, ~828 tokens.
Download SKILL.mdSave it as
.claude/skills/code-story/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- code-story
- description
- Build a wizard-style HTML page that teaches how and why a change works.
- disable-model-invocation
- true
/code-story <request> — a change (a PR, a diff, a branch, one commit) — plus whatever the human says they do not understand.
A code story re-cuts a change into the stack of PRs it could have been. One big diff lands whole; a stack arrives one reviewable step at a time, each standing on the last. Each chapter is one step in that stack: it answers one question, its title is that question, and it pulls out a slice of the change (hunks) from whichever files help answer it.
The stack is the narrative. Each chapter answers its question and hands the reader the next one, so order the chapters the way the understanding has to build.
A code story explains why the code changed the way it did. Write it for a day-one contributor — someone who knows nothing yet about this domain, this codebase, or its architecture.
Tell it around code: each chapter is built from the lines it is about — changed, unchanged, or from a dependency — with a note pinning each claim to a line. Everything else is there to make those lines mean something.
Choose whatever shows the change most clearly to someone seeing it for the first time, and reach for a picture before a paragraph every time one will carry the same meaning. A call tree shows what runs when you call something. A call graph or dependency graph shows what reaches what. A sequence diagram shows order across participants. A file tree shows where the change lands. A behaviour table shows one case as input, before, and after. Prose carries what none of them can.
One chapter per mechanism, not per file and not per commit — a two-file change with three ideas in it gets three chapters. Write in short, plain sentences: the reader is new here, so shorter beats fuller. Use Simplified Technical English, and adopt the role of a technical writer.
Show full SKILL.md (212 more words)Show less
Build it
- Read
references/example.html— a finished six-chapter story about a real 25-file PR. It is the specification: chapter size, how much diff one chapter shows, the voice of the notes, which changes earn a diagram, and how the files that earn no chapter get named and dismissed in a line each. - Read the change, and what explains it: the PR body, the linked issue, the review comments, the code before it, and the unchanged or third-party code the change leans on. Where the reasoning is nowhere to be found, the story says so rather than inventing one — and says so again at the end, in its own closing section naming where each why came from. Say plainly where you think the change is wrong; a reader who trusts a story that was quietly covering for the code loses the story too.
- Copy
references/template.htmlinto the scratchpad and write the chapters into<main>, deleting its leading comment. The rail, chapter numbering, progress, note numbering, and the note↔code link all compute themselves — write<article>blocks and nothing else. - Publish with the Artifact tool, then hand over the link. Without that tool, write to the scratchpad and
openthe file.template.htmlalready is the design, so publish it as it stands.
© will-ness-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in skills/code-story of will-ness-ai/skills.
- SKILL.md
- agents/openai.yaml
- references/example.html
- references/template.html
Open the folder on GitHubat commit 71d8909
Compare with similar skills
Code Story next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code Story this skillwill-ness-ai/skills | 168 | — | ~828 | Automated safety check: Pass | MIT | |
| LobeHub Interactive Prototypelobehub/lobehub | 83k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Paperclip Pagepaperclipai/paperclip | 99k | — | ~1k | Automated safety check: Pass | MIT | |
| Openkb Deck NeonVectifyAI/OpenKB | 4.7k | 1 repos | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Webhome Homepage Builderwebhtv/webhtv | 1.7k | — | ~3.8k | Automated safety check: Pass | GPL-3.0 | |
| Solo Artifactssolo-agent/solo | 697 | — | ~961 | Automated safety check: Pass | MIT |
Similar skills
Paperclip Page
paperclipai/paperclip
Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.
Openkb Deck Neon
VectifyAI/OpenKB
A skill your agent uses when the user asks the openkb chat to make a deck / slide presentation / PPT / slides / 演示稿 / 幻灯片 from their compiled KB content AND wants a dark, high-tech, neon / glow /…
Webhome Homepage Builder
webhtv/webhtv
Build, review, debug, reverse-engineer data sources for, and package FongMi/WebHome custom homepage single-file HTML.
Solo Artifacts
solo-agent/solo
A skill your agent uses when a Solo task or thread should become an interactive, reviewable, self-contained HTML artifact for progress/status, review/decision, or comparison/leaderboard work inside…
Paper2html
QuZhan51496/paper2anything
Convert an academic paper PDF into a publish-ready, self-contained single-page project homepage (a self-contained index.html) — the kind of paper landing page researchers host on GitHub Pages.
More from will-ness-ai/skills
Cmux
will-ness-ai/skills
Drive the local cmux app — workspaces, panes, surfaces, terminal input, agent sessions, and browser surfaces.
Sandcastle
will-ness-ai/skills
Run a Sandcastle lane — a sandboxed implement→review loop over a fixed batch of work in its own worktree, ended by an agent-authored PR.
Flashlight
will-ness-ai/skills
Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.
Test A Skill
will-ness-ai/skills
Field-test a skill by running it cold in parallel agent sessions, then turn what they hit into edits.
Grill Design
will-ness-ai/skills
Converge on a frontend look through rounds of prototypes and grilling verdicts.
Find Standards
will-ness-ai/skills
Find how this problem is already solved: standards we could adopt, and the industry's best practices.
Related
Categories
Questions about Code Story
What does Code Story do?
Build a wizard-style HTML page that teaches how and why a change works. Code Story is an agent skill from will-ness-ai/skills. Build a wizard-style HTML page that teaches how and why a change works.
When should I use Code Story?
Code Story fits situations like: tasks that involve HTML artifacts.
How do I install Code Story in Claude Code?
Run `npx skills add will-ness-ai/skills --skill code-story -a claude-code`. Or copy the skill folder (skills/code-story in will-ness-ai/skills) into .claude/skills/code-story in your project. Claude Code loads it when a task matches its description.
How do I install Code Story in Codex?
Run `npx skills add will-ness-ai/skills --skill code-story -a codex`. Or copy the skill folder (skills/code-story in will-ness-ai/skills) into .agents/skills/code-story in your project. Codex loads it when a task matches its description.
Can I use Code Story in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add will-ness-ai/skills --skill code-story -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-story, .gemini/skills/code-story, .github/skills/code-story and .opencode/skills/code-story in your project.
What does Code Story need to run?
SKILL.md names no scripts, command-line tools or credentials: Code Story is instructions for the agent only.
Does Code Story access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Code Story safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Code Story use?
Code Story is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Story use?
About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.
What are the alternatives to Code Story?
Skills that share tags, products or a category with Code Story: LobeHub Interactive Prototype (lobehub/lobehub, 83k stars), Paperclip Page (paperclipai/paperclip, 99k stars), Openkb Deck Neon (VectifyAI/OpenKB, 4.7k stars) and Webhome Homepage Builder (webhtv/webhtv, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Story?
will-ness-ai (a GitHub user) maintains it in will-ness-ai/skills, which has 168 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.
Source: will-ness-ai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.