← 101CONTENT HISTORY
WHAT CHANGED
changed
Update to 101
Snapshot Nov 11, 2026 · 00:08 UTC · version 2.0.6
Collection source: downloaded plugin package.
Instructions updated for company-creation
Skill instructions — Now says: as the next step toward the original goal; offer waiting for an invitation if the user has indicated that this is their intended path.
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
or wait for an invitation.
After
Nov 11, 2026 · 00:08 UTC
as the next step toward the original goal; offer waiting for an invitation if the user has indicated that this is their intended path.
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -31,7 +31,7 @@ Create one company through `create_company`: the current user becomes the owner. No company selection is required beforehand. 1. For an explicit request to create a company, obtain `title`. If the name is missing, ask for it; do not invent it from personal data. -2. If there are no companies yet and no choice has been made, offer to create their own company or wait for an invitation. If creation has already been chosen, ask only for the missing name. The offer itself does not authorize a write. +2. If there are no companies yet and no choice has been made, offer to create their own company as the next step toward the original goal; offer waiting for an invitation if the user has indicated that this is their intended path. If creation has already been chosen, ask only for the missing name. The offer itself does not authorize a write. 3. Pass `code` only if the user provided the code. Requisites and other optional fields must come only from supplied data. 4. Apply `write-preflight`, excluding the requirement for an existing company, and the standard confirmation policy. An explicit request with a name does not require additional approval of your own. 5. After success, use the response as confirmation. If the response is lost, first check `whoami`; a match by name alone does not prove creation and does not authorize a retry.
Full technical diff · 1 changed fields
changed /skill_md_contents
BEFORE
"---\nname: company-creation\ndescription: Use when a person asks to create a new company in 101 or does not yet have a company in 101 and wants to get started.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - company.create\ndepends_on:\n - write-preflight\nrequired_tools:\n - whoami\n - create_company\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# Company Creation\n\nCreate one company through `create_company`: the current user becomes the owner. No company selection is required beforehand.\n\n1. For an explicit request to create a company, obtain `title`. If the name is missing, ask for it; do not invent it from personal data.\n2. If there are no companies yet and no choice has been made, offer to create their own company or wait for an invitation. If creation has already been chosen, ask only for the missing name. The offer itself does not authorize a write.\n3. Pass `code` only if the user provided the code. Requisites and other optional fields must come only from supplied data.\n4. Apply `write-preflight`, excluding the requirement for an existing company, and the standard confirmation policy. An explicit request with a name does not require additional approval of your own.\n5. After success, use the response as confirmation. If the response is lost, first check `whoami`; a match by name alone does not prove creation and does not authorize a retry.\n\nErrors: `9010` — a company has already been created without a code; offer the existing one or creation with a code; `9001` — the code was not found; `9002` — it has been used. For a field error, request a correction.\n\nReturn the name, confirmed ownership, and material limitations. If creation was a step toward a previously stated goal, refresh `whoami` and continue that goal without requiring a repeated instruction or collecting known data again. Do not add actions outside the original goal.\n"
AFTER
"---\nname: company-creation\ndescription: Use when a person asks to create a new company in 101 or does not yet have a company in 101 and wants to get started.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - company.create\ndepends_on:\n - write-preflight\nrequired_tools:\n - whoami\n - create_company\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# Company Creation\n\nCreate one company through `create_company`: the current user becomes the owner. No company selection is required beforehand.\n\n1. For an explicit request to create a company, obtain `title`. If the name is missing, ask for it; do not invent it from personal data.\n2. If there are no companies yet and no choice has been made, offer to create their own company as the next step toward the original goal; offer waiting for an invitation if the user has indicated that this is their intended path. If creation has already been chosen, ask only for the missing name. The offer itself does not authorize a write.\n3. Pass `code` only if the user provided the code. Requisites and other optional fields must come only from supplied data.\n4. Apply `write-preflight`, excluding the requirement for an existing company, and the standard confirmation policy. An explicit request with a name does not require additional approval of your own.\n5. After success, use the response as confirmation. If the response is lost, first check `whoami`; a match by name alone does not prove creation and does not authorize a retry.\n\nErrors: `9010` — a company has already been created without a code; offer the existing one or creation with a code; `9001` — the code was not found; `9002` — it has been used. For a field error, request a correction.\n\nReturn the name, confirmed ownership, and material limitations. If creation was a step toward a previously stated goal, refresh `whoami` and continue that goal without requiring a repeated instruction or collecting known data again. Do not add actions outside the original goal.\n"
Full snapshot data
{
"description": "Use when a person asks to create a new company in 101 or does not yet have a company in 101 and wants to get started.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 43
}
],
"name": "company-creation",
"skill_md_contents": "---\nname: company-creation\ndescription: Use when a person asks to create a new company in 101 or does not yet have a company in 101 and wants to get started.\nversion: \"1.0.0\"\nrole: primary\ninvocation: internal\nintents:\n - company.create\ndepends_on:\n - write-preflight\nrequired_tools:\n - whoami\n - create_company\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# Company Creation\n\nCreate one company through `create_company`: the current user becomes the owner. No company selection is required beforehand.\n\n1. For an explicit request to create a company, obtain `title`. If the name is missing, ask for it; do not invent it from personal data.\n2. If there are no companies yet and no choice has been made, offer to create their own company as the next step toward the original goal; offer waiting for an invitation if the user has indicated that this is their intended path. If creation has already been chosen, ask only for the missing name. The offer itself does not authorize a write.\n3. Pass `code` only if the user provided the code. Requisites and other optional fields must come only from supplied data.\n4. Apply `write-preflight`, excluding the requirement for an existing company, and the standard confirmation policy. An explicit request with a name does not require additional approval of your own.\n5. After success, use the response as confirmation. If the response is lost, first check `whoami`; a match by name alone does not prove creation and does not authorize a retry.\n\nErrors: `9010` — a company has already been created without a code; offer the existing one or creation with a code; `9001` — the code was not found; `9002` — it has been used. For a field error, request a correction.\n\nReturn the name, confirmed ownership, and material limitations. If creation was a step toward a previously stated goal, refresh `whoami` and continue that goal without requiring a repeated instruction or collecting known data again. Do not add actions outside the original goal.\n"
}SHA-256 of public snapshot: f503faf009cc4f3f5343cfe502c04888a05f818f175fb3a6adb03ebcc1e8d366