Update to 101
Snapshot Nov 17, 2026 · 00:11 UTC · version 2.1.0
Collection source: downloaded plugin package.
Instructions updated for task-management
Skill instructions — Now says: version: "1.0.1" - Request changes with `update_task(status="changes_requested")` — reviewer only, from `on_review`, with `needsReview=true` and...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 11, 2026 · 00:08 UTC
version: "1.0.0"
Nov 17, 2026 · 00:11 UTC
version: "1.0.1" - Request changes with `update_task(status="changes_requested")` — reviewer only, from `on_review`, with `needsReview=true` and `permissions.canRequestChanges=true`. The timer is stopped. Resume work through `in_progress...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,7 +1,7 @@ --- name: task-management description: Use for searching, reading, creating, editing, and deleting tasks, comments, and bulk actions. -version: "1.0.0" +version: "1.0.1" role: primary invocation: internal intents: @@ -61,6 +61,7 @@ - `create_task`: `title` is required; pass the company, project, assignee, watchers, deadlines, and links according to the request. `description_blocks` creates the task body together with the task; do not create a separate Wiki page for it. `recurrence` requires `due_at`. - `update_task`: pass only fields being changed. Clear values through the corresponding `clear_*`; `watcher_guids` replaces the entire list. Changing recurrence on an occurrence affects the series template. +- Request changes with `update_task(status="changes_requested")` — reviewer only, from `on_review`, with `needsReview=true` and `permissions.canRequestChanges=true`. The timer is stopped. Resume work through `in_progress`. Find these tasks with `list_tasks(status="changes_requested")`. - `delete_task`: only upon an explicit request to delete the specified task; the server checks permissions. - `update_tasks_bulk`: up to 100 verified tasks per call and one action from the schema. For assignment, omitting `assignee_guid` removes the assignee. Distinguish successful changes and `skipped`; skipped items mean a partial result. - `add_task_comment`: a text comment from the conversation. The tool does not accept attachments; do not promise to send them this way.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: task-management\ndescription: Use for searching, reading, creating, editing, and deleting tasks, comments, and bulk actions.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - tasks.create\n - tasks.delete\n - tasks.bulk\n - tasks.list\n - tasks.read\n - tasks.open\n - tasks.update\n - tasks.comment\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_tasks\n - get_task\n - show_result\noptional_tools:\n - create_task\n - create_tasks_bulk\n - update_task\n - delete_task\n - update_tasks_bulk\n - open_app_screen\n - search_users\n - list_task_comments\n - add_task_comment\n - list_contractors\n - upload_files\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# Task Management\n\n## Reading and Presentation\n\n- `list_tasks`: choose `scope` according to the request. `my`, `created`, `watching`, and `recurring` do not require the `company_guid` parameter, but the initial MCP check and the general rule for continuing the goal still apply; `company` requires `company_guid`, and `project` requires `project_guid`. Preserve filters, dates, sorting, and pagination. If “for today” or “today” does not identify the date in context, clarify whether the user means due today or created today; `due_*` and `created_*` are not interchangeable.\n- Resolve an individual task through `entity-resolution`, then read `get_task`. Read comments separately through `list_task_comments`.\n- In chat, present the result through the issued `structuredContent.presentation.token` and available `show_result`. For an explicitly requested application screen, use `open_app_screen` with a verified task; a widget and an application screen are different actions.\n\n## Writes\n\nBefore a write, apply `write-preflight` and the current tool schema.\n\n- `create_task`: `title` is required; pass the company, project, assignee, watchers, deadlines, and links according to the request. `description_blocks` creates the task body together with the task; do not create a separate Wiki page for it. `recurrence` requires `due_at`.\n- `update_task`: pass only fields being changed. Clear values through the corresponding `clear_*`; `watcher_guids` replaces the entire list. Changing recurrence on an occurrence affects the series template.\n- `delete_task`: only upon an explicit request to delete the specified task; the server checks permissions.\n- `update_tasks_bulk`: up to 100 verified tasks per call and one action from the schema. For assignment, omitting `assignee_guid` removes the assignee. Distinguish successful changes and `skipped`; skipped items mean a partial result.\n- `add_task_comment`: a text comment from the conversation. The tool does not accept attachments; do not promise to send them this way.\n\n`set_task_assignee` and `submit_task_comment` are available only to the application. The widget uses them for the assignee and a comment with `file_list`. The model does not substitute ordinary calls for these actions. Upload files with a supported tool; pass only server-issued identifiers.\n\nAfter a write, reread state if the response does not contain a fresh card. Show confirmed names, status, and material omissions; show GUIDs upon request.\n\n## Bulk task creation\n\n- Commands: use `create_task` for a new standalone task; use `create_tasks_bulk` for a list, its continuation, and row retries, including a single row. `update_tasks_bulk` only modifies existing tasks.\n- Input: only `items`, with 1–50 items. Split larger lists into batches of up to 50, preserving original order and numbering. Each item requires `title` and `external_id`, plus `create_task` fields. Repeat shared values in the relevant items; specify the resolved company explicitly. If no assignee is specified, the current user is assigned. The task and `description_blocks` are created together; `recurrence` requires `due_at`.\n- IDs: assign `external_id` before the first call; use 1–64 characters from `[A-Za-z0-9:_-]`, with no duplicates within the request. Example: `assistant:20261110-k7f2:07`. Use one list identifier across all batches and unique row numbers; use a new identifier for a new list. Preserve the mapping between each row, its ID, and submitted fields.\n- Interrupted call or lost response: retry the original batch with the same IDs, fields, user, and companies. Tasks already created return with `already_existed=true`. Correct rows from `failed` using their original IDs. A new ID, user, or company breaks duplicate protection; deleting a task does not release its ID.\n- Existing ID: a retry does not change fields or description. Check the task against the goal; apply changes through a separate supported command. A deleted task returned in the response has not been restored.\n- Response: `created` contains new and previously created tasks with `task` and `wikiPage`; `failed` contains row errors. Separate counters: `meta.created`, `meta.already_existed`, `meta.failed`. Match by `external_id`, not array position. A successful call does not mean all rows succeeded; do not count previously existing tasks as new.\n- Write result: task + description is an atomic write; a batch is not. A row error does not roll back other rows. For partial success, report confirmed results, error reasons, and remaining work; correct and retry only failed rows with their original IDs. If the outcome is unknown, retry the original batch. Request errors `9447` (size), `9448` (ID), and `9449` (duplicate IDs) create nothing.\n- Confirmation: an explicit request to create tasks is required; `create_tasks_bulk` has no additional server confirmation. Do not add your own; if the current command requests confirmation, follow its standard procedure.\n"
"---\nname: task-management\ndescription: Use for searching, reading, creating, editing, and deleting tasks, comments, and bulk actions.\nversion: \"1.0.1\"\nrole: primary\ninvocation: internal\nintents:\n - tasks.create\n - tasks.delete\n - tasks.bulk\n - tasks.list\n - tasks.read\n - tasks.open\n - tasks.update\n - tasks.comment\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_tasks\n - get_task\n - show_result\noptional_tools:\n - create_task\n - create_tasks_bulk\n - update_task\n - delete_task\n - update_tasks_bulk\n - open_app_screen\n - search_users\n - list_task_comments\n - add_task_comment\n - list_contractors\n - upload_files\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# Task Management\n\n## Reading and Presentation\n\n- `list_tasks`: choose `scope` according to the request. `my`, `created`, `watching`, and `recurring` do not require the `company_guid` parameter, but the initial MCP check and the general rule for continuing the goal still apply; `company` requires `company_guid`, and `project` requires `project_guid`. Preserve filters, dates, sorting, and pagination. If “for today” or “today” does not identify the date in context, clarify whether the user means due today or created today; `due_*` and `created_*` are not interchangeable.\n- Resolve an individual task through `entity-resolution`, then read `get_task`. Read comments separately through `list_task_comments`.\n- In chat, present the result through the issued `structuredContent.presentation.token` and available `show_result`. For an explicitly requested application screen, use `open_app_screen` with a verified task; a widget and an application screen are different actions.\n\n## Writes\n\nBefore a write, apply `write-preflight` and the current tool schema.\n\n- `create_task`: `title` is required; pass the company, project, assignee, watchers, deadlines, and links according to the request. `description_blocks` creates the task body together with the task; do not create a separate Wiki page for it. `recurrence` requires `due_at`.\n- `update_task`: pass only fields being changed. Clear values through the corresponding `clear_*`; `watcher_guids` replaces the entire list. Changing recurrence on an occurrence affects the series template.\n- Request changes with `update_task(status=\"changes_requested\")` — reviewer only, from `on_review`, with `needsReview=true` and `permissions.canRequestChanges=true`. The timer is stopped. Resume work through `in_progress`. Find these tasks with `list_tasks(status=\"changes_requested\")`.\n- `delete_task`: only upon an explicit request to delete the specified task; the server checks permissions.\n- `update_tasks_bulk`: up to 100 verified tasks per call and one action from the schema. For assignment, omitting `assignee_guid` removes the assignee. Distinguish successful changes and `skipped`; skipped items mean a partial result.\n- `add_task_comment`: a text comment from the conversation. The tool does not accept attachments; do not promise to send them this way.\n\n`set_task_assignee` and `submit_task_comment` are available only to the application. The widget uses them for the assignee and a comment with `file_list`. The model does not substitute ordinary calls for these actions. Upload files with a supported tool; pass only server-issued identifiers.\n\nAfter a write, reread state if the response does not contain a fresh card. Show confirmed names, status, and material omissions; show GUIDs upon request.\n\n## Bulk task creation\n\n- Commands: use `create_task` for a new standalone task; use `create_tasks_bulk` for a list, its continuation, and row retries, including a single row. `update_tasks_bulk` only modifies existing tasks.\n- Input: only `items`, with 1–50 items. Split larger lists into batches of up to 50, preserving original order and numbering. Each item requires `title` and `external_id`, plus `create_task` fields. Repeat shared values in the relevant items; specify the resolved company explicitly. If no assignee is specified, the current user is assigned. The task and `description_blocks` are created together; `recurrence` requires `due_at`.\n- IDs: assign `external_id` before the first call; use 1–64 characters from `[A-Za-z0-9:_-]`, with no duplicates within the request. Example: `assistant:20261110-k7f2:07`. Use one list identifier across all batches and unique row numbers; use a new identifier for a new list. Preserve the mapping between each row, its ID, and submitted fields.\n- Interrupted call or lost response: retry the original batch with the same IDs, fields, user, and companies. Tasks already created return with `already_existed=true`. Correct rows from `failed` using their original IDs. A new ID, user, or company breaks duplicate protection; deleting a task does not release its ID.\n- Existing ID: a retry does not change fields or description. Check the task against the goal; apply changes through a separate supported command. A deleted task returned in the response has not been restored.\n- Response: `created` contains new and previously created tasks with `task` and `wikiPage`; `failed` contains row errors. Separate counters: `meta.created`, `meta.already_existed`, `meta.failed`. Match by `external_id`, not array position. A successful call does not mean all rows succeeded; do not count previously existing tasks as new.\n- Write result: task + description is an atomic write; a batch is not. A row error does not roll back other rows. For partial success, report confirmed results, error reasons, and remaining work; correct and retry only failed rows with their original IDs. If the outcome is unknown, retry the original batch. Request errors `9447` (size), `9448` (ID), and `9449` (duplicate IDs) create nothing.\n- Confirmation: an explicit request to create tasks is required; `create_tasks_bulk` has no additional server confirmation. Do not add your own; if the current command requests confirmation, follow its standard procedure.\n"
Full snapshot data
{
"description": "Use for searching, reading, creating, editing, and deleting tasks, comments, and bulk actions.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
}
],
"name": "task-management",
"skill_md_contents": "---\nname: task-management\ndescription: Use for searching, reading, creating, editing, and deleting tasks, comments, and bulk actions.\nversion: \"1.0.1\"\nrole: primary\ninvocation: internal\nintents:\n - tasks.create\n - tasks.delete\n - tasks.bulk\n - tasks.list\n - tasks.read\n - tasks.open\n - tasks.update\n - tasks.comment\ndepends_on:\n - entity-resolution\n - write-preflight\nrequired_tools:\n - whoami\n - list_tasks\n - get_task\n - show_result\noptional_tools:\n - create_task\n - create_tasks_bulk\n - update_task\n - delete_task\n - update_tasks_bulk\n - open_app_screen\n - search_users\n - list_task_comments\n - add_task_comment\n - list_contractors\n - upload_files\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# Task Management\n\n## Reading and Presentation\n\n- `list_tasks`: choose `scope` according to the request. `my`, `created`, `watching`, and `recurring` do not require the `company_guid` parameter, but the initial MCP check and the general rule for continuing the goal still apply; `company` requires `company_guid`, and `project` requires `project_guid`. Preserve filters, dates, sorting, and pagination. If “for today” or “today” does not identify the date in context, clarify whether the user means due today or created today; `due_*` and `created_*` are not interchangeable.\n- Resolve an individual task through `entity-resolution`, then read `get_task`. Read comments separately through `list_task_comments`.\n- In chat, present the result through the issued `structuredContent.presentation.token` and available `show_result`. For an explicitly requested application screen, use `open_app_screen` with a verified task; a widget and an application screen are different actions.\n\n## Writes\n\nBefore a write, apply `write-preflight` and the current tool schema.\n\n- `create_task`: `title` is required; pass the company, project, assignee, watchers, deadlines, and links according to the request. `description_blocks` creates the task body together with the task; do not create a separate Wiki page for it. `recurrence` requires `due_at`.\n- `update_task`: pass only fields being changed. Clear values through the corresponding `clear_*`; `watcher_guids` replaces the entire list. Changing recurrence on an occurrence affects the series template.\n- Request changes with `update_task(status=\"changes_requested\")` — reviewer only, from `on_review`, with `needsReview=true` and `permissions.canRequestChanges=true`. The timer is stopped. Resume work through `in_progress`. Find these tasks with `list_tasks(status=\"changes_requested\")`.\n- `delete_task`: only upon an explicit request to delete the specified task; the server checks permissions.\n- `update_tasks_bulk`: up to 100 verified tasks per call and one action from the schema. For assignment, omitting `assignee_guid` removes the assignee. Distinguish successful changes and `skipped`; skipped items mean a partial result.\n- `add_task_comment`: a text comment from the conversation. The tool does not accept attachments; do not promise to send them this way.\n\n`set_task_assignee` and `submit_task_comment` are available only to the application. The widget uses them for the assignee and a comment with `file_list`. The model does not substitute ordinary calls for these actions. Upload files with a supported tool; pass only server-issued identifiers.\n\nAfter a write, reread state if the response does not contain a fresh card. Show confirmed names, status, and material omissions; show GUIDs upon request.\n\n## Bulk task creation\n\n- Commands: use `create_task` for a new standalone task; use `create_tasks_bulk` for a list, its continuation, and row retries, including a single row. `update_tasks_bulk` only modifies existing tasks.\n- Input: only `items`, with 1–50 items. Split larger lists into batches of up to 50, preserving original order and numbering. Each item requires `title` and `external_id`, plus `create_task` fields. Repeat shared values in the relevant items; specify the resolved company explicitly. If no assignee is specified, the current user is assigned. The task and `description_blocks` are created together; `recurrence` requires `due_at`.\n- IDs: assign `external_id` before the first call; use 1–64 characters from `[A-Za-z0-9:_-]`, with no duplicates within the request. Example: `assistant:20261110-k7f2:07`. Use one list identifier across all batches and unique row numbers; use a new identifier for a new list. Preserve the mapping between each row, its ID, and submitted fields.\n- Interrupted call or lost response: retry the original batch with the same IDs, fields, user, and companies. Tasks already created return with `already_existed=true`. Correct rows from `failed` using their original IDs. A new ID, user, or company breaks duplicate protection; deleting a task does not release its ID.\n- Existing ID: a retry does not change fields or description. Check the task against the goal; apply changes through a separate supported command. A deleted task returned in the response has not been restored.\n- Response: `created` contains new and previously created tasks with `task` and `wikiPage`; `failed` contains row errors. Separate counters: `meta.created`, `meta.already_existed`, `meta.failed`. Match by `external_id`, not array position. A successful call does not mean all rows succeeded; do not count previously existing tasks as new.\n- Write result: task + description is an atomic write; a batch is not. A row error does not roll back other rows. For partial success, report confirmed results, error reasons, and remaining work; correct and retry only failed rows with their original IDs. If the outcome is unknown, retry the original batch. Request errors `9447` (size), `9448` (ID), and `9449` (duplicate IDs) create nothing.\n- Confirmation: an explicit request to create tasks is required; `create_tasks_bulk` has no additional server confirmation. Do not add your own; if the current command requests confirmation, follow its standard procedure.\n"
}SHA-256 of public snapshot: 1a987b27af0364ca5ca4a77ffa2fc86397b9ccfc90f33d8a30825bc7f5476821