← 101CONTENT HISTORY

Update to 101

Snapshot Nov 17, 2026 · 00:11 UTC · version 2.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for entity-resolution

Skill instructions — Now says: version: "1.0.1" - get_company_fund For `list_bills`, use `project_guid` or `company_guid`. Use `fund_guid` from `get_company_fund.funds` only with...

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.

Skill instructions

Before

Nov 9, 2026 · 00:21 UTC

version: "1.0.0"

After

Nov 17, 2026 · 00:11 UTC

version: "1.0.1" - get_company_fund For `list_bills`, use `project_guid` or `company_guid`. Use `fund_guid` from `get_company_fund.funds` only with `company_guid`. For company queries, omitting `fund_guid` selects the main fund. Use `l...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,7 +1,7 @@
 ---
 name: entity-resolution
 description: Use when an internal 101 workflow needs to identify a user, company, project, contractor, event, Wiki, page, task, expense category or price list from a human description.
-version: "1.0.0"
+version: "1.0.1"
 role: helper
 invocation: internal
 intents:
@@ -20,6 +20,7 @@
   - list_price_lists
   - get_current_screen
   - get_company
+  - get_company_fund
 resources:
   - path: ../shared-resources/context-and-identity.md
     kind: semantic-guide
@@ -41,4 +42,6 @@
 4. Automatically select one exact accessible match. Present multiple candidates by name and distinguishing context. Result order and a partial match do not prove the choice.
 5. Return the type, identifier, name, verified company/project and result source. Keep GUIDs for commands; use names in ordinary replies.
 
+For `list_bills`, use `project_guid` or `company_guid`. Use `fund_guid` from `get_company_fund.funds` only with `company_guid`. For company queries, omitting `fund_guid` selects the main fund. Use `list_mode=eventSelection` to select an event category. `archived=true` selects archived only, default is active. `usage_type=expense` selects report/estimate categories, `agent` selects commission categories. An empty successful list means no accessible matches for the filters.
+
 If there is no result, access is denied or ambiguity remains, return the reason to the goal owner. Suggest a short question only when the answer can remove the obstacle; do not ask again for known information. Do not substitute a similar entity.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: entity-resolution\ndescription: Use when an internal 101 workflow needs to identify a user, company, project, contractor, event, Wiki, page, task, expense category or price list from a human description.\nversion: \"1.0.0\"\nrole: helper\ninvocation: internal\nintents:\n  - entities.resolve\ndepends_on: []\nrequired_tools:\n  - whoami\noptional_tools:\n  - search_users\n  - list_projects\n  - list_contractors\n  - list_events\n  - list_wikis\n  - list_tasks\n  - list_bills\n  - list_price_lists\n  - get_current_screen\n  - get_company\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Entity Resolution\n\nReceive the object type, description and search scope from the primary workflow. Return a verified entity; the primary workflow owns the user's goal.\n\n1. Preserve an explicit company or the company of the target object. When the request requires a company and none is set, use a non-null `whoami.default_company`; otherwise return the need to choose a company to the goal owner. Return the same reason for `company_selection_required`.\n2. If the user refers to the current screen, obtain the available context through `get_current_screen`. It helps identify the object but does not replace an access check.\n3. Check the selected company's information through `get_company` when the goal needs it. Use an appropriate search or list with server filters and pagination. Preserve the requested scope; do not turn a personal task list into one company's list without a reason.\n4. Automatically select one exact accessible match. Present multiple candidates by name and distinguishing context. Result order and a partial match do not prove the choice.\n5. Return the type, identifier, name, verified company/project and result source. Keep GUIDs for commands; use names in ordinary replies.\n\nIf there is no result, access is denied or ambiguity remains, return the reason to the goal owner. Suggest a short question only when the answer can remove the obstacle; do not ask again for known information. Do not substitute a similar entity.\n"
AFTER
"---\nname: entity-resolution\ndescription: Use when an internal 101 workflow needs to identify a user, company, project, contractor, event, Wiki, page, task, expense category or price list from a human description.\nversion: \"1.0.1\"\nrole: helper\ninvocation: internal\nintents:\n  - entities.resolve\ndepends_on: []\nrequired_tools:\n  - whoami\noptional_tools:\n  - search_users\n  - list_projects\n  - list_contractors\n  - list_events\n  - list_wikis\n  - list_tasks\n  - list_bills\n  - list_price_lists\n  - get_current_screen\n  - get_company\n  - get_company_fund\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Entity Resolution\n\nReceive the object type, description and search scope from the primary workflow. Return a verified entity; the primary workflow owns the user's goal.\n\n1. Preserve an explicit company or the company of the target object. When the request requires a company and none is set, use a non-null `whoami.default_company`; otherwise return the need to choose a company to the goal owner. Return the same reason for `company_selection_required`.\n2. If the user refers to the current screen, obtain the available context through `get_current_screen`. It helps identify the object but does not replace an access check.\n3. Check the selected company's information through `get_company` when the goal needs it. Use an appropriate search or list with server filters and pagination. Preserve the requested scope; do not turn a personal task list into one company's list without a reason.\n4. Automatically select one exact accessible match. Present multiple candidates by name and distinguishing context. Result order and a partial match do not prove the choice.\n5. Return the type, identifier, name, verified company/project and result source. Keep GUIDs for commands; use names in ordinary replies.\n\nFor `list_bills`, use `project_guid` or `company_guid`. Use `fund_guid` from `get_company_fund.funds` only with `company_guid`. For company queries, omitting `fund_guid` selects the main fund. Use `list_mode=eventSelection` to select an event category. `archived=true` selects archived only, default is active. `usage_type=expense` selects report/estimate categories, `agent` selects commission categories. An empty successful list means no accessible matches for the filters.\n\nIf there is no result, access is denied or ambiguity remains, return the reason to the goal owner. Suggest a short question only when the answer can remove the obstacle; do not ask again for known information. Do not substitute a similar entity.\n"
Full snapshot data
{
  "description": "Use when an internal 101 workflow needs to identify a user, company, project, contractor, event, Wiki, page, task, expense category or price list from a human description.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 43
    }
  ],
  "name": "entity-resolution",
  "skill_md_contents": "---\nname: entity-resolution\ndescription: Use when an internal 101 workflow needs to identify a user, company, project, contractor, event, Wiki, page, task, expense category or price list from a human description.\nversion: \"1.0.1\"\nrole: helper\ninvocation: internal\nintents:\n  - entities.resolve\ndepends_on: []\nrequired_tools:\n  - whoami\noptional_tools:\n  - search_users\n  - list_projects\n  - list_contractors\n  - list_events\n  - list_wikis\n  - list_tasks\n  - list_bills\n  - list_price_lists\n  - get_current_screen\n  - get_company\n  - get_company_fund\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Entity Resolution\n\nReceive the object type, description and search scope from the primary workflow. Return a verified entity; the primary workflow owns the user's goal.\n\n1. Preserve an explicit company or the company of the target object. When the request requires a company and none is set, use a non-null `whoami.default_company`; otherwise return the need to choose a company to the goal owner. Return the same reason for `company_selection_required`.\n2. If the user refers to the current screen, obtain the available context through `get_current_screen`. It helps identify the object but does not replace an access check.\n3. Check the selected company's information through `get_company` when the goal needs it. Use an appropriate search or list with server filters and pagination. Preserve the requested scope; do not turn a personal task list into one company's list without a reason.\n4. Automatically select one exact accessible match. Present multiple candidates by name and distinguishing context. Result order and a partial match do not prove the choice.\n5. Return the type, identifier, name, verified company/project and result source. Keep GUIDs for commands; use names in ordinary replies.\n\nFor `list_bills`, use `project_guid` or `company_guid`. Use `fund_guid` from `get_company_fund.funds` only with `company_guid`. For company queries, omitting `fund_guid` selects the main fund. Use `list_mode=eventSelection` to select an event category. `archived=true` selects archived only, default is active. `usage_type=expense` selects report/estimate categories, `agent` selects commission categories. An empty successful list means no accessible matches for the filters.\n\nIf there is no result, access is denied or ambiguity remains, return the reason to the goal owner. Suggest a short question only when the answer can remove the obstacle; do not ask again for known information. Do not substitute a similar entity.\n"
}

SHA-256 of public snapshot: 4f03047d27309bddb5666231b8ca804f5d2fa8cd7c7080d381ac5589a4333fe6