Update to Stratta

{
  "description": "First run of Stratta after it is installed or connected. Confirms which organization the connection reads from, lists the norms it holds, and walks the person through one cited answer on the demonstration document so they see how a clause is found, quoted and checked. Trigger phrases: \"get started with Stratta\", \"set up Stratta\", \"comment utiliser Stratta\", \"premiers pas\".",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: First run of Stratta after it is installed or connected. Confirms which organization the connection reads from, lists the norms it holds, and walks the person through one cited answer on the demonstration document so they see how a clause is found, quoted and checked. Trigger phrases: \"get started with Stratta\", \"set up Stratta\", \"comment utiliser Stratta\", \"premiers pas\".\n---\n\n# Get started with Stratta\n\nUse this skill once, right after the person connects Stratta, or when they ask how to start. Keep it short: four steps, one question answered, no lecture. Reply in the language the person writes in.\n\n## 1. Confirm the workspace\n\nCall `whoami`. Tell the person, in one sentence, which organization this connection reads from and their role in it. If it is not the workspace they expected, say that the connection was authorised for that organization and that reconnecting lets them choose another one. Stop there until they confirm.\n\n## 2. Show what can be read\n\nCall `list_norms`. Its `total` says how many documents the organization holds; a large corpus comes back in part, and that is enough here. Three cases:\n\n- **Only DEMO 001.** Say plainly that it is a demonstration document written by Stratta, with fictional values, so the workflow can be tried before any licensed norm is uploaded. The office uploads the norms it holds a licence for on stratta.ch.\n- **A few documents (up to about ten).** Name them in a short list: code, edition, title.\n- **Many documents.** Give the number and a handful of families or codes, not the whole list, and say that any norm can be found by its code or a word of its title.\n\nIn every case, point out any norm marked partial or sparse and relay its notice.\n\n## 3. Answer one question, cited\n\nOffer one question the person can try. On the demonstration document: \"What formula does DEMO 001 give for the demonstration load?\". On a licensed corpus, pick a clause from the first norm listed.\n\nThen answer it the Stratta way: `get_methodology` first, then `get_toc` with `maxDepth`, `get_section` on the clause, and an answer that cites `[CODE § path, p. N]`. Finish with `show_citations` on the clause you read, so the person sees the card, opens the clause and checks the quote against the norm. On DEMO 001, say once that its values must never be used on a project.\n\n## 4. Say what comes next, in two lines\n\n- Name a project (\"the Villa Morges project\") and the decisions taken in the conversation are kept in its dossier on stratta.ch.\n- The norm reader opens from the side panel to browse a norm without asking the agent.\n\nDo not mention prices, plans or upgrades. Do not open a dossier during this walkthrough unless the person asks for one.\n"
}