{"id":89940,"plugin_id":"plugin_asdk_app_697254461bb0819199d9f896114e1b98","kind":"skill","collection_source":"plugin_package","comparison_source":"plugin_package","observed_at":"2026-11-11T00:08:12.304Z","digest":"a1ef4bda9fb3b3baf49e23e30d229e84713a35f7dde430d00ab4bcd1a0f2fc63","against":86328,"payload":{"description":"Use when an existing user needs to be invited to a company as a contractor, or a virtual contractor card without a 101 account is needed, including a customer.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":43}],"name":"contractor-invitations","skill_md_contents":"---\nname: contractor-invitations\ndescription: Use when an existing user needs to be invited to a company as a contractor, or a virtual contractor card without a 101 account is needed, including a customer.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - contractors.invite\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - search_users\n  - list_contractors\n  - create_contractor_and_invite\noptional_tools:\n  - create_contractor\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\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Inviting a Member\n\n1. Determine the target company and existing user through `search_users`. If there are several matches, clarify the person using understandable distinguishing details; do not guess GUIDs.\n2. Check `list_contractors`: do not create a duplicate invitation if the required relationship is already confirmed. A row without a status does not prove that the invitation has been accepted.\n3. Obtain an explicit request to invite this person and establish the meaning of their category. Check permissions and the tool schema.\n4. Call `create_contractor_and_invite` with `user_guid` and `company_guid`; pass a verified `category_guid` or a supported category name. For a customer, use `categoryTitle=Заказчик`. Do not pass conflicting category variants.\n5. Complete standard confirmation. Report the actual invitation result; do not promise acceptance by the user. If the outcome is unknown, first check current state.\n\nThe tool does not register a new user or change existing members' roles. If the person is not in 101 or no invitation is needed, create a virtual card: `create_contractor` with `company_guid`, `display_name`, and `category_type` — 4 customer, 2 supplier, 8 contractor, 1 employee, 3 partner. Do not guess the role: if it is unclear, ask. Omit `phone` and `email`; no invitation is sent. After the write, verify the category in the response.\n\nGeneral rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md).\nBefore a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).\n"},"changes":[{"path":"/description","type":"changed","before":"Use when an existing user needs to be invited to a company as a contractor, including as a customer.","after":"Use when an existing user needs to be invited to a company as a contractor, or a virtual contractor card without a 101 account is needed, including a customer."},{"path":"/skill_md_contents","type":"changed","before":"---\nname: contractor-invitations\ndescription: Use when an existing user needs to be invited to a company as a contractor, including as a customer.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - contractors.invite\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - search_users\n  - list_contractors\n  - create_contractor_and_invite\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\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Inviting a Member\n\n1. Determine the target company and existing user through `search_users`. If there are several matches, clarify the person using understandable distinguishing details; do not guess GUIDs.\n2. Check `list_contractors`: do not create a duplicate invitation if the required relationship is already confirmed. A row without a status does not prove that the invitation has been accepted.\n3. Obtain an explicit request to invite this person and establish the meaning of their category. Check permissions and the tool schema.\n4. Call `create_contractor_and_invite` with `user_guid` and `company_guid`; pass a verified `category_guid` or a supported category name. For a customer, use `categoryTitle=Заказчик`. Do not pass conflicting category variants.\n5. Complete standard confirmation. Report the actual invitation result; do not promise acceptance by the user. If the outcome is unknown, first check current state.\n\nThe tool does not register a new user, change existing members' roles, or provide full contractor management. If the user does not exist, state the limitation.\n\nGeneral rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md).\nBefore a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).\n","after":"---\nname: contractor-invitations\ndescription: Use when an existing user needs to be invited to a company as a contractor, or a virtual contractor card without a 101 account is needed, including a customer.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - contractors.invite\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - search_users\n  - list_contractors\n  - create_contractor_and_invite\noptional_tools:\n  - create_contractor\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\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Inviting a Member\n\n1. Determine the target company and existing user through `search_users`. If there are several matches, clarify the person using understandable distinguishing details; do not guess GUIDs.\n2. Check `list_contractors`: do not create a duplicate invitation if the required relationship is already confirmed. A row without a status does not prove that the invitation has been accepted.\n3. Obtain an explicit request to invite this person and establish the meaning of their category. Check permissions and the tool schema.\n4. Call `create_contractor_and_invite` with `user_guid` and `company_guid`; pass a verified `category_guid` or a supported category name. For a customer, use `categoryTitle=Заказчик`. Do not pass conflicting category variants.\n5. Complete standard confirmation. Report the actual invitation result; do not promise acceptance by the user. If the outcome is unknown, first check current state.\n\nThe tool does not register a new user or change existing members' roles. If the person is not in 101 or no invitation is needed, create a virtual card: `create_contractor` with `company_guid`, `display_name`, and `category_type` — 4 customer, 2 supplier, 8 contractor, 1 employee, 3 partner. Do not guess the role: if it is unclear, ask. Omit `phone` and `email`; no invitation is sent. After the write, verify the category in the response.\n\nGeneral rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md).\nBefore a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).\n"}],"summary":"Fields changed: 2. /description, /skill_md_contents.","summary_kind":"deterministic","summary_metadata":{}}