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.
Write, check, repair and publish a plan page: a project's plans and subject files under its plans directory, rendered by .agents/pstack/plan-page.mjs and rendered as one local HTML page per subject…
Install Plan Page
$ npx skills add udecode/dotai --skill plan-page -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install udecode/dotai plan-page --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/udecode/dotai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan-page .claude/skills/plan-page && 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 "plan-page" agent skill from https://github.com/udecode/dotai/tree/main/skills/plan-page into .claude/skills/plan-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-page", 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/udecode/dotai/tree/main/skills/plan-pageType 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 udecode/dotai --skill plan-page -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install udecode/dotai plan-page --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/dotai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan-page .agents/skills/plan-page && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-page" agent skill from https://github.com/udecode/dotai/tree/main/skills/plan-page into .agents/skills/plan-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-page", 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 udecode/dotai --skill plan-page -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install udecode/dotai plan-page --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/dotai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan-page .cursor/skills/plan-page && 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 "plan-page" agent skill from https://github.com/udecode/dotai/tree/main/skills/plan-page into .cursor/skills/plan-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-page", 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/udecode/dotai.git --path skills/plan-page--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 udecode/dotai --skill plan-page -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install udecode/dotai plan-page --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/dotai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan-page .gemini/skills/plan-page && 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 "plan-page" agent skill from https://github.com/udecode/dotai/tree/main/skills/plan-page into .gemini/skills/plan-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-page", 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 udecode/dotai plan-pageInstalls 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 udecode/dotai --skill plan-page -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/udecode/dotai.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan-page .github/skills/plan-page && 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 "plan-page" agent skill from https://github.com/udecode/dotai/tree/main/skills/plan-page into .github/skills/plan-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-page", 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 udecode/dotai --skill plan-page -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install udecode/dotai plan-page --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/udecode/dotai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan-page .opencode/skills/plan-page && 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 "plan-page" agent skill from https://github.com/udecode/dotai/tree/main/skills/plan-page into .opencode/skills/plan-page/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-page", 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
plan-page- GitHub stars
- 1.2k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,772 words
- Files
- 2 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- None found
At a glance
Write, check, repair and publish a plan page: a project's plans and subject files under its plans directory, rendered by .agents/pstack/plan-page.mjs and rendered as one local HTML page per subject…
- Works in 8 steps: Pick the subject before writing the… → Name the subject with Topic: under… → Name the playbook poteto-mode picked… → …
- Tasks that involve HTML artifacts
- SKILL.md covers Render, Check, Repair and Change, plus 1 more section
- Calls node and git
What it does
Plan Page is an agent skill from udecode/dotai. Write, check, repair and publish a plan page: a project's plans and subject files under its plans directory, rendered by .agents/pstack/plan-page.mjs and rendered as one local HTML page per subject with a local index of every subject, and published to claude.ai at each hand-back for comments and feedback. The page is how work hands back to the user. Use before writing or changing a plan, a subject file in <plans/topics or its page; at every stop that hands work back, such as a review verdict other than a…
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/shape.md`).
It sits in Frontend & Design, covering HTML artifacts.
When your agent uses it
- Tasks that involve HTML artifacts
Example prompts
- “s, a next answer or a playbook”
- “/plan-page”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Pick the subject before writing the plan. Continue the subject whose thing the work changes. Start a new one only for a new thing that…
- Name the subject with Topic: under Status:, or through the first entry of the frontmatter list the project names in pageTopic.field, so…
- Name the playbook poteto-mode picked with Playbook: under Status:, so the rail shows it. When a project playbook in .agents/playbooks/…
- Write the leading plan's ## Brief first, per references/shape.md. It is the part the owner reads first. A page with a brief then shows…
- Walk Check's reading list before the first publish and after each revision, then run node .agents/pstack/plan-page.mjs . It refuses every…
- When the work does something the owner can try, write the plan's ## Demo per references/shape.md before the hand-back, reusing the frames…
- Publish the printed file with the Artifact tool to the subject's Page: URL, or to the one-off plan's own, so the user can comment on it…
- After a subject page renders, run node .agents/pstack/plan-page.mjs --index, which renders every subject's page and the index locally. The…
What it can do on your machine
Read from SKILL.md and the folder at commit 6eb4bd9. 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
Shell commands in SKILL.md call:
nodegit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Plan Page loads about 2.9k tokens when it runs, and up to ~7.1k if it reads all its reference files. Until then it costs about 184 tokens; SKILL.md has 1,772 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 1,772 words (~2,891 tokens).
“The user reads pages, not replies; the block's Plan pages rule says when to publish and what the reply holds. A subject is one thing the work changes, and it has one page. Its file, /topics/.md, holds the current state…”
- name
- plan-page
- argument-hint
- [refresh | check | repair | change] [plan]
- metadata.source
- udecode/dotai
- metadata.source-path
- skills/plan-page
Files
SKILL.md and 1 other file (references) in skills/plan-page of udecode/dotai.
- SKILL.md
- references/shape.md
Open the folder on GitHubat commit 6eb4bd9
Compare with similar skills
Plan Page 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 |
|---|---|---|---|---|---|---|
| Plan Page this skilludecode/dotai | 1.2k | — | ~2.9k | Automated safety check: Pass | None | |
| LobeHub Interactive Prototypelobehub/lobehub | 83k | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Paperclip Pagepaperclipai/paperclip | 98k | — | ~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 udecode/dotai
Walkthrough
udecode/dotai
Present final screenshots or rendered artifacts as an annotated walkthrough when visual evidence is requested.
Sync Pstack
udecode/dotai
Set up the pstack plugin in a project through an interview, and keep every pstack project on one pinned tag and one shared AGENTS.md overrides block.
Test Audit
udecode/dotai
Audit existing tests for low-value, duplicated or implementation-coupled cases and the test-only code they keep alive, then remove or rewrite them on evidence.
Related
Categories
Questions about Plan Page
What does Plan Page do?
Write, check, repair and publish a plan page: a project's plans and subject files under its plans directory, rendered by .agents/pstack/plan-page.mjs and rendered as one local HTML page per subject…. Plan Page is an agent skill from udecode/dotai.ai at each hand-back for comments and feedback.
When should I use Plan Page?
Plan Page fits situations like: tasks that involve HTML artifacts.
How do I install Plan Page in Claude Code?
Run `npx skills add udecode/dotai --skill plan-page -a claude-code`. Or copy the skill folder (skills/plan-page in udecode/dotai) into .claude/skills/plan-page in your project. Claude Code loads it when a task matches its description.
How do I install Plan Page in Codex?
Run `npx skills add udecode/dotai --skill plan-page -a codex`. Or copy the skill folder (skills/plan-page in udecode/dotai) into .agents/skills/plan-page in your project. Codex loads it when a task matches its description.
Can I use Plan Page 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 udecode/dotai --skill plan-page -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-page, .gemini/skills/plan-page, .github/skills/plan-page and .opencode/skills/plan-page in your project.
What does Plan Page need to run?
Going by SKILL.md and its folder, Plan Page needs the command-line tools its instructions call (node and git).
Does Plan Page access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Plan Page 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 Plan Page use?
No licence was found for Plan Page or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Plan Page use?
About 2.9k tokens (SKILL.md is roughly 12k 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 4.2k tokens, read only when the agent opens those files.
What are the alternatives to Plan Page?
Skills that share tags, products or a category with Plan Page: LobeHub Interactive Prototype (lobehub/lobehub, 83k stars), Paperclip Page (paperclipai/paperclip, 98k 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 Plan Page?
udecode (a GitHub organization) maintains it in udecode/dotai, which has 1,158 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: udecode/dotai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.