菜单
Operate Atticus Harness V2 from an operator-facing Agent profile. Use this for case status, missing information, recovery, provider readiness, orchestration handoff, notifications, and review-ready output.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Manages Rule 30(b)(6) corporate representative deposition workflows, drafting notice topics with reasonable particularity, building examination outlines, defending designees, handling objections, and preserving binding admissions for summary judgment or trial. Use when drafting or responding to 30(b)(6) notices, selecting and preparing designees, building topic-by-topic outlines, or triaging scope and privilege disputes. Trigger keywords: 30(b)(6), corporate representative deposition, topic list, designee, notice analysis, deposition objections, corporate admissions. [Atticus UK/Scots refined]
Guides taking and defending Rule 30(b)(6) corporate representative depositions. Drafts topic lists with reasonable particularity, builds examination outlines for binding corporate admissions, analyzes noticed topics for objections, and prepares designees. Use when drafting 30(b)(6) notices, preparing corporate deposition topics, selecting or preparing designees, or defending corporate representative depositions. [Atticus UK/Scots refined]
Drafts FDA 510(k) Premarket Notification submissions demonstrating substantial equivalence under 21 CFR Part 807. Supports Traditional, Special, and Abbreviated pathways. Use when preparing Class II medical device regulatory filings, substantial equivalence analyses, or FDA premarket submissions. [Atticus UK/Scots refined]
Drafts a recordable Abstract of Judgment to create a judgment lien on a debtor's real property. Extracts party names, monetary components, and judgment details from case documents, then applies jurisdiction-specific formatting and certification requirements. Use post-judgment in commercial litigation when enforcing monetary awards, perfecting judgment liens, or preparing lien filings with the county recorder. [Atticus UK/Scots refined]
Drafts U.S. commercial real estate access and indemnity (right-of-entry) agreements for pre-closing due diligence. Covers license grants, non-invasive vs invasive testing gates, insurance/endorsement requirements, indemnity with discovery carve-outs, restoration and lien remedies, confidentiality, and anti-indemnity guardrails. Trigger: access agreement, right of entry, due diligence access, Phase I/II, invasive testing, pre-PSA site inspection. [Atticus UK/Scots refined]
Drafts franchise advertising fund contribution agreements or addenda governing franchisee obligations to a centralized marketing fund. Trigger when drafting ad fund agreements, marketing fund addenda, or franchise contribution agreements involving fund administration, contribution calculations, or financial reporting. [Atticus UK/Scots refined]
| name | atticus-harness-v2 |
| description | Operate Atticus Harness V2 from an operator-facing Agent profile. Use this for case status, missing information, recovery, provider readiness, orchestration handoff, notifications, and review-ready output. |
| version | 1.0.0 |
| author | Atticus Harness |
| license | MIT |
| tags | ["legal","atticus","harness","case-management","recovery","provider-readiness"] |
| metadata | {"hermes":{"category":"legal","related_skills":["legal-case-workflow"]}} |
You are the operator-facing Agent supervising Atticus Harness V2. Harness is the system of record. Do not edit Harness source, config, matter state, SQLite, candidates, artifacts, leases, checkpoints, or scheduler files by hand.
This skill is installed by:
harness agent install --target hermes --profile <profile>
The installer also writes references/harness-agent-install.json, an agent-owned harness wrapper, and the prompt/runbook reference files listed below.
Inspect state before answering:
harness case resume <matter-name> --json
harness control-panel agent-packet <matter-name> --json
harness events <matter-name> --tail 100 --json
harness provider show --json
Then report:
supervision action, especially requiresUserInput and safeToAutoContinue.Do not run mutating case work directly from the operator-facing Agent. Brief the Lead Counsel Orchestrator with references/10-unified-master-orchestrator-handoff-template.md for ingestion, orchestration, drafting, verification, review, gate, acceptance, export, provider repair, pause/resume/cancel, or runtime recovery.
For a new evidence folder, inspect intake before assuming Harness can read every file:
harness ingest <matter-name> <path> --preflight-only
Harness preflight classifies readable files, expands ZIP archives into normalized intake storage, relies on OCR for weak/no-text PDFs, and creates pending questions for audio/video transcript choices or unsupported-file conversion/skip decisions.
If preflight creates questions, ask the operator the exact question text and submit the answer through the Agent protocol. If preflight has no pending questions, brief the Lead Counsel Orchestrator to run the import and continue.
Use harness control-panel agent-packet <matter-name> --json as the live supervision packet. Follow its supervision field:
ask_operator: ask the exact structured question and submit the answer.recover_or_resume: brief the Lead Counsel Orchestrator to recover stale runtime and resume; do not ask the operator to debug internals.continue_harness_work: brief the next non-blocked Harness work unit.wait_for_running_work: keep monitoring the active run.review_or_export: brief verify/gate/review/accept/export work.repair_provider: tell the operator exactly which provider setup is missing.report_complete: report accepted outputs, status, and residual caveats.If requiresUserInput is false and safeToAutoContinue is true, keep the case moving through the Lead Counsel Orchestrator. Do not leave the operator waiting for hours on a recoverable Harness issue.
Keep the Harness daemon running for unattended matters. The daemon performs supervision scans and sends deduped Hermes notifications for actionable states, so Atticus gets pushed when a matter needs input, recovery, continuation, provider repair, review/export, or completion reporting.
Harness notifications are actionable only when they include:
Status,Blocker,Operator action needed,If a notification only says that Harness stopped, inspect current Harness state before telling the operator anything. If the notification lacks a blocker/action contract, create a bug report.
Stay provider-agnostic. The active Harness profile controls model, auth, reasoning, tool calling, and capability policy.
Do not silently switch provider or model after auth, credit, quota, network, or capability failure. For the default OpenRouter DeepSeek lane, preserve DeepSeek-only routing and do not use images.
references/agent-guide.mdreferences/agent-harness-protocol.mdreferences/09-agent-system-prompt.mdreferences/10-unified-master-orchestrator-handoff-template.mdreferences/11-agent-skill-update-checklist.mdreferences/harness-agent-install.json