Jinbi Smart Property Management CLI

Problem

Property operations such as work orders, visits, collections, and inspections are spread across multiple CLI modules. If a model guesses endpoints, fills parameters from memory, or calls unregistered commands, it can create unauthorized actions, broken workflows, and results that are hard to reproduce. This skill constrains those calls to a deterministic route: it only handles requests registered in the current Go ycli build and allowed by the module allowlist.

How It Works

• Keyword routing: signals such as order, visit, daojia, charge, and collection select the matching scene.
• Scene-document priority: commands, parameters, and examples come from jinbi_enter_scene or pre-routing, avoiding ad hoc reads of scattered docs.
• Pre-execution checks: validate module whitelist, Go registered entry, accessKey, and required business parameters.
• Controlled invocation: business commands run through sh ./scripts/jinbi-cli.sh, avoiding local binary searches or manual config edits.
• Tight output: success returns only the result; failure returns a fixed message, without exposing command names, flags, or debugging steps.

Boundaries

It targets concrete property-management operations, not general chat, unregistered commands, guessed APIs, or resource IDs recovered from history. It stops with a short prompt when parameters, permissions, or module documentation are missing.