メニュー
Legal productivity workflows for Copilot CLI: contract review, NDA triage, redline-risk, xref, evidence packs, response drafting, briefings, vendor checks, and style learning over existing legal documents.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill legal-productivityコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？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
SKILL.md を表示中
SOC 職業分類に基づく
| name | legal-productivity |
| title | Legal Productivity |
| description | Legal productivity workflows for Copilot CLI: contract review, NDA triage, redline-risk, xref, evidence packs, response drafting, briefings, vendor checks, and style learning over existing legal documents. |
| author | dvelton |
| author_url | https://github.com/dvelton/copilot-legal-productivity-pack/tree/main/skills/legal-productivity |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | contracts |
| language | en |
Use this skill when a legal team wants structured legal workflows in Copilot without moving its documents into GitHub. The user's sources may be local Word files, PDFs, exported emails, SharePoint/OneDrive-synced folders, CLM exports, URLs, or matter folders.
This skill is assistive. It does not provide legal advice. Outputs must be reviewed by qualified counsel before use.
When the user asks for contract review, NDA triage, redline analysis, legal response drafting, legal briefing, vendor context, xref navigation, or source-backed legal analysis, say that the Legal Productivity skill is active and identify the workflow you will run.
Do not assume the customer's documents live in GitHub. Use local files, folders, URLs, and connected document systems the user provides.
The CLI is:
copilot-legal
If it is not installed, from this repository run:
npm install
npm link
copilot-legal setup-check
For global install from GitHub:
npm install -g github:dvelton/copilot-legal-productivity-pack
Use when the user asks to review an MSA, DPA, order form, terms, vendor agreement, customer agreement, or similar contract.
copilot-legal review-contract "<source>" --we-are "<party>" --playbook "<playbook.yml>"
If no playbook is supplied, use the default commercial playbook. Ask which party the user represents if the answer is not clear.
Return:
Use when the user asks whether an NDA is standard or needs review.
copilot-legal triage-nda "<source>"
Return green, yellow, or red, with the specific provisions that drive the classification.
Use when the user provides a Word document with tracked changes.
copilot-legal redline-risk "<source.docx>" --we-are "<party>" --format html
Ask which party the user represents before running this workflow. Directional assessment depends on party perspective.
Use when the user wants to navigate a long agreement, resolve defined terms, or check references.
copilot-legal xref "<source>"
Return the generated HTML file path and a short document-health summary.
Use when the user wants source-backed output.
copilot-legal evidence-pack "<source>" --we-are "<party>"
This package produces an HTML evidence report. If the separate Eyeball skill is installed, prefer Eyeball for Word documents with rendered source screenshots.
Use when the user asks to answer a customer, business stakeholder, security questionnaire, procurement question, or internal legal request.
copilot-legal respond "<question or question-file>" --sources "<approved-source-folder>" "<policy-folder>"
Do not send messages externally. Draft only, cite source basis, and flag counsel-review triggers.
Use when the user asks for a meeting brief, matter brief, topic brief, or summary of a folder.
copilot-legal brief "<matter-folder>" --topic "<topic>"
Use when the user asks what is known about a vendor.
copilot-legal vendor-check "<vendor name>" --sources "<matter-folder>" "<approved-responses-folder>"
Use when the user provides an AI draft and attorney-edited final version.
copilot-legal learn-style "<original-draft>" "<final-version>" --profile "~/Copilot Legal/style/style-profile.md"
Read the style profile before drafting future legal work product for that user or team.
Initialize a local workspace:
copilot-legal init
This creates:
~/Copilot Legal/
playbooks/
templates/
approved-responses/
policies/
matters/
outputs/
style/
The workspace is a convenience. The user can point commands at any file or folder.