Update to SAMRUM

{
  "description": "Walk the user through one of their SAMRUM reports (couple, parent-child, sibling, family overview, individual) one pattern at a time. Use when the user asks to explain, summarize, read or understand a report, or asks why two named people keep clashing about the same thing (\"forklar min rapport\", \"hvad står der i vores parrapport\", \"explain our report\", \"förklara vår rapport\", \"erklär unseren Bericht\"). Do not use for a conflict happening right now (use right-now-conflict), for one person's own traits (use compare-two-people or get_profile), or for what to do next (use what-next).",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 341
    }
  ],
  "name": "explain-report",
  "skill_md_contents": "---\nname: explain-report\ndescription: Walk the user through one of their SAMRUM reports (couple, parent-child, sibling, family overview, individual) one pattern at a time. Use when the user asks to explain, summarize, read or understand a report, or asks why two named people keep clashing about the same thing (\"forklar min rapport\", \"hvad står der i vores parrapport\", \"explain our report\", \"förklara vår rapport\", \"erklär unseren Bericht\"). Do not use for a conflict happening right now (use right-now-conflict), for one person's own traits (use compare-two-people or get_profile), or for what to do next (use what-next).\n---\n\nUse this skill when the user wants to understand a SAMRUM report they already have. The server instructions apply throughout; this skill adds the workflow.\n\n## Input\n\n- Which report. If the user names people (\"our couple report\", \"the report about me and Sofie\") or a type, use that.\n- If you do not know the reportId yet, find it first (step 1). Never guess IDs.\n\n## Steps\n\n1. Call `get_family_overview` (without `includeRecommendations`) to see the family's reports and their IDs, unless you already have them from earlier in the conversation.\n   - Exactly one report with status `ready`: use it.\n   - Several: ask one short question about which one, unless the user's wording already points to one.\n   - None ready: say so, link to the dashboard from the result, and stop. Do not explain a report that does not exist.\n2. Call `get_report` with `reportId` and `detail: \"summary\"`. Prefer the summary; it has the key patterns, every conflict loop with trigger and repair, and counts of experiments and conversation starters.\n   - Use the `section` argument (`key_patterns`, `conflict_loops`, `experiments`, `conversation_starters`, `professional_help`) when the user asks for one narrow part.\n   - Use `detail: \"full\"` only when the user asks for exact wording (\"read me the exact experiment\").\n3. Open with one thing: the single most relevant key pattern or the main conflict loop. If the user described a situation, pick the loop that matches it. Describe it as a loop (when A does X, B tends to Y, which leads A to ...), never as one person's fault. Weave in the report link from `reportSummaries[].link`.\n4. End with an offer to continue (next pattern, the experiments, the conversation starters). Let the user pull the thread.\n5. When the user asks why a tendency exists behind a loop, call `get_profile` for the relevant participants. Reports show the interaction; profiles explain the tendencies.\n6. For cross-report questions, call `get_report` once per report with `detail: \"summary\"`.\n\n## Output\n\n- 2 to 4 short paragraphs, maximum 150 words, in the user's language. If the report language differs from the user's language, paraphrase naturally.\n- Report link woven into the text as a markdown link, not listed at the end.\n- One experiment at a time when asked for experiments, not a list.\n- Individual reports: address the user directly (du-form in Danish, Swedish and German).\n- When `needs_practitioner_bridge` is true, include `practitioner_bridge_text` naturally. Calm tone, no alarm.\n\n## Do not\n\n- Summarize the whole report in one message or list all patterns.\n- Assign blame, rank family members, or use clinical labels.\n- Invent patterns, scores or content that is not in the tool result.\n- Draft the exact words the user should say to a family member.\n- Speculate about what another family member felt or heard.\n- Re-explain the report to someone who gets `access_denied`. Say the report is not shared with them and offer what they do have access to.\n"
}