Genbi
Turn a Wren project's context layer into a shareable, browser-side GenBI web app and...
Install
npx skills add Canner/WrenAI --skill genbi -g -a claude-code -y- Repository
- Canner/WrenAI18k
- Category
- AI and agents
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,874 tokens
- Runs scripts
- No, instructions only
What it does
Turn a Wren project's context layer into a shareable, browser-side GenBI web app and deploy it to the user's Vercel or Cloudflare account. Orchestrates the full flow: `wren genbi build` returns a project-hydrated build instruction, the agent authors the app from scratch into apps/<name>/, then register → verify → deploy produce a shareable URL. Use this skill whenever the user wants to: build a dashboard from their Wren project, make a shareable analytics app, deploy their context layer as a web app, host a GenBI app on Vercel or Cloudflare Pages, or asks for a 'genbi app'.
Wren GenBI App, Agent Workflow Guide
This guide is served by the
wrenCLI (wren skills get genbi), so it always matches your installed wrenai version.
Turn a Wren context layer into a shareable GenBI app, from a natural-language request to a public URL in one conversation.
Division of labor: the CLI owns the authoritative build instruction (it
knows the live project facts and the pinned wren-core-wasm version) and all
deterministic state (index, verify, deploy). You, the agent, author the app
code by following the instruction. Never hand-write .wren/apps.yml.
Preconditions
- A Wren project is discoverable (
wren_project.ymlin cwd/ancestors, or ask for the path and pass-p). - The context layer exists. If
target/mdl.jsonis missing,wren genbi buildcompiles it implicitly, no separate step needed. wrenCLI ≥ the version that ships thegenbicommand group (wren genbi --helpworks).
Workflow
1. Resolve the app name and data mode
- App name: short kebab-case derived from the request (e.g.
sales-overview). - Data mode:
snapshot(default), data is bundled with the app as parquet/duckdb and queried client-side. Fully serverless. Right for demos, reports, small data, and dlt-pipeline output.live, the app calls back to the user's warehouse/API at view time. Right for production-scale or always-fresh data. Requires a CORS-enabled endpoint and carries strict no-credentials rules.
- Ask the user ONLY if the choice is genuinely ambiguous.
2. Get the build instruction
wren genbi build <name> --prompt "<the user's request, verbatim>" --data-mode <mode>
