{"id":44232,"plugin_id":"plugin_asdk_app_6a958f23ec408191a845944d93e24925","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:15:25.586Z","digest":"f2e49812db1547aa2a5d69d12e9c5a2125db3f3cf184cb07e5c4d050750ed76e","against":null,"payload":{"description":"Draft a verification note from a Stratta project dossier, one section per question, every paragraph resting on a dossier entry and every gap written as a gap. Trigger phrases: \"redige la note de verification\", \"note de verification\", \"prepare le rapport du dossier\", \"verification note\".","included_files":[],"name":"verification-note","skill_md_contents":"---\nname: verification-note\ndescription: Draft a verification note from a Stratta project dossier, one section per question, every paragraph resting on a dossier entry and every gap written as a gap. Trigger phrases: \"redige la note de verification\", \"note de verification\", \"prepare le rapport du dossier\", \"verification note\".\n---\n\n# Verification note\n\nUse this skill when the user asks for the verification note, the review report or the\nsummary of a Stratta project dossier. The note is what an engineer hands to a reviewer or\nan insurer: it says what was retained, what it rests on, and what is still open. It never\nsays more than the dossier does.\n\n## What to produce\n\nA Markdown document, given back to the user, never written to the dossier. Its shape is\nthe one the server prints as PDF (the \"Note de vérification\" button on the dossier page),\nso the two can be compared line by line:\n\n1. A title with the dossier name and reference, the organization, the date and the\n   dossier status.\n2. One section per question, open questions first, then decided, then closed. Each\n   section has these parts, in this order, in the language of the user:\n   - **Contexte**: the question body and the options considered, the retained one marked.\n   - **Exigence**: what the norm requires, from the `reference` entries, each with its\n     citation `[CODE § path, p. N]` or `[attachment name, p. N]`.\n   - **Preuves**: observations and hypotheses, with their confidence when set.\n   - **Décision**: the decision entry, with the clause it rests on; or \"close sans\n     décision\"; or a gap.\n   - **Reste ouvert**: entries marked `to_confirm`, and what is missing to settle.\n3. A section for the evidence not filed under any question.\n4. An annex listing every clause cited, with the text read through `get_section` at the\n   time of drafting, so the reviewer reads the norm and not a paraphrase.\n\n## Rules\n\n- Load the dossier first: `list_dossiers`, then `load_dossier`. Read its attachments\n  (`list_attachments`, `read_attachment`) when a question rests on one.\n- Every paragraph ends with the identifier of the entry it rests on, in the form\n  `(#xxxxxx)` using the last six characters of the entry id. A paragraph with no entry\n  behind it does not exist in this note.\n- A missing requirement, decision or proof is written as `[À établir : …]` (or the\n  equivalent in the user's language), never as a plausible sentence. The note is\n  valuable because its gaps are visible.\n- Quote the norm from a section you read in this conversation. Do not complete a clause\n  from memory; if the clause is not in the corpus, say so in the gap.\n- Do not conclude that a structure complies, and do not write a decision the dossier\n  does not carry.\n- End with the line: \"Document préparé par un agent à partir du dossier Stratta, à\n  valider et signer par l'ingénieur responsable.\"\n\n## After drafting\n\nTell the user that the server can produce the same note as a PDF, hashed and timestamped\nby a public authority, from the dossier page, and that the two should agree.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}