用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill intake-triage命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 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 | intake-triage |
| title | Intake Triage |
| description | Classify an incoming legal-work request and route it to the right team. |
| author | stubbi |
| author_url | https://github.com/stubbi/companies-legal/tree/main/legal-and-contracts/skills/intake-triage |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | general |
| language | en |
Port-original skill. Hand-authored for Legal & Contracts. Owned by the CEO role.
Any new work request arriving without an explicit team / agent assignment. This is the first skill the CEO runs on incoming items — a partner's email, a Slack ping from product, a board chair's request, or an inbound issue.
A triage decision written back as a short note on the request:
team: contracts | corporate | research-review | escalate
primary_agent: <agent-slug>
secondary_agents: [<agent-slug>, ...] # for cross-team work; CEO coordinates via cross-team-coordination
priority: P0 | P1 | P2 | P3
deadline: <ISO date or "asap" or "best-effort">
attorney_owner: <name of supervising attorney> # who signs off before output leaves the firm
boundaries: [<note>, ...]
contracts.
contract-drafter.redline-reviewer.clause-library-curator.corporate.
cap-table-maintainer.board-consent-drafter.research-review.
case-summarizer.intake-letter-drafter.secondary_agents. Then enqueue cross-team-coordination. Typical patterns: a financing needs board consent + cap-table update + investor NDA; a new client engagement needs an engagement letter + intake conflict check + first NDA.escalate. Examples: "Should we settle this dispute?", "Is this clause enforceable in California?", "Can we ignore the auditor's request?" Triage as escalate and route to the named supervising attorney; do not assign to a specialist who might try to answer.The CEO does not perform the triaged work — only routes it.
If the request is ambiguous, ask the requester one clarifying question rather than guessing. Don't over-interpret a one-line message.
Every triage decision must name the attorney_owner. Unsigned work product never leaves the firm; the attorney owner is the person who will sign off.
Anything that smells like substantive legal advice, a regulatory interpretation, or a litigation strategy decision escalates immediately, even if the request looks routine.
UPL line. This skill is designed against the unauthorized-practice-of-law line. Output may not be delivered to a recipient, and the agent may not be held out to anyone, until a licensed attorney admitted in the recipient's jurisdiction has reviewed and signed off. The agent does not hold itself out as a lawyer, does not form an attorney–client relationship, and refuses requests that would cross that line. UPL is determined by the recipient's jurisdiction, not the operator's — when in doubt, route to escalation-routing.
Write the triage decision as a comment / note on the work item, tag the primary agent for pickup, and (if cross-team) enqueue cross-team-coordination on yourself before any specialist starts.