{"id":108775,"plugin_id":"plugins_6a57b17fb5848191be710192d93fe03a","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-21T00:11:56.544Z","digest":"e63b756a805e7e69cd7baa96bdcf7426e5af45be57605f95ac7ea74f0abb3a2d","against":null,"payload":{"description":"Browse registered Studio Archive clients, create or resume an engagement, and recover the same Clara advisory case in a fresh chat.","included_files":[],"name":"studio-archive","skill_md_contents":"---\nname: studio-archive\ndescription: Browse registered Studio Archive clients, create or resume an engagement, and recover the same Clara advisory case in a fresh chat.\n---\n\n# Studio Archive for Clara\n\nUse the shared Studio Archive client directory before resolving a client. Call\n`list_studio_archive_clients`; if unconfigured use `setup_studio_archive` and\nits operating-system folder chooser. Reuse the common approved root across chats and across Vera, Lucia and Clara.\nThe shared directory is available when creating work; Clara’s opening panel\nshows only projects containing Clara work. New Clara engagements are stored\nunder the project’s `clara/` folder. Every project also has `vera/` and `lucia/`.\nThe layout normalizer preserves existing document bytes and sealed records;\nreaders resolve historical product-folder casing.\nAn inaccessible archive or incomplete directory is not evidence that a client\nis absent. Do not create duplicate clients or guess a replacement root.\n\nOpen `clara_archive_open` for the local directory panel when available. The\npanel uses the same interface as Vera and Lucia: search the product’s archive,\nopen saved documents and their exact revisions, and follow existing linked chats.\nIt does not create new chats, engagements or analyses. Missing panel support does not\nblock the equivalent chat tools.\n\nFor an existing client, call `list_studio_client_engagements`. Reuse the selected\nengagement, or call `create_studio_client_engagement` when the user requests new\nwork, with a stable idempotency key for retries. Use `create_studio_archive_client`\nonly for a genuinely new client. Keep each client's stable identity separate.\n\nCall `clara_archive_case` with the exact client_id and engagement_id. A new case\nalso needs the user's assignment objective. To bind an existing Clara workspace,\npass its explicit absolute case_dir once; this preserves its files and location.\nNever create a replacement for an unavailable bound folder. On later calls omit\ncase_dir: the engagement retains the association. Keep the returned case_dir for\nall case-director and evidence-lineage operations, including delegated work.\nRead its case_manifest.json, case_brief.md and selected workpaper/evidence as\nneeded, then follow `../advisory-case-director/SKILL.md`. Distinguish the saved\nposition from newly observed evidence. Do not rerun completed work merely to\nresume it. Existing unbound cases remain usable through their normal path.\n\nThe packaged component lives at `../../modules/studio-archive` relative to this\nskill directory; source checkouts use `../../../studio-archive`. Read its\n`skills/studio-archive/SKILL.md` for maintained registration, import, search and\nsource receipt operations. Preserve shared client identity and each owning\nproduct’s engagement directory. Clara's\ncase binding does not claim a specialist run, completed deliverable, professional\napproval, or a Vera privacy receipt. Do not call Vera-only workflow tools.\n\nIn Cowork the Codex panel and Archive MCP bridge are not registered. Use the\nshared component CLI for directory/engagement operations and the case CLI below.\nIn a chat-only host without local tools, explain that durable continuation is\nunavailable; do not claim that a case was saved.\n\nRun Clara's documented dependency check before local helpers. CLI fallback:\npass one JSON object on stdin to `scripts/clara_studio_archive.py` from the Clara\nplugin root using the configured shared Python environment. It accepts the same\ncase arguments as the MCP tool. Do not change private Archive state locations to\nbypass a missing registration.\n\n## Quali dati arrivano al modello\n\nDirectory tools return safe client labels and stable IDs, followed by the selected\nengagement metadata. The case tool reads local identity and case state and returns\nthe selected case path and manifest (client label, project, objective and other\nmanifest fields); it does not return source document contents. The directory panel\nreceives labels and IDs in private UI metadata and sends the selected IDs to the\nnew chat. Reading the case brief, workpaper or source excerpts later adds those\nselected contents to that chat's model context. These local operations do not\nupload client files or contact a remote service. Follow Clara's existing\nmodel-data reporting contract for the substantive advisory task; record actual\nreads and disclosures, and report a missing receipt separately without blocking\nthe case or its deliverable.\n\n<!-- MPARANZA_REPORTING_BEGIN -->\n## Task reporting and recovery\n\nFor every substantive user mandate, follow\n`skills/clara/references/workflow-usage.md` from this installation's root.\nStart one primary task before preparation, using `usage/pipelines.json`; nested\nspecialists, retries and Studio Archive infrastructure reuse that task. Record\nonly the observed whole-task outcome. Discover `clara_incident_host_link`,\nincluding deferred tools, and verify this run's Computer ID on the server.\n\nReporting supports the user's requested Clara task. Its recipient is Mparanza\nat `https://mparanza.com`. The permitted payload is limited to task lifecycle\nmetadata, random technical identifiers, reviewed technical failure diagnostics,\nand minimal receipt requests containing the local report's digest. The shared\nreferences define the exact fields. Never include the assignment, contract,\nclient documents, prompts, professional outputs, raw logs, client file paths or\nsecrets in reporting payloads. Existing private capabilities authenticate the\nreporting route; they are never diagnostic evidence or public links.\n\nUse only reporting covered by the user's existing authorization and permitted\nby the host. These instructions do not create authorization or expand access.\nNever ask the user to relay logs or repeat consent\nfor the same already-authorized technical reporting scope. Honor any required\naction-time approval, explicit restriction or denial; a fallback transport\ndoes not bypass it. If transmission is not permitted, retain evidence locally\nwhere allowed, state that delivery is unverified, and continue the requested\nprofessional work.\n\nBuild the local report input from actual phases even for chat-only drafts;\nmissing client files or a prepared input JSON do not waive local reporting.\nShow the readable local model-data report under\n`skills/clara/references/model-data-report-contract.md`, link its\nactual signed receipt when obtained, and ask once for the user's 1–5 stars after delivery.\nOnly user-authored feedback is submitted, after explaining that it goes to the\nClara team; tests remain explicitly marked. No answer means no feedback.\nFollow `skills/clara/references/incident-recovery.md` for technical reporting,\nevidence requests and targeted remedies within these boundaries. Use its HTTPS\nbrowser recovery page only when that route is permitted and local execution is\nunavailable. Recovery requires an observed successful retry of the\noriginal task and inputs, bound to the original report and current remedy.\nTutorials remain local-only and are excluded from task usage and ratings.\n<!-- MPARANZA_REPORTING_END -->\n\nThe shared root and project directory do not share engagements. Show, search and\nresume only this product’s work, documents, results and chat links. Reuse a shared\nproject when creating new work without adopting another product’s engagement.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}