| name | operating-intelligence |
| description | This skill should be used when the user asks to "manage a business object lifecycle", "record an operating ledger", "attribute content to a deal", "operate used-car inventory with MCP", "use lifecycle CLI commands", or "transition an operating object safely". |
| version | 0.1.0 |
Operating Intelligence Lifecycle
Operate generic business lifecycle records through MatriXpost MCP and CLI. Model a vehicle as one template among many, not as a special core type. Keep this skill focused on local business records; do not build, invoke, or describe an agent runtime, publish content, dispatch a provider, or handle secrets.
Start from the operating object
Choose a caller-owned stable ID and a generic kind, such as vehicle, asset, project, or product. Add externalId only when an outside identifier exists. For a used-car template, an external ID may hold a VIN, but never make VIN mandatory or encode it into generic workflows.
Create the object before recording cost, revenue, reimbursement, preparation, sale, receivable, aftersales, or content attribution. Use attributes only for safe descriptive fields. Do not put secrets in attributes: sensitive key names such as token, cookie, password, and session are rejected. Do not scan or reject ordinary business wording merely because it contains one of those words.
Use the safe lifecycle order
- Create or retrieve the object.
- Create immutable directed relations after both endpoint objects exist.
- Append each expense or revenue event as a new immutable ledger entry.
- Link relevant existing publication-history records to the object.
