菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill set-up-my-legal-info命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when retrieving arbitration institutional rules (ICC, LCIA, SCC, SIAC, HKIAC, VIAC, МКАС/МАК при ТПП України, UNCITRAL) — fetching current version, verifying redaction applicable to the date of arbitration agreement, constructing URLs for official rule texts
Use when choosing the Polish legal regime for letters, requests, applications, complaints, petitions, public-information requests, KPA filings, PPSA complaints, RODO access requests, registry extracts, court-file access, tax/ZUS/cudzoziemcy/USC procedures, or professional lawyer letters. Prevents mixing UDIP, KPA, PPSA, RODO, registry, special-procedure, and advocate/radca letter regimes.
Use when preparing applications for recognition and enforcement of foreign arbitral awards in Poland, applications for setting aside arbitral awards under KPC art. 1205–1211, or opposing such applications — mapping Article V of the 1958 New York Convention to art. 1214–1215 of the Polish KPC, identifying grounds for refusal, structuring public policy arguments
基于 SOC 职业分类
正在显示 SKILL.md
| name | set-up-my-legal-info |
| title | 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. |
| author | gethouston |
| author_url | https://github.com/gethouston/houston/tree/main/store/agents/legal/.agents/skills/set-up-my-legal-info |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | corporate |
| language | en |
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 .houston/<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".