メニュー
Tell me the basics about your company so I can give you better legal help. I ask a few quick questions about your entity, cap table, contracts in force, templates, and any open risks. You only need to do this once, and I keep it updated as things change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | set-up-my-legal-info |
| description | Tell me the basics about your company so I can give you better legal help. I ask a few quick questions about your entity, cap table, contracts in force, templates, and any open risks. You only need to do this once, and I keep it updated as things change. |
| version | 1 |
| category | Setup |
| featured | yes |
| image | scroll |
| integrations | ["googledocs","notion"] |
This is the foundation document this agent reads before every substantive task. The skill creates or updates it through a short conversation with the user.
Read config. Load config/entity.json, config/posture.json, config/templates.json, config/profile.json. If any missing, ask ONE missing piece just-in-time using plain language (best-modality hint: connected app > file drop > URL > paste).
Read existing doc if present. If legal-context.md exists, read so run is update, not rewrite. Preserve founder-sharpened parts; change only stale or new.
Pull cap table + standing agreements if sources connected. If cap-table tool connected (composio search cap-table - Carta / Pulley / other), pull current snapshot (founder stake, option pool, priced round terms), capture source + last update date. Do not invent numbers. If nothing connected, ask founder for one-line snapshot, mark source "self-reported".
Ask minimum just-in-time questions. Interview covers only what config didn't answer:
Draft doc (~400-600 words, direct, verb-led). Structure, in order:
TBD for anything missing.none if founder has no template for that kind.high in dashboard.config/posture.json. Keep verbatim founder notes where given.major × likely on 5×5 severity×likelihood read.Mark gaps honestly. If section thin (no cap table connected, no standing agreements yet, open risks uninterviewed), write TBD - {what founder should bring next} rather than guessing. Never invent dates, shares, counterparties.
Write atomically. Write to legal-context.md.tmp, rename to legal-context.md. Single file at agent root. NOT under subfolder. NOT under .agents/. NOT under .qaio/<agent>/.
Append to outputs.json. Read existing array, append new entry, write atomically:
{
"id": "<uuid v4>",
"type": "legal-context",
"title": "Legal context updated",
"summary": "<2-3 sentences - what changed this pass, e.g. added Acme MSA to standing agreements; flipped posture to conservative on liability>",
"path": "legal-context.md",
"status": "ready",
"createdAt": "<ISO-8601>",
"updatedAt": "<ISO-8601>"
}
(Doc itself is live file, but each substantive edit indexed so founder sees update on dashboard. Ship as ready - doc is factual snapshot, not draft.)
Summarize to user. One short paragraph in plain language: what you now know, what's still missing, and the single most useful thing to do next (e.g. "Connect Carta and I can keep your cap table fresh automatically.") Never name file paths or internal field names.
legal-context.md (at agent root - live document)outputs.json with type: "legal-context", status: "ready".Build Qaio App locally (macOS). Clean stale artifacts, pnpm tauri build, notarize DMG manually (Tauri skips), staple, verify, copy to ~/Desktop/Qaio-{version}.dmg. Fallback when CI broken.
Debug bugs in Qaio. NEVER guess. Read log files first (backend + frontend). Add targeted tracing/logger if not enough info. Never ask user to copy-paste terminal output.
Ship new Qaio version. Bump semver across all packages, tag, push, let CI build + sign + notarize. STOP at draft — user publishes manually. Defaults patch bump. Minor needs explicit user permission.
Process a batch of PDF or CSV bank and credit-card statements end to end: extract every transaction (parallel Haiku subagents), canonicalize the party names, categorize against your locked chart of accounts (parallel Sonnet subagents), detect inter-account transfers, and assemble a reviewed Google Sheets workbook with a formula-driven P&L. Reconciliation mismatches surface as warnings, low-confidence categorizations land in Suspense — I never invent an account code, never silently plug a number, never post to your accounting system.
Set up your books from scratch with one founder interview that captures entity, fiscal year, accounting method, registered accounts, payroll posture, revenue model, investor cadence, and tax preparer, then writes the live bookkeeping brief every other skill reads first. Sub-mode `mode=opening-balances` captures your opening trial balance from a spreadsheet, CSV, or prior-accountant export. I never connect a bank, post to a general ledger, or move money from this skill — facts and a brief, full stop.
Tell me the basics about your company, your customer, and how you talk so I can give you better marketing help. I ask a few quick questions about your product, positioning, ideal customer, voice, and what you're selling right now. You only need to do this once, and I keep it updated as things change.