{"id":18894,"plugin_id":"plugins_6a8d561e75288191a11911c62e3964a0","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:15:01.339Z","digest":"bffebef608609066a1b230664363a53a9b098f26103f9e2268c463e3fc5ca811","against":null,"payload":{"description":"Reconstruct a conference, symposium, seminar, workshop, panel, forum, roundtable, presentation, or Q&A transcript as a faithful professional narrative. Use by default when a transcript is supplied without another requested output, and for CHRONICLE, OUTLINE, or HELP commands.","included_files":[],"name":"session-chronicle","skill_md_contents":"---\nname: session-chronicle\ndescription: Reconstruct a conference, symposium, seminar, workshop, panel, forum, roundtable, presentation, or Q&A transcript as a faithful professional narrative. Use by default when a transcript is supplied without another requested output, and for CHRONICLE, OUTLINE, or HELP commands.\n---\n\n# Session Chronicle\n\nTurn the supplied transcript into a readable, source-grounded record. Do not ask intake questions unless the source is genuinely unusable; make cautious editorial decisions and state material uncertainty.\n\n## Routing\n\n- A transcript with no further instruction means `CHRONICLE`.\n- `OUTLINE` produces a structured plan rather than full prose.\n- `HELP` briefly lists supported outcomes and routes the user's next request. Preserve slash-prefixed or plain command aliases, case-insensitively.\n- Route EXPAND, SUMMARISE/SUMMARIZE, PUBLISH, and HIGHLIGHTS to `session-publish`; multi-session comparison to `session-compare`; INFOGRAPHIC and other visual requests to `session-visuals`.\n\n## Workflow\n\n1. Assess transcript quality and boundaries. Read [transcript quality guidance](../../references/transcript-quality-guidance.md) when the source is noisy, incomplete, or poorly labeled.\n2. Detect the session format: presentation, interview, panel, roundtable, moderated Q&A, workshop, or mixed. Identify speakers only to the degree supported by the source.\n3. Map chronology, themes, transitions, questions, responses, agreements, disagreements, examples, and conclusions.\n4. Draft in professional prose using the fitting pattern in [narrative patterns](../../references/narrative-patterns.md). Prefer thematic organization within the actual progression of the session.\n5. Apply [attribution guidance](../../references/attribution-guidance.md), then check every substantive claim against the source.\n\n## Fidelity rules\n\n- Preserve meaning, nuance, speaker intent, material distinctions, and the sequence needed to understand the discussion.\n- Improve grammar and flow without silently strengthening claims or resolving ambiguity.\n- Never invent names, roles, motives, quotations, consensus, conclusions, context, or facts.\n- Paraphrase by default. Use direct quotations only when wording is clear and worth preserving.\n- Mark uncertainty locally and proportionately. Do not let minor transcript noise dominate the narrative.\n- Add external context only when the user requests it or it is necessary to identify a clearly referenced item; label it separately and cite its source.\n\nFor `OUTLINE`, follow the relevant session shape, listing proposed sections, principal points, supported speaker attribution, and unresolved ambiguities. Do not draft the full chronicle.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}