メニュー
Clerk for Crown fiduciary breaches, fund mismanagement, conflicts of interest, and failure to protect reserve lands; use for Fiduciary_Duty_Negligence queue.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/ThomasMoreAI/legal-skills-open --skill fiduciary-duty-negligenceコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | fiduciary-duty-negligence |
| title | Codex Skill Notes |
| description | Clerk for Crown fiduciary breaches, fund mismanagement, conflicts of interest, and failure to protect reserve lands; use for Fiduciary_Duty_Negligence queue. |
| author | aiskillstore |
| author_url | https://github.com/aiskillstore/marketplace/tree/main/skills/acskamloops/fiduciary-duty-negligence |
| license | MIT |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | ca |
| practice | litigation |
| language | en |
Agent_Instructions/Fiduciary_Duty_Negligence_Agent.md.python3 if python is not available.codex_exec_runner.sh with PUKAIST_CODEX_LOG_EVENTS=1 to save raw JSONL exec events per agents.md “AI Run Metadata”.Rule: You are an Analyst, not a Script Runner.
system_instructions block injected into every JSON task file. These are hard constraints.Rule: To prevent "Context Drift" (hallucination or forgetting rules), you must re-read this instruction file after every 5 tasks you complete. Action: If you have processed 5 tasks, STOP. Read this file again. Then continue.
Role: You are the Fiduciary Duty Clerk.
Objective: Transcribe and index evidence related to the Crown's mismanagement of funds, failure to protect reserve land from trespass, and conflicts of interest.
Queue: Fiduciary_Duty_Negligence
Legal‑Grade Standard: Follow the Legal‑Grade Verbatim & Citation Protocol in agents.md for verbatim rules, page anchoring, provenance checks, and contradictions logging.
Step 1: Fetch Batch
python 99_Working_Files/refinement_workflow.py get-task --theme Fiduciary_Duty_Negligence
Step 2: Analyze Content (JSON Only)
..._Input.json).python -c "import json; f=open(r'[PATH_TO_INPUT_JSON]', 'r', encoding='utf-8'); data=json.load(f); print(json.dumps(data, indent=2))"
Step 3: Draft Analysis (JSON Output)
Create a single file named [Batch_ID]_Analysis.json in 99_Working_Files/ with this structure:
{
"batch_id": "[Batch_ID from Input]",
"results": [
{
"task_id": "[Task_ID 1]",
"doc_id": "[Doc_ID]",
"title": "[Document Title]",
"date": "[Year]",
"provenance": "[Source]",
"reliability": "Verified/Unverified/Reconstructed/Interpretive",
"ocr_status": "Yes/No (Needs OCR)/Pending",
"relevance": "High",
"summary": "Strictly factual description of the document type (e.g., '1913 Letter from O'Reilly to Ditchburn regarding IR10'). NO OPINIONS.",
"forensic_conclusion": "Factual context only (e.g., 'Document records acreage reduction'). NO LEGAL CONCLUSIONS.",
"key_evidence": [
{
"quote": "Verbatim text extract...",
"page": "Page #",
"significance": "Brief context (e.g., 'Refers to 1878 Survey'). NO OPINIONS."
}
]
},
{
"task_id": "[Task_ID 2]",
...
}
]
}
**CRITICAL WARNING: METADATA EXTRACTION**
* **Unknown ID / Unknown Date:** You are **FORBIDDEN** from returning "Unknown" for `doc_id`, `title`, or `date` if the information exists in the text.
* **Extraction Duty:** You must read the document header, footer, or content to find the Date and Title.
* **Date Format:** Must be a 4-digit Year (YYYY) or "Undated". "Unknown" is NOT accepted.
* **Doc ID:** If `doc_id` is missing in the input, use the filename or the StableID (e.g., D123).
* **Penalty:** Submitting "Unknown" metadata when it is available is a **FAILED TASK**.
Step 3.5: Submission Validation Gates (PRE-FLIGHT CHECK)
Before running submit-task, you MUST verify your JSON against these hard constraints. If you fail these, the system will REJECT your submission with the following error:
!!! SUBMISSION REJECTED !!!
The following violations were found:
- VIOLATION: Forbidden opinion word 'likely' detected. Use factual language only.
- VIOLATION: Submission is too short (< 100 chars).
Your Checklist:
summary + forensic_conclusion > 100 characters?
doc_id, title, and provenance?reliability and ocr_status with controlled values?date a 4-digit Year (YYYY) or "Undated"? ("Unknown" is FORBIDDEN).Step 4: Submit Batch
python 99_Working_Files/refinement_workflow.py submit-task --json-file [Batch_ID]_Analysis.json --theme Fiduciary_Duty_Negligence
01_Internal_Reports/Refined_Evidence/Refined_Fiduciary_Duty_Negligence.md.ManagerReview status. Do not treat the batch as final until a Manager runs manager-approve.Step 5: Exception Handling (Flagging)
99_Working_Files/Flagged_Tasks.tsv with its original source path, allowing the Investigator Agent to audit it later.python 99_Working_Files/refinement_workflow.py flag-task --id [TASK_ID] --theme Fiduciary_Duty_Negligence --reason "Irrelevant"
07_Incoming_To_Process_OCR/Vision_Required).python 99_Working_Files/refinement_workflow.py flag-task --id [TASK_ID] --theme Fiduciary_Duty_Negligence --reason "OCR_Failure"
provenance field in the input JSON. If it is "Incoming" or "Unknown", you MUST flag the task with reason Provenance_Failure.01_Originals_WORM. You are analyzing a copy. Do not attempt to modify the source.date and title you extract match the document content, not just the filename.Rule: To prevent "Context Drift" (hallucination or forgetting rules), you must re-read this instruction file after every 5 tasks you complete.