← 101CONTENT HISTORY
WHAT CHANGED
Update to 101
Snapshot Nov 9, 2026 · 00:21 UTC · version 2.0.5
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save 101 and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when an internal 101 request requires managing CRM pipelines, stages, deals, or distribution rules through the current CRM API.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
},
{
"relative_path": "references/crm-orchestration.md",
"size_in_bytes": 5336
}
],
"name": "crm-management",
"skill_md_contents": "---\nname: crm-management\ndescription: Use when an internal 101 request requires managing CRM pipelines, stages, deals, or distribution rules through the current CRM API.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - crm.pipeline.manage\n - crm.funnel.manage\n - crm.deal.manage\n - crm.distribution.manage\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_crm_pipelines\n - create_crm_pipeline\n - reorder_crm_pipelines\n - get_crm_pipeline\n - edit_crm_pipeline\n - delete_crm_pipeline\n - create_crm_funnel\n - reorder_crm_funnels\n - edit_crm_funnel\n - delete_crm_funnel\n - create_crm_deal\n - get_crm_deal\n - edit_crm_deal\n - delete_crm_deal\n - move_crm_deal\n - list_crm_distribution_rules\n - create_crm_distribution_rule\n - get_crm_distribution_rule_schema\n - reorder_crm_distribution_rules\n - edit_crm_distribution_rule\n - delete_crm_distribution_rule\n - list_contractors\n - search_users\noptional_tools: []\nresources:\n - path: ../shared-resources/context-and-identity.md\n kind: semantic-guide\n required: true\n - path: ../shared-resources/safety-and-permissions.md\n kind: semantic-guide\n required: true\n - path: references/crm-orchestration.md\n kind: semantic-guide\n required: true\ncompletion:\n statuses:\n - готово\n - частично\n - заблокировано\n---\n\n# CRM Management\n\nBefore the selected operation, read `references/crm-orchestration.md`; take arguments from the current tool schema. CRM work is a primary workflow, without its own dispatcher or a new interface.\n\n1. Determine the company and pipeline through `whoami` and `list_crm_pipelines`.\n2. Read stages, deals, sources, and fields through `get_crm_pipeline`; read an individual deal through `get_crm_deal`. Resolve the contact through `list_contractors` / `search_users`. Obtain rules and allowed conditions through `list_crm_distribution_rules` / `get_crm_distribution_rule_schema`.\n3. Clarify the remaining material distinction with one short question. Do not choose the business meaning for the user; retain defaults specified by the contract. Do not ask again for known answers.\n4. Before a write, apply `entity-resolution` and `write-preflight`. `payload` matches the body of the current REST request; URL parameters identify the existing entity. Build complete ordering lists from fresh state.\n5. Ordinary creation, editing, moving, and reordering follow the standard policy. Deletion requires two-step server confirmation with `_confirmation_token`.\n6. For generated distribution rules, before creation, editing, or reordering, show the final logic, priority, candidates, and fallback rule; obtain confirmation of that specific plan. This is approval of the intended operation, separate from the deletion token.\n7. After a write, check the response and perform the required verification read. On a conflict or partially completed plan, stop, retain receipts, and report the result.\n\nDo not imitate unavailable tools for pipeline members, the field builder, pages, or sources through other APIs. Return human-readable names of the changed entities and material limitations.\n"
}SHA-256 of public snapshot: 5ed64eb6173f1d511716fbbb9457b2bea0054e129b98bf6596b31f7015d057ab