一键导入
crossbeam-ops
// Operations manual for the CrossBeam ADU Permit Assistant. Teaches AI agents how to operate the deployed system — trigger flows, check status, read results, navigate the UI, and query the database.
// Operations manual for the CrossBeam ADU Permit Assistant. Teaches AI agents how to operate the deployed system — trigger flows, check status, read results, navigate the UI, and query the database.
Local demo: City-side ADU plan review. Point this at a plan binder (PDF or pre-extracted PNGs) and a city name. It reviews the plans sheet-by-sheet against state and city code, then generates a draft corrections letter. Fire-and-forget — no human-in-the-loop pause. Triggers on: 'Review this ADU plan set for [City]' or 'Run the city review on [path]'.
Local demo: Contractor corrections analysis and response — two-phase flow with a human-in-the-loop pause. Phase 1 reads the corrections letter, researches codes, views plan sheets, and generates questions for the contractor. The agent STOPS and presents questions to the user. After the user provides answers, Phase 2 generates the full response package (response letter, professional scope, corrections report, sheet annotations). Triggers on: 'Analyze these corrections' or 'Run the contractor flow on [path]'.
City-side ADU plan review — the flip side of adu-corrections-flow. Takes a plan binder PDF + city name, reviews each sheet against code-grounded checklists, checks state and city compliance, and generates a draft corrections letter with confidence flags and reviewer blanks. Coordinates three sub-skills (california-adu for state law, adu-city-research OR a dedicated city skill for city rules, adu-targeted-page-viewer for plan extraction). Triggers when a city plan checker uploads a plan binder for AI-assisted review.
Generate 2-minute product demo videos for technical projects (GitHub repos, APIs, technical products). Runs parallel build options with structured critic review. Use when demoing code, explaining architecture, or creating explainer videos.
Analyzes ADU permit corrections letters — the first half of the corrections pipeline. Reads the corrections letter, builds a sheet manifest from the plan binder, researches state and city codes, views referenced plan sheets, categorizes each correction item, and generates informed contractor questions. This skill should be used when a contractor receives a city corrections letter for an ADU permit. It coordinates three sub-skills (california-adu for state law, adu-city-research for city rules, adu-targeted-page-viewer for plan sheet navigation) to produce research artifacts and a UI-ready questions JSON. Does NOT generate the final response package — that is handled by adu-corrections-complete after the contractor answers questions. Triggers when a corrections letter PDF/PNG is provided along with the plan binder PDF.
City-side ADU plan review — the flip side of adu-corrections-flow. Takes a plan binder PDF + city name, reviews each sheet against code-grounded checklists, checks state and city compliance, and generates a draft corrections letter with confidence flags and reviewer blanks. Coordinates three sub-skills (california-adu for state law, adu-city-research OR a dedicated city skill for city rules, adu-targeted-page-viewer for plan extraction). Triggers when a city plan checker uploads a plan binder for AI-assisted review.
| name | crossbeam-ops |
| version | 1.0 |
| description | Operations manual for the CrossBeam ADU Permit Assistant. Teaches AI agents how to operate the deployed system — trigger flows, check status, read results, navigate the UI, and query the database. |
This skill teaches you how to operate the CrossBeam system programmatically and via browser.
| What you want to do | Load these references |
|---|---|
| Trigger a flow, check results, or reset via API | references/api-endpoints.md |
| Query the database directly (Supabase MCP or SQL) | references/data-model.md |
| Understand what each flow does and its phases | references/flows.md |
| Navigate the UI via Chrome browser | references/ui-navigation.md |
| Work with demo/test projects | references/demo-projects.md |
| Item | Value |
|---|---|
| Vercel URL | https://cc-crossbeam.vercel.app |
| Cloud Run URL | https://crossbeam-server-v7eqq3533a-uc.a.run.app |
| Supabase Project ID | bhjrpklzqyrelnhexhlj |
| Supabase URL | https://bhjrpklzqyrelnhexhlj.supabase.co |
| Auth method | Authorization: Bearer $CROSSBEAM_API_KEY |
| Judge Contractor Project | b0000000-0000-0000-0000-000000000002 |
| Judge City Project | b0000000-0000-0000-0000-000000000001 |
| Schema | crossbeam (not public) |
# 1. Reset the demo project
curl -X POST https://cc-crossbeam.vercel.app/api/reset-project \
-H "Authorization: Bearer $CROSSBEAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{"project_id":"b0000000-0000-0000-0000-000000000002"}'
# 2. Trigger corrections analysis
curl -X POST https://cc-crossbeam.vercel.app/api/generate \
-H "Authorization: Bearer $CROSSBEAM_API_KEY" \
-H "Content-Type: application/json" \
-d '{"project_id":"b0000000-0000-0000-0000-000000000002","flow_type":"corrections-analysis"}'
# 3. Poll until done (check project.status)
curl -s https://cc-crossbeam.vercel.app/api/projects/b0000000-0000-0000-0000-000000000002 \
-H "Authorization: Bearer $CROSSBEAM_API_KEY" | jq '.project.status'