{"id":11913,"plugin_id":"plugin_asdk_app_6a6759afdd20819185b27e68d2eccbad","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:00:31.688Z","digest":"b6f60a1c6064d75dfde79480dbf925fd70297f75c0d4d02238f55859ff797716","against":null,"payload":{"name":"june-create-case-document","description":"Create a case document in JUNE from an approved template, supplied text, or an uploaded local file. Use when a user asks to draft, render, file, or upload a document for a specific JUNE case, including DOCX and PDF output.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":461}],"skill_md_contents":"---\nname: june-create-case-document\ndescription: Create a case document in JUNE from an approved template, supplied text, or an uploaded local file. Use when a user asks to draft, render, file, or upload a document for a specific JUNE case, including DOCX and PDF output.\n---\n\n# Create a JUNE case document\n\nIdentify the exact case first. Document creation writes data and can create duplicates, so do not guess identifiers or retry automatically.\n\n## Choose the path\n\n### JUNE template\n\n1. Resolve the case with `get_case_by_reference` or `get_case_context`.\n2. Call `list_document_templates` for that case before creation.\n3. Select only a returned `template_id`, supported output format, and returned addressee `participant_id`. A contact ID is not a participant ID.\n4. If the template is blocked or the intended addressee is absent, explain the missing participant role. Use `create_contact` and `add_case_participant` only when the user asks to add that participant.\n5. Confirm the case, template, addressee, format, and any claims-account options when they are not already explicit.\n6. Call `create_case_document` once.\n\nFor PDF, report the filed document ID. For DOCX, surface the short-lived download URL immediately and explain that the file is not yet filed in the case. If the template is designed for interactive editing, retain that warning.\n\n### Text document\n\nUse `create_document_from_text` only after confirming the target case, safe filename, direction, document type, and final text. Preserve user-supplied wording unless asked to edit it.\n\n### Local file upload\n\nUse `request_document_upload` and `finalize_document_upload` only when both tools are available and the client can upload the file bytes to the returned URL with every required header. Resolve `document_type` with `get_value_list` first. Use only letters, digits, spaces, dot, hyphen, and underscore in filenames.\n\nIf the client cannot perform the binary upload, tell the user to download or edit the file and file it through JUNE instead of pretending the upload completed.\n\n## Safety and result\n\nEvery `create_case_document` call creates a new document. After an error or timeout, check the case before retrying. Do not expose a short-lived download URL beyond the user who requested it. Report the case reference, filename, output format, whether it was filed, document ID when present, and the required next step.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}