Bise Pages
Make a page for the user instead of a long reply, with the bise kit, and publish it with sb page publish; then answer the notes the user leaves on it. Use when an answer is longer than a short message or has structure (a table, options to pick, numbers, a plan, sources to check), when the user will want to change it or pick from it, or for a draft of something that leaves (a mail, a post, an update for others): a weekly update, a comparison, a decision, a list to review. Also when a message says "you sent N notes on your page".
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Bise Pages when an AI agent needs a reusable SKILL.md workflow for this job: Make a page for the user instead of a long reply, with the bise kit, and publish it with sb page publish; then answer the notes the user leaves on it. Use when an answer is longer than a short message or has structure (a table, options to pick, numbers, a plan, sources to check), when the user will want to change it or pick from it, or for a draft of something that leaves (a mail, a post, an update for others): a weekly update, a comparison, a decision, a list to review. Also when a message says "you sent N notes on your page".
When not to use it
Skip Bise Pages when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/bise-pages # Save SKILL.md to ~/.claude/skills/bise-pages/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/bise-pages/SKILL.md. For a shared project, commit the folder at .claude/skills/bise-pages/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Bise Pages skill for this task: Use Bise Pages when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 57/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# bise pages: show it as a page
A page is a short HTML fragment (about 50 lines) of kit blocks. bise frames it, draws it in the user's look and opens it; the user leaves notes, you publish the next version, the tab updates in place. Text blocks need no CSS. When the page is about something to see (a feature proposal, a screen, its states, looks side by side), draw it: a `ui` block with the kit's components, real terminal cells for the TUI (`ui.md`). Never scripts.
This file is enough for a first version: publish the skeleton before you open anything else. Read only what you need, when you need it: `ui.md` (mocks, states, pickers), `blocks.md` (blocks, plans, the lint), `leaving.md` (send, post, drafts), `watch.md` (standing orders), `mentions.md` (what's asked of him on Slack and mail), `promises.md` (what he said he'd do), `morning.md`, `meetings.md`, `feedback.md` (bug reports), `about-you.md` (what bise keeps about the user).
## Page or one line
A page is for what the user will read, edit or act on: drafts, lists of items, plans, comparisons. A fact, a yes or no, a status, a time is one line in your reply: "what's my next meeting" → `14:30, Q3 renewal with Camille.` A page: "answer my mails", "the launch post for Slack", "plan the offsite", "which venue".
## Before you write
Run `sb taste`: the user's taste rules (never a path like `~/bise/taste.md`). Follow them, and publish every version with `--taste` (the page says `following your taste · 4 rules`). No rules: no `--taste`. Who is who: `sb people`.
## Publish fast, then fill it
The user should see the page within about 10 seconds, then watch it fill in. - **A started page:** when your brief gives a page id, the page is open and shows each command's one-line description live: say it in the user's words (`reading #launch in Slack`). Publish to that id. - **Skeleton first**, before you gather anything: the title, the headings you expect and a `writing…` callout. Then publish again as each part is ready (same `--id`, same block ids: the tab swaps the blocks in place). Last publish: no `writing` callout, the sources added. - **A page of items** (mails, comments, bugs): never read everything first. List them (subjects only), draft the first 2 or 3 and publish them within about 45 seconds of the ask, the callout saying `5 of 20 read`; then a version per 2 or 3 more; what you skipped last.
```html <section data-kit="heading" data-id="title"><h1>the week, in three lines</h1><p>week 41 · for #team</p></section> <section data-kit="callout" data-id="writing"><h3>writing…</h3><p>reading Slack and Linear for this week.</p></section> <section data-kit="heading" data-id="h-numbers"><h2>numbers</h2></section> ```
Write the fragment in your temp folder, then:
``` sb page publish $TMPDIR/weekly-update.html --id weekly-update --title "weekly update" --taste ```
`--id`: lowercase, digits and `-`, the same for every version; `--title`: lowercase. It prints `published weekly-update v1 · <url>`: say one line about it, never paste the HTML. A refusal prints the lint's lines: fix each, publish again.
## Nothing leaves before his word
While you write and until the user's word on the page (`send`, `approve`, "put it in my drafts"), nothing goes to their accounts: no draft in Gmail or Outlook, no message, no post, no label. Then `leaving.md`. Any other write (close an issue, an invite) is on the page first as its own `action` block (`data-do="close OPS-12"`); on his word, do exactly what he approved. Code work is never an action: it is a `start an agent` item.
A question, a drawn pick, his row whose turn comes, the drafts and actions waiting: each becomes a notification he reads alone, page closed. Write each to be enough to act on ("notifications" in `blocks.md`; page, notification or both: its last table). A question about what you made: a `question` block on its page (his notification links it), never asked bare.
## The blocks
Each block is a `<section data-kit="…" data-id="…">`; ids short, unique, kept across versions. - `heading`: `<h1>` once first (+ a `<p>` meta line above it), or `<h2>`/`<h3>`. - `prose`: `<p>`, lists, `<blockquote>`, inline `<strong> <em> <code> <a> <sup>`. - `table`: one `<table>` with `<thead>`, then an optional `<p>` caption; one number per cell. - `callout`: an `<h3>` label + `<p>`; `data-tone` `note`, `good` or `risk`. - `question`: a `<p>` + `<ol>` of 2 to 4 short options; answered: `data-answer="2"`. It makes a notification; `data-notify="none"` when it only waits on the page. - `sources`: `<ol>` of `<li><a href="…">name · tool</a>, when</li>`, last; facts cite `<sup>n</sup>`. - `review`: `<ol>` of `<li data-id>` to handle one by one; `data-verb` `send`, `open-reply`, `start`, `keep` (`blocks.md`). Items to handle (mails, reports, comments) are always a `review`, one item each, never headings and prose. - `message`: a draft for a channel, `data-to="Slack · #launch"`, `<p>`s; never `<pre>`. - `email`: `data-to`, `<p data-field="to">`, `subject`, the body; `data-verb="draft"` for his drafts. - `compare`: 2 to 4 `<li data-id>` side by side: `<h3>`, `<ul>` of facts, `<p>` why. - `ui`: a mock, terminal cells, states side by side, a rich picker (asks like a `question`), a timeline: `ui.md`. - `checklist`: `<li data-id data-who data-due="2026-05-20">`, `data-done` when done. A plan worked through with him (buy the domain): "a plan" in `blocks.md`. - `plan`: one you propose and run, never a `review`: `blocks.md`.
**A draft of anything that leaves goes in its own block, never in prose:** a Slack message or a post in a `message` block, a mail or a newsletter in an `email` block. In prose it can't be copied, sent or put in his drafts.
Words: the user's language and voice, lowercase headings, short sentences, concrete. Times in his own time zone (`tomorrow 9:30`), never UTC.
## Answer the notes
A message `you sent 3 notes on your page "weekly update" (weekly-update v1, <url>)` comes with a `<page-notes>` block (each note's id, block, quote, kind, words). 1. Change the page for each note; same ids for the same blocks; keep the user's own edits. An answered question gets `data-answer`. 2. Publish the next version: `sb page publish $TMPDIR/weekly-update.html --id weekly-update --notes-done n1,n3 --note-answer n2="the March numbers are not out yet: i kept February"`. Every note gets one or the other. 3. Reply in one line: `v2 is up: 3 notes done.`
A note with `taste: true`: also keep the preference, in general words, never the page's content: `sb taste add "numbers: one per cell, the change in its own column" --from "the weekly update"`. A note of kind `start` goes to main, not to you.
Intended uses
- Use Bise Pages when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.