← 101CONTENT HISTORY

Update to 101

Snapshot Nov 11, 2026 · 00:08 UTC · version 2.0.6

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for contractor-invitations

Full description — Now says: 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.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save 101 and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 9, 2026 · 00:21 UTC

Use when an existing user needs to be invited to a company as a contractor, including as a customer.

After

Nov 11, 2026 · 00:08 UTC

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.

Skill instructions

Before

Nov 9, 2026 · 00:21 UTC

including as a customer. optional_tools: [] The 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.

After

Nov 11, 2026 · 00:08 UTC

or a virtual contractor card without a 101 account is needed, including a customer. optional_tools: - create_contractor The tool does not register a new user or change existing members' roles. If the person is not in 101 or no invitati...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,6 +1,6 @@
 ---
 name: contractor-invitations
-description: Use when an existing user needs to be invited to a company as a contractor, including as a customer.
+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.
 version: "1.0.0"
 role: primary
 invocation: internal
@@ -14,7 +14,8 @@
   - search_users
   - list_contractors
   - create_contractor_and_invite
-optional_tools: []
+optional_tools:
+  - create_contractor
 resources:
   - path: ../shared-resources/context-and-identity.md
     kind: semantic-guide
@@ -37,7 +38,7 @@
 4. 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.
 5. Complete standard confirmation. Report the actual invitation result; do not promise acceptance by the user. If the outcome is unknown, first check current state.
 
-The 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.
+The 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.
 
 General rules: [context-and-identity](../shared-resources/context-and-identity.md), [safety-and-permissions](../shared-resources/safety-and-permissions.md).
 Before a write, use [entity-resolution](../entity-resolution/SKILL.md), [write-preflight](../write-preflight/SKILL.md).
Full technical diff · 2 changed fields

changed /description

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."

changed /skill_md_contents

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"
Full snapshot data
{
  "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"
}

SHA-256 of public snapshot: a1ef4bda9fb3b3baf49e23e30d229e84713a35f7dde430d00ab4bcd1a0f2fc63