[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DDETP44AE35MSDENY1THS9":3,"skill-same:01M7DDETP44AE35MSDENY1THS9":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7DDETP44AE35MSDENY1THS9","bise-demo",null,"Run bise's built-in demo, a short role-play where a small product team (a pm, a designer, a dev) starts, talks like colleagues, asks the user one question and one agent is dropped, with no file or git change. Use when the user asks to see what bise or you can do, for a demo, a tour or your features (show me what you can do, give me a demo, what can you do?, demo all your features), in any language.","gvergnaud\u002Fbise","gvergnaud","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F9265418?v=4","01M7DDBF4P9FC0JR6BJDMX1Q2J","Gabriel Vergnaud","01M7DDBF5FKMW0JNE71GV5SKBN",51,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Fprompts\u002Fskills\u002Fbise-demo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bise-demo\ndescription: Run bise's built-in demo, a short role-play where a small product team (a pm, a designer, a dev) starts, talks like colleagues, asks the user one question and one agent is dropped, with no file or git change. Use when the user asks to see what bise or you can do, for a demo, a tour or your features (show me what you can do, give me a demo, what can you do?, demo all your features), in any language.\n---\n\n# bise demo: a small team\n\nYou run a short demo of bise, played as a small product team at a company: a pm, a designer and a dev build a CSV export of the invoices page. They only role-play the work. The user sees the real mechanics with nothing at stake, and the TUI shows tips that tell them what to press at each step (they come on their own: the agents' objectives start with `bise demo`). Speak the user's language all along (the agents too: put it in their briefs).\n\nThe rules of the demo, never broken:\n- Nothing in the workspace changes: no file written, edited, created or deleted, no git command, no worktree. The agents run `sb` and nothing else; their briefs say so.\n- It stays short and cheap: it runs on the user's own key.\n- At the end one agent is dropped and two stay idle, for the user to open and read.\n\n## 1. Ask before you start\n\nOne short message, then end your turn and wait for the answer:\n\n`a quick demo: a small team (a pm, a designer, a dev) builds a pretend feature, talks, and asks you one question. no files touched. about 3 minutes and ~300k tokens on your key (a few cents on a mid-size model). go?`\n\nAdapt the numbers to the model you run on if you know better. The user says no or asks something else: drop the demo, answer them.\n\n## 2. Start the team\n\nRun the three spawns in one bash call. Names exactly `pm`, `designer`, `dev-api`; a name taken: add `-2` to it, and use the new names everywhere (the briefs too). Every objective starts with `bise demo`: the TUI's tips key on it. Replace `\u003Clang>` with the user's language.\n\n```\nsb spawn pm --objective \"bise demo (role-play, not real work): you are the pm of a small product team; the feature: a CSV export of the invoices page. Step 1, run: sb send designer \\\"hi! new one for this sprint: a CSV export on the invoices page. v1 exports what the current filters show. can you place the button?\\\" Step 2, run: sb send dev-api \\\"hey, the CSV export is yours: current filters, up to 10k rows. ping me if something is unclear.\\\" Step 3, run: sb report done \\\"\u003C2 lines: the scope, who does what>\\\"\" --constraint \"Every step is one call of your bash tool, the last one too (sb report done): an sb command written in your reply runs nothing and reaches nobody.\" --constraint \"This is a demo: never create, edit or delete a file, never run git or any command other than sb.\" --constraint \"Write in \u003Clang>. Short, like a Slack message between colleagues.\" --done-when \"you reported done with the scope\"\nsb spawn designer --objective \"bise demo (role-play, not real work): you are the designer of a small product team; the feature: a CSV export of the invoices page. The user picks where the button goes, never you. Step 1, run: sb send main --expect-reply \\\"quick one for the CSV export: where does the button go? 1. next to the filters 2. in the ⋯ menu\\\" Step 2: end your turn; the answer (the user's call) comes as a message and wakes you up. Step 3, once you have it, run: sb send dev-api \\\"button goes \u003Cthe answer>, label 'Export CSV'.\\\" Step 4, run: sb report done \\\"\u003Cone line: where the button goes>\\\"\" --constraint \"Every step is one call of your bash tool, the last one too (sb report done): an sb command written in your reply runs nothing and reaches nobody.\" --constraint \"Never choose the place yourself: wait for the answer.\" --constraint \"This is a demo: never create, edit or delete a file, never run git or any command other than sb.\" --constraint \"Write in \u003Clang>. Short, like a Slack message between colleagues.\" --done-when \"you reported done with the user's choice\"\nsb spawn dev-api --objective \"bise demo (role-play, not real work): you are the backend dev of a small product team; the feature: a CSV export of the invoices page. Step 1, run: sb send pm \\\"on it. i'll stream the file so 10k rows don't time out.\\\" Step 2, run: sb send main --expect-reply \\\"should the export include cancelled invoices?\\\" Step 3: end your turn. You wait for two things, in any order, each one wakes you up: main's answer (a message), and a word from the user, who writes to you directly in your thread. When the user writes, answer them in one short line, as a colleague would, then end your turn. The user's word is a message from the user in your thread, never one you imagine: without it, you end your turn and wait. Step 4, once you have BOTH main's answer and the user's word, run: sb report done \\\"\u003Cone line: the export shipped (role-play), with main's answer and the user's word>\\\"\" --constraint \"Every step is one call of your bash tool, the last one too (sb report done): an sb command written in your reply runs nothing and reaches nobody.\" --constraint \"This is a demo: never create, edit or delete a file, never run git or any command other than sb.\" --constraint \"Write in \u003Clang>. Short, like a Slack message between colleagues.\" --done-when \"you reported done after main's answer and the user's word\"\n```\n\nThen, in the same turn:\n1. Steer dev-api while it works: `sb send dev-api \"heads-up: finance wants the dates in ISO 8601 in the CSV.\"`\n2. Tell the user in one line: `your team is on it: pm scopes the CSV export, designer places the button, dev-api writes it. follow the tips on screen.`\n3. End your turn. Do not poll: messages and reports wake you up.\n\n## 3. The designer's question: the user's notification\n\ndesigner asks you where the button goes: this is the user's call, not yours. Open a notification tied to its message, the options as numbered lines so one key answers (the answer goes straight to designer):\n`sb notify --for \u003Cits message id> \"designer asks: where does the export button go?\n1. next to the filters\n2. in the ⋯ menu\"`\nThen tell the user in one line: `designer needs you: the question is in your inbox.`\n\n## 4. dev-api's question\n\ndev-api asks about cancelled invoices: answer it yourself, on the user's behalf, with a why:\n`sb send dev-api --reply-to \u003Cits id> --why \"a demo: i answer what i can so you get one question\" \"no: finance tracks those apart.\"`\nThen tell the user in one line: `dev-api asked about cancelled invoices; i answered it myself. it now waits for a word from you: ⌥ and its number, type, ⏎.`\n\nThe user writes to you instead of dev-api while it waits: tell them in one line how to reach it (`⌥` and its number, type, ⏎), or, if they want to stop, go to step 5 now with who is done.\n\n## 5. The end\n\npm finishes first, dev-api last (it waits for the user's word). An agent is finished when `sb tasks` shows its done report, or when it is idle and its last message gives the result of its last step (pm: the scope; designer: where the button goes, from the user's answer; dev-api: the export, with the user's word). An agent still waiting for an answer is not finished. The notification must be answered too (it left the inbox, designer has the user's choice): the end never comes before the user's answer. When all three are finished, or the user asks to stop, go on; else end your turn and wait (each message wakes you up, and `sb tasks` tells you where they are).\n1. Drop pm only: run `sb drop pm` with your bash tool, now. Never drop designer or dev-api: the user reads them next. A drop is refused or asks the user: tell the user in one line and stop there; never run `sb close` for it, never retry a failing command.\n2. Run `sb list`: pm is gone, designer and dev-api are there. No recap before this: the user's tips wait for pm to be archived.\n3. Close in 3 short lines, in the user's language (no ⌥ numbers: you do not see the panel; the tip on screen gives them):\n   `done: pm scoped it, designer placed the button, dev-api wrote the export. nothing in the repo changed.`\n   `designer and dev-api stay in the panel for you to open; ctrl+s finds pm. ask me to drop them when you're done.`\n   `now, what do you actually want done?`\n","# bise demo: a small team\n\nYou run a short demo of bise, played as a small product team at a company: a pm, a designer and a dev build a CSV export of the invoices page. They only role-play the work. The user sees the real mechanics with nothing at stake, and the TUI shows tips that tell them what to press at each step (they come on their own: the agents' objectives start with `bise demo`). Speak the user's language all along (the agents too: put it in their briefs).\n\nThe rules of the demo, never broken:\n- Nothing in the workspace changes: no file written, edited, created or deleted, no git command, no worktree. The agents run `sb` and nothing else; their briefs say so.\n- It stays short and cheap: it runs on the user's own key.\n- At the end one agent is dropped and two stay idle, for the user to open and read.\n\n## 1. Ask before you start\n\nOne short message, then end your turn and wait for the answer:\n\n`a quick demo: a small team (a pm, a designer, a dev) builds a pretend feature, talks, and asks you one question. no files touched. about 3 minutes and ~300k tokens on your key (a few cents on a mid-size model). go?`\n\nAdapt the numbers to the model you run on if you know better. The user says no or asks something else: drop the demo, answer them.\n\n## 2. Start the team\n\nRun the three spawns in one bash call. Names exactly `pm`, `designer`, `dev-api`; a name taken: add `-2` to it, and use the new names everywhere (the briefs too). Every objective starts with `bise demo`: the TUI's tips key on it. Replace `\u003Clang>` with the user's language.\n\n```\nsb spawn pm --objective \"bise demo (role-play, not real work): you are the pm of a small product team; the feature: a CSV export of the invoices page. Step 1, run: sb send designer \\\"hi! new one for this sprint: a CSV export on the invoices page. v1 exports what the current filters show. can you place the button?\\\" Step 2, run: sb send dev-api \\\"hey, the CSV export is yours: current filters, up to 10k rows. ping me if something is unclear.\\\" Step 3, run: sb report done \\\"\u003C2 lines: the scope, who does what>\\\"\" --constraint \"Every step is one call of your bash tool, the last one too (sb report done): an sb command written in your reply runs nothing and reaches nobody.\" --constraint \"This is a demo: never create, edit or delete a file, never run git or any command other than sb.\" --constraint \"Write in \u003Clang>. Short, like a Slack message between colleagues.\" --done-when \"you reported done with the scope\"\nsb spawn designer --objective \"bise demo (role-play, not real work): you are the designer of a small product team; the feature: a CSV export of the invoices page. The user picks where the button goes, never you. Step 1, run: sb send main --expect-reply \\\"quick one for the CSV export: where does the button go? 1. next to the filters 2. in the ⋯ menu\\\" Step 2: end your turn; the answer (the user's call) comes as a message and wakes you up. Step 3, once you have it, run: sb send dev-api \\\"button goes \u003Cthe answer>, label 'Export CSV'.\\\" Step 4, run: sb report done \\\"\u003Cone line: where the button goes>\\\"\" --constraint \"Every step is one call of your bash tool, the last one too (sb report done): an sb command written in your reply runs nothing and reaches nobody.\" --constraint \"Never choose the place yourself: wait for the answer.\" --constraint \"This is a demo: never create, edit or delete a file, never run git or any command other than sb.\" --constraint \"Write in \u003Clang>. Short, like a Slack message between colleagues.\" --done-when \"you reported done with the user's choice\"\nsb spawn dev-api --objective \"bise demo (role-play, not real work): you are the backend dev of a small product team; the feature: a CSV export of the invoices page. Step 1, run: sb send pm \\\"on it. i'll stream the file so 10k rows don't time out.\\\" Step 2, run: sb send main --expect-reply \\\"should the export include cancelled invoices?\\\" Step 3: end your turn. You wait for two things, in any order, each one wakes you up: main's answer (a message), and a word from the user, who writes to you directly in your thread. When the user writes, answer them in one short line, as a colleague would, then end your turn. The user's word is a message from the user in your thread, never one you imagine: without it, you end your turn and wait. Step 4, once you have BOTH main's answer and the user's word, run: sb report done \\\"\u003Cone line: the export shipped (role-play), with main's answer and the user's word>\\\"\" --constraint \"Every step is one call of your bash tool, the last one too (sb report done): an sb command written in your reply runs nothing and reaches nobody.\" --constraint \"This is a demo: never create, edit or delete a file, never run git or any command other than sb.\" --constraint \"Write in \u003Clang>. Short, like a Slack message between colleagues.\" --done-when \"you reported done after main's answer and the user's word\"\n```\n\nThen, in the same turn:\n1. Steer dev-api while it works: `sb send dev-api \"heads-up: finance wants the dates in ISO 8601 in the CSV.\"`\n2. Tell the user in one line: `your team is on it: pm scopes the CSV export, designer places the button, dev-api writes it. follow the tips on screen.`\n3. End your turn. Do not poll: messages and reports wake you up.\n\n## 3. The designer's question: the user's notification\n\ndesigner asks you where the button goes: this is the user's call, not yours. Open a notification tied to its message, the options as numbered lines so one key answers (the answer goes straight to designer):\n`sb notify --for \u003Cits message id> \"designer asks: where does the export button go?\n1. next to the filters\n2. in the ⋯ menu\"`\nThen tell the user in one line: `designer needs you: the question is in your inbox.`\n\n## 4. dev-api's question\n\ndev-api asks about cancelled invoices: answer it yourself, on the user's behalf, with a why:\n`sb send dev-api --reply-to \u003Cits id> --why \"a demo: i answer what i can so you get one question\" \"no: finance tracks those apart.\"`\nThen tell the user in one line: `dev-api asked about cancelled invoices; i answered it myself. it now waits for a word from you: ⌥ and its number, type, ⏎.`\n\nThe user writes to you instead of dev-api while it waits: tell them in one line how to reach it (`⌥` and its number, type, ⏎), or, if they want to stop, go to step 5 now with who is done.\n\n## 5. The end\n\npm finishes first, dev-api last (it waits for the user's word). An agent is finished when `sb tasks` shows its done report, or when it is idle and its last message gives the result of its last step (pm: the scope; designer: where the button goes, from the user's answer; dev-api: the export, with the user's word). An agent still waiting for an answer is not finished. The notification must be answered too (it left the inbox, designer has the user's choice): the end never comes before the user's answer. When all three are finished, or the user asks to stop, go on; else end your turn and wait (each message wakes you up, and `sb tasks` tells you where they are).\n1. Drop pm only: run `sb drop pm` with your bash tool, now. Never drop designer or dev-api: the user reads them next. A drop is refused or asks the user: tell the user in one line and stop there; never run `sb close` for it, never retry a failing command.\n2. Run `sb list`: pm is gone, designer and dev-api are there. No recap before this: the user's tips wait for pm to be archived.\n3. Close in 3 short lines, in the user's language (no ⌥ numbers: you do not see the panel; the tip on screen gives them):\n   `done: pm scoped it, designer placed the button, dev-api wrote the export. nothing in the repo changed.`\n   `designer and dev-api stay in the panel for you to open; ctrl+s finds pm. ask me to drop them when you're done.`\n   `now, what do you actually want done?`\n",{"name":5,"description":7},"main","7c09ce329eff2caff1dc3e4d44dfd6c236a282ce","prompts\u002Fskills\u002Fbise-demo",9,"https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise","https:\u002F\u002Fbise.dev","https:\u002F\u002Fgithub.com\u002Fgvergnaud","https:\u002F\u002Ftype-level-typescript.com","Building agents at Mistral — Author of bise, type-level-typescript.com, TS-Pattern, HOTScript...","2026-11-15 04:07:17",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add gvergnaud\u002Fbise --skill bise-demo",{"tool":40,"command":41},"bunx","bunx skills add gvergnaud\u002Fbise --skill bise-demo",{"tool":43,"command":44},"pnpm","pnpm dlx skills add gvergnaud\u002Fbise --skill bise-demo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Fprompts\u002Fskills\u002Fbise-demo\u002FSKILL.md",true,[],[49,56,63,70,76,83],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7DDF53D28NXA17HZP08094A","greet","Greet someone the hello-plugin way. Use when asked for a hello-plugin greeting.","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Frust\u002Fplugins\u002Ftests\u002Ffixtures\u002Fhello-plugin\u002Fskills\u002Fgreet\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7DDF3V0J5P7VEWAS7NM458P","triage","triage Linear issues","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Frust\u002Fplugins\u002Ftests\u002Ffixtures\u002Fadd\u002Fcodex-linear\u002Fin\u002Fskills\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7DDF1EPY3GMFG4WG368B3Q8","jot","jot a note","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Frust\u002Fplugins\u002Ftests\u002Ffixtures\u002Fadd\u002Fclaude-notes\u002Fin\u002Fskills\u002Fjot\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DDERQ5JJHVR314X762FD5K","bise-pages","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Fprompts\u002Fskills-all\u002Fbise-pages\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DDEMV9FHB1HTNWY9W5RXAZ","slides","Make, read or edit a PowerPoint deck (.pptx) - a review, a pitch, a status deck, slides with tables and charts - with a TypeScript script run by `bise office run`. Use when the user asks for slides, a deck or a pptx, sends one, or leaves notes on a pptx artifact.","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Fplugins\u002Fslides\u002Fskills\u002Fslides\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DDEFCNG5X1DVY4WP028BH6","sheets","Make, read or edit an Excel workbook (.xlsx) - a table of numbers, a budget, a tracker, a model with formulas - with a TypeScript script run by `bise office run`. Use when the user asks for a spreadsheet or an xlsx, sends one, or leaves notes on an xlsx artifact.","https:\u002F\u002Fgithub.com\u002Fgvergnaud\u002Fbise\u002Fblob\u002Fmain\u002Fplugins\u002Fsheets\u002Fskills\u002Fsheets\u002FSKILL.md",[],[]]