Case Cloud Case, Calendar, and Team Management

Problem

Law firm operations are usually fragmented across cases, calendars, clients, projects, contracts, and finance. Manually checking case progress, scheduling court dates, and filing case records can easily produce missing entity links or incorrect enum values. This skill wraps the Case Cloud Open API for OA-style legal workflows, making it easier to query active cases, create linked calendar entries, upload case attachments, and review receivables or contracts through natural language.

Core capabilities

• Access model: authorization is based on a PAT Token, with visibility scoped by individual, team administrator, or firm owner roles.
• Case management: supports GET /cases, POST /cases, and PATCH /cases/{code} for case lists, details, stages, and attachments; case creation should first use GET /enums to map controlled values.
• Calendar and records: POST /calendar and PUT /calendar/{id} are the unified entry points; type and linkid connect entries to cases, projects, or clients so records are not left unattached.
• Clients and projects: creation starts from create-form schemas, then maps user input to dynamic fields and confirms before posting.
• Finance and contracts: receivables, payment records, and contracts often return full datasets, so date ranges, statuses, related entities, and owners must be used to narrow results.

Boundaries

• Deletion of cases, calendar entries, clients, or projects is not supported and should be handled in the OA web app.
• High-risk case updates, such as process_code, current_stage_id, or court/unit changes, require explicit user confirmation.
• Time values use Beijing time, and calendar queries should prefer explicit start_date and end_date ranges.
• When duplicate cases are matched, list candidates first and do not link records by guess.