← ClaudeAtlas

quickbase-qbl-analyzerlisted

Parse a Quickbase QBL (Quickbase Language) export into a queryable inventory, then answer questions about the application - architecture, data model, pipelines and integrations, formulas, permissions, dependencies, and technical debt. Also produces an Excel workbook and CSVs. Use for QBL parsing, architecture review, impact analysis ("what breaks if I change this field"), pipeline and integration review, solution inventory, and application documentation. Accepts one QBL YAML file plus an optional Quickbase table schema JSON file. Supports QBL schema versions through v0.15.
thardy-qb/quickbase-qbl-analyzer · ★ 0 · Data & Documents · score 75
Install: claude install-skill thardy-qb/quickbase-qbl-analyzer
# QBL Solution Analyzer Turn a Quickbase QBL export into something you can ask questions about. The primary use is interpretation: explaining what an application does, how its pipelines and integrations work, what depends on what, and where the risks are. A spreadsheet and CSVs come out of the same run for users who want them. Use this Skill only with files supplied by the user. Never call Quickbase or any other external API. Never request or use a user token, service-account token, password, `.env` file, or credentials file of any kind. ## Inputs Required: - One QBL export in YAML format. The filename may end in `.yaml`, `.yml`, or `.txt`. Optional: - One Quickbase table schema JSON file, which adds runtime table IDs, table names, and storage metadata. Everything else — including the field and role IDs the export declares — comes from the QBL file itself, so the analysis is complete without it. ## Workflow ### 1. Parse once ```bash python3 <skill-dir>/scripts/qbl_analyzer.py summary \ "<qbl-file>" \ --output-dir "<output-dir>" \ --label "<solution-label>" ``` Add `--table-schema "<file>"` when one was supplied. This writes the queryable inventory and every artifact. Run it once per solution and reuse the output directory for the rest of the conversation. Do not re-parse to answer a follow-up question. Use a new folder for `--output-dir`, such as `qbl-analysis` beside the export, never the folder the export sits in. The analyzer clears its output folder o