← 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 price-list-management

Full description — Now says: Use for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs.

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 for reading and creating price lists, categories, and positions, and bulk changes to prices and costs.

After

Nov 17, 2026 · 00:11 UTC

Use for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs.

Skill instructions

Before

Nov 9, 2026 · 00:21 UTC

reading and creating price lists, categories, and positions, and bulk changes to prices and costs. version: "1.0.0" 3. `create_price_list`: the company and `name`.

After

Nov 17, 2026 · 00:11 UTC

reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs. version: "1.0.1" - price-lists.update - update_price_list 3. `create_price_list`: the company and `name`. For `updat...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,12 +1,13 @@
 ---
 name: price-list-management
-description: Use for reading and creating price lists, categories, and positions, and bulk changes to prices and costs.
-version: "1.0.0"
+description: Use for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs.
+version: "1.0.1"
 role: primary
 invocation: internal
 intents:
   - price-lists.read
   - price-lists.create
+  - price-lists.update
   - price-lists.positions.update
 depends_on:
   - entity-resolution
@@ -17,6 +18,7 @@
   - get_price_list
 optional_tools:
   - create_price_list
+  - update_price_list
   - create_price_list_category
   - create_price_list_position
   - bulk_update_price_list_positions
@@ -38,7 +40,7 @@
 
 1. Determine the company. Select the price list through `list_price_lists`; read `get_price_list` for categories, positions, attributes, and linked projects. Similar names do not prove the selection.
 2. Before a write, check the explicit action, current entities, permissions, and the current tool schema.
-3. `create_price_list`: the company and `name`. `create_price_list_category`: `price_list_id`, `name`, and, if needed, `parent_id` and allowed attributes. The root is represented by the absence of a parent.
+3. `create_price_list`: the company and `name`. For `update_price_list`, pass `price_list_id` and at least one changed field — `name`, `is_hidden` (hide/show in lists), `default_measurement_unit` (unit ID, `null` clears). `create_price_list_category`: `price_list_id`, `name`, and, if needed, `parent_id` and allowed attributes. The root is represented by the absence of a parent.
 4. `create_price_list_position`: the price list, name, `cost_price`, and `price` are required. Pass the category, unit, and attributes from verified data; do not guess unit identifiers. For the root, omit `category_id`.
 5. `bulk_update_price_list_positions`: select the exact `scope=all|category|positions`, `change_type=amount|percent`, `value`, `target_fields`, and rounding if requested. For “by 10” without a unit, clarify whether it is an amount or a percentage; then clarify the scope if needed. Changing “by an amount” does not mean setting the final price. Do not add cost changes or rounding without a basis.
 6. After a write, reread the price list and check created items or changed values. Report partial completion and denial; do not repeat a write with an unknown outcome.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Use for reading and creating price lists, categories, and positions, and bulk changes to prices and costs."
AFTER
"Use for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs."

changed /skill_md_contents

BEFORE
"---\nname: price-list-management\ndescription: Use for reading and creating price lists, categories, and positions, and bulk changes to prices and costs.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n  - price-lists.read\n  - price-lists.create\n  - price-lists.positions.update\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - list_price_lists\n  - get_price_list\noptional_tools:\n  - create_price_list\n  - create_price_list_category\n  - create_price_list_position\n  - bulk_update_price_list_positions\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# Price Lists\n\n1. Determine the company. Select the price list through `list_price_lists`; read `get_price_list` for categories, positions, attributes, and linked projects. Similar names do not prove the selection.\n2. Before a write, check the explicit action, current entities, permissions, and the current tool schema.\n3. `create_price_list`: the company and `name`. `create_price_list_category`: `price_list_id`, `name`, and, if needed, `parent_id` and allowed attributes. The root is represented by the absence of a parent.\n4. `create_price_list_position`: the price list, name, `cost_price`, and `price` are required. Pass the category, unit, and attributes from verified data; do not guess unit identifiers. For the root, omit `category_id`.\n5. `bulk_update_price_list_positions`: select the exact `scope=all|category|positions`, `change_type=amount|percent`, `value`, `target_fields`, and rounding if requested. For “by 10” without a unit, clarify whether it is an amount or a percentage; then clarify the scope if needed. Changing “by an amount” does not mean setting the final price. Do not add cost changes or rounding without a basis.\n6. After a write, reread the price list and check created items or changed values. Report partial completion and denial; do not repeat a write with an unknown outcome.\n\nDo not promise deletion, renaming, or arbitrary attribute changes for an existing position: there is no separate tool for this. Selecting a price list for a project does not change the price list itself.\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: price-list-management\ndescription: Use for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs.\nversion: \"1.0.1\"\nrole: primary\ninvocation: internal\nintents:\n  - price-lists.read\n  - price-lists.create\n  - price-lists.update\n  - price-lists.positions.update\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - list_price_lists\n  - get_price_list\noptional_tools:\n  - create_price_list\n  - update_price_list\n  - create_price_list_category\n  - create_price_list_position\n  - bulk_update_price_list_positions\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# Price Lists\n\n1. Determine the company. Select the price list through `list_price_lists`; read `get_price_list` for categories, positions, attributes, and linked projects. Similar names do not prove the selection.\n2. Before a write, check the explicit action, current entities, permissions, and the current tool schema.\n3. `create_price_list`: the company and `name`. For `update_price_list`, pass `price_list_id` and at least one changed field — `name`, `is_hidden` (hide/show in lists), `default_measurement_unit` (unit ID, `null` clears). `create_price_list_category`: `price_list_id`, `name`, and, if needed, `parent_id` and allowed attributes. The root is represented by the absence of a parent.\n4. `create_price_list_position`: the price list, name, `cost_price`, and `price` are required. Pass the category, unit, and attributes from verified data; do not guess unit identifiers. For the root, omit `category_id`.\n5. `bulk_update_price_list_positions`: select the exact `scope=all|category|positions`, `change_type=amount|percent`, `value`, `target_fields`, and rounding if requested. For “by 10” without a unit, clarify whether it is an amount or a percentage; then clarify the scope if needed. Changing “by an amount” does not mean setting the final price. Do not add cost changes or rounding without a basis.\n6. After a write, reread the price list and check created items or changed values. Report partial completion and denial; do not repeat a write with an unknown outcome.\n\nDo not promise deletion, renaming, or arbitrary attribute changes for an existing position: there is no separate tool for this. Selecting a price list for a project does not change the price list itself.\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 for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 43
    }
  ],
  "name": "price-list-management",
  "skill_md_contents": "---\nname: price-list-management\ndescription: Use for reading, creating, and editing price lists, creating categories and positions, and bulk changes to prices and costs.\nversion: \"1.0.1\"\nrole: primary\ninvocation: internal\nintents:\n  - price-lists.read\n  - price-lists.create\n  - price-lists.update\n  - price-lists.positions.update\ndepends_on:\n  - entity-resolution\n  - write-preflight\nrequired_tools:\n  - whoami\n  - list_price_lists\n  - get_price_list\noptional_tools:\n  - create_price_list\n  - update_price_list\n  - create_price_list_category\n  - create_price_list_position\n  - bulk_update_price_list_positions\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# Price Lists\n\n1. Determine the company. Select the price list through `list_price_lists`; read `get_price_list` for categories, positions, attributes, and linked projects. Similar names do not prove the selection.\n2. Before a write, check the explicit action, current entities, permissions, and the current tool schema.\n3. `create_price_list`: the company and `name`. For `update_price_list`, pass `price_list_id` and at least one changed field — `name`, `is_hidden` (hide/show in lists), `default_measurement_unit` (unit ID, `null` clears). `create_price_list_category`: `price_list_id`, `name`, and, if needed, `parent_id` and allowed attributes. The root is represented by the absence of a parent.\n4. `create_price_list_position`: the price list, name, `cost_price`, and `price` are required. Pass the category, unit, and attributes from verified data; do not guess unit identifiers. For the root, omit `category_id`.\n5. `bulk_update_price_list_positions`: select the exact `scope=all|category|positions`, `change_type=amount|percent`, `value`, `target_fields`, and rounding if requested. For “by 10” without a unit, clarify whether it is an amount or a percentage; then clarify the scope if needed. Changing “by an amount” does not mean setting the final price. Do not add cost changes or rounding without a basis.\n6. After a write, reread the price list and check created items or changed values. Report partial completion and denial; do not repeat a write with an unknown outcome.\n\nDo not promise deletion, renaming, or arbitrary attribute changes for an existing position: there is no separate tool for this. Selecting a price list for a project does not change the price list itself.\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: 8b5daf8b488dfb325fbbedfaba75e7514ed174a2c1c0ba2678e3060358225095