China Court Litigation Fee Calculator

Problem

In civil, commercial, administrative, enforcement, and preservation matters, court acceptance fees and application fees are often not single fixed amounts. Property cases are calculated by segmented cumulative amounts; enforcement, preservation, and payment orders depend on applied amounts; some items also involve local base fees, statutory ranges, or default lower-bound estimates. When integrating such a calculator, the practical issues are whether case facts are complete, whether amount labels are mixed, whether the calculation basis is traceable, and how to handle mismatches between CLI output and local rules. @user_f26b93e2/litigation-fee-calculator addresses this by turning case fact extraction, CLI parameter construction, backend result consumption, and reviewable output into a fixed workflow.

How It Works

The skill is a calculation skill. Once invoked, it uses deli-cli as the default entry point, runs the common deli-cli preflight to discover available calculation commands in the current skill scope, and then organizes parameters according to the litigation fee CLI guide. Stable rules, segment ratios, caps, and default lower-bound interpretations come from references/ rather than local fallback calculation.

Key steps:
- Extract case facts: identify the fee type first, such as property case acceptance, enforcement, preservation, payment order, bankruptcy, labor disputes, or administrative cases; ask only for missing required facts.
- Preserve amount semantics: keep original labels such as principal claimed, total property subject to division, enforcement subject, and preservation amount; do not merge multiple amounts automatically.
- Invoke backend calculation: the CLI calls a backend MCP calculation service; the skill directory does not contain a local calculation entry point.
- Produce reviewable output: include calculation object, itemized calculation, total, cited rule source, and risk notes; keep amounts to the cent and state the value used for range-based fees.

Boundaries

It is not intended for legal research, case retrieval, or guessing local standards. If the CLI is unavailable, no calculation command is returned, or required fields are missing, the skill should say so instead of silently computing. Range-based fees must not be presented as one nationwide fixed amount; reduction, waiver, and deferral are excluded unless the user provides a court decision or specific applicable facts. When CLI output conflicts with local references/, mark the discrepancy and recommend manual review.