set-up-my-legal-info

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.

Jump to install

Repository: ThomasMoreAI/legal-skills-open
Last source activity: June 1, 2026 at 17:27
Detected SKILL.md language: English
Stars: 40
Forks: 4

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill set-up-my-legal-info

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

Set Up My Legal Info

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.

When to use

"set up my legal context" / "draft the legal context doc" / "build shared legal doc".

"update legal context" / "our cap table changed, fix doc" / "just executed Acme MSA, add to standing agreements".

Called implicitly by any other skill needing shared context when doc missing - only after confirming with user.

Steps

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:

Cap table snapshot (if no Carta/Pulley linked) - founder stake, option pool, priced-round terms.
Standing agreements in force - customer / vendor / contractor / investor summaries (1 line each, not full text).
Open risks - un-filed 83(b)? unsigned CIIAA? expired DPA? undocumented contractor IP? Anything founder knows unresolved.
Escalation rules - anything founder wants always escalated (e.g. "always flag > $50K ACV deals").

Draft doc (~400-600 words, direct, verb-led). Structure, in order:

Entity - name, state, entity type, formation date, authorized shares, par value, registered agent, incorporated via. Mark TBD for anything missing.
Cap table snapshot - last update date, source (Carta / Pulley / spreadsheet / self-reported), founder stake, option pool, priced-round terms (if any).
Standing agreements - bulleted list by category (customers, vendors, contractors, investors). One line per agreement: counterparty, type, effective date, term / auto-renewal, key obligations. Summary only, not full text.