← ClaudeAtlas

quickbase-qbl-app-builderlisted

Generate Quickbase QBL YAML for a new application, or for an edit to an existing one, from a description or a requirements document, then validate it by creating it in your own realm. Builds tables, fields, formulas, relationships, reports, charts, forms, roles, pages, dashboards, pipelines and code pages where nothing native will do. Traces every acceptance criterion to what meets it, runs offline gates, then creates the document in Quickbase to prove it builds, keeps a ledger of every test application so you can delete them, and localises a hang with a ladder of smaller creates. Use for "build me a Quickbase app for X", "generate QBL from these user stories", "validate this QBL by creating it", "edit my app through QBL". Creates real applications; always asks first.
thardy-qb/quickbase-qbl-app-builder · ★ 0 · Data & Documents · score 72
Install: claude install-skill thardy-qb/quickbase-qbl-app-builder
# Quickbase QBL App Builder Generate QBL that Quickbase will build, not merely QBL that parses. A document can pass every offline check and still hang the create with no message. The only proof that Quickbase will build a document is to create it, so this Skill builds the document, runs offline gates, and then creates it. **QBL 0.15.** Every generated document declares `Version: 0.15`, the newest version Quickbase accepts. Do not lower it: a Scatter3D chart is written with 0.15's `ZAxis`, which 0.14 rejects, and `CustomAppMessages` and the newer pipeline channel steps are dropped below 0.15. **Creating makes real applications in the user's realm.** Every attempt that may have made one is written to a cleanup ledger. The user deletes them in Quickbase afterwards; this Skill has no delete call. ## Token rules (read before anything touches Quickbase) The only token sources are the operating system's credential store (macOS Keychain, Windows Credential Manager, Linux Secret Service) or a Claude extension that holds the token itself. - Never ask the user to paste a token into the conversation, and never accept, store, repeat or use one that appears there, in a file, in an environment variable or in a command argument. No script here reads any of those. - If a token is pasted anyway, say so plainly: it is exposed, so they should rotate it in Quickbase, and then store the new one themselves. - Storing is the user's own action: `python3 scripts/store_token.py`, run by