[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW89NFDET69RG1JK4CNHXY":3,"skill-same:01M6JW89NFDET69RG1JK4CNHXY":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JW89NFDET69RG1JK4CNHXY","forgiveness-confirmation-and-prevention",null,"Use this skill when the user must commit to an irreversible or high-stakes action and reversibility isn't enough — confirmation dialogs, type-to-confirm patterns, password re-entry, two-step authentication for destructive actions, and structural prevention that makes the wrong action impossible. Trigger when designing destructive flows for genuinely-irreversible commitments, when reviewing confirmation fatigue, or when picking between a single confirm dialog and a multi-step verification. Sub-aspect of `forgiveness`; read that first.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Fforgiveness-confirmation-and-prevention\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"forgiveness","forgiveness confirmation and prevention","prevention","confirmation","trigger","when","reversibility","for","action","commitments","re","flows","fatigue","commit","structural","patterns","use","read","dialog","actions","verification","authentication","2026-11-10 10:12:30",false,"---\nname: forgiveness-confirmation-and-prevention\ndescription: 'Use this skill when the user must commit to an irreversible or high-stakes action and reversibility isn''t enough — confirmation dialogs, type-to-confirm patterns, password re-entry, two-step authentication for destructive actions, and structural prevention that makes the wrong action impossible. Trigger when designing destructive flows for genuinely-irreversible commitments, when reviewing confirmation fatigue, or when picking between a single confirm dialog and a multi-step verification. Sub-aspect of `forgiveness`; read that first.'\n---\n\n# Forgiveness through confirmation and prevention\n\nWhen an action can't be made reversible, the next-best forgiveness is requiring deliberate intent. The user must take an explicit, considered step before the irreversible thing happens. The challenge: confirmation overuse trains users to dismiss it on autopilot, defeating the purpose. Confirmation must be reserved for the moments when it earns its friction.\n\n## When confirmation is appropriate\n\nA useful test before adding confirmation: is the action irreversible *and* high-stakes?\n\n- **Irreversible + high-stakes** → confirm. (Account deletion, ownership transfer, large financial transaction.)\n- **Reversible + high-stakes** → use undo \u002F soft-delete instead. Confirmation here is fatigue-inducing.\n- **Irreversible + low-stakes** → consider whether it should be reversible. If it must be irreversible, a light confirmation may suffice.\n- **Reversible + low-stakes** → no confirmation. Just do it; let undo catch mistakes.\n\n## Confirmation strength\n\nMatch confirmation friction to action severity:\n\n### Light confirmation: \"Yes \u002F No\" dialog\n\n```\nCancel reservation?\n[ Cancel ]   [ Cancel reservation ]\n```\n\nFor actions the user clearly initiated, where the dialog mostly catches accidental clicks. The user reads the title, picks an option.\n\n### Medium confirmation: dialog with summary\n\n```\nDelete project \"Acme Q4\"?\n\nThis deletes 24 tasks and 8 attached files.\n\n[ Cancel ]   [ Delete project ]\n```\n\nFor actions where the user benefits from seeing what they're about to lose. The summary gives them a chance to step back.\n\n### Strong confirmation: type-to-confirm\n\n```\nDelete project \"Acme Q4\"?\n\nThis deletes 24 tasks and 8 attached files. Cannot be undone.\n\nTo confirm, type the project name below:\n[ Acme Q4__________ ]\n\n[ Cancel ]   [ Delete project ]   (button enabled only when name matches)\n```\n\nFor irreversible high-stakes actions. The user must actively type the resource name, breaking autopilot. The button stays disabled until the confirmation matches.\n\n### Strongest: re-authentication\n\n```\nThis action requires re-authentication.\nEnter your password to continue.\n\n[ Password__________ ]\n\n[ Cancel ]   [ Continue ]\n```\n\nFor account-affecting actions: deleting account, changing email, transferring ownership, viewing audit logs. Re-authentication catches both autopilot mistakes and someone-else-using-my-session attacks.\n\n## Type-to-confirm: the canonical pattern for irreversible action\n\n```html\n\u003Cdialog id=\"delete-dialog\">\n  \u003Ch2>Delete workspace \"Acme Inc\"?\u003C\u002Fh2>\n  \u003Cp>\n    This permanently deletes the workspace, all 47 projects, all 12 members'\n    access, and 3.2 GB of files. This cannot be undone.\n  \u003C\u002Fp>\n  \u003Cp>To confirm, type the workspace name below:\u003C\u002Fp>\n  \u003Cinput id=\"confirm\" placeholder=\"Acme Inc\" autocomplete=\"off\" \u002F>\n  \u003Cdiv class=\"actions\">\n    \u003Cbutton onclick=\"closeDialog()\">Cancel\u003C\u002Fbutton>\n    \u003Cbutton id=\"confirm-btn\" disabled class=\"destructive\">\n      Delete workspace permanently\n    \u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\u003C\u002Fdialog>\n\n\u003Cscript>\nconst input = document.getElementById('confirm');\nconst btn = document.getElementById('confirm-btn');\ninput.addEventListener('input', () => {\n  btn.disabled = input.value !== workspace.name;\n});\n\u003C\u002Fscript>\n```\n\nWhat this achieves:\n\n- The dialog must be opened deliberately.\n- The consequences are stated plainly.\n- The user must type — an active gesture that breaks autopilot.\n- The button is disabled until the typed name matches, so even autopilot Enter doesn't trigger.\n\nFor actions that should genuinely never happen by accident, this stack is appropriate.\n\n## Re-authentication for security-sensitive operations\n\n```html\n\u003Cbutton onclick=\"requireReauthThen('delete-account')\">\n  Delete account\n\u003C\u002Fbutton>\n\n\u003Cdialog id=\"reauth-dialog\">\n  \u003Ch2>Confirm your identity\u003C\u002Fh2>\n  \u003Cp>For your security, please re-enter your password to continue.\u003C\u002Fp>\n  \u003Cinput type=\"password\" id=\"reauth-password\" autofocus \u002F>\n  \u003Cdiv class=\"actions\">\n    \u003Cbutton onclick=\"closeDialog()\">Cancel\u003C\u002Fbutton>\n    \u003Cbutton id=\"reauth-submit\">Continue\u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\u003C\u002Fdialog>\n```\n\nUse re-authentication when:\n\n- The action affects security or billing.\n- The action affects other users' access.\n- The action would be devastating if performed by someone with stolen session access.\n- Compliance requires it.\n\nThe cost: an extra password entry. The benefit: a second opportunity for the user to reconsider, plus protection against session theft.\n\n## Structural prevention (the highest forgiveness)\n\nStronger than any confirmation: making the wrong action impossible.\n\n### Disable the action when invalid\n\nA \"Submit\" button disabled when the form has errors. The user can't trigger the failure path. (Pair with inline error explanations so the user knows what's missing — see `affordance-false-and-anti`.)\n\n### Type-restricted inputs\n\n`\u003Cinput type=\"email\">` rejects non-email format. `\u003Cinput type=\"number\">` rejects non-numeric. `\u003Cinput type=\"tel\">` shows a numeric keyboard on mobile. Each is structural prevention of certain input errors.\n\n### Constraint by selection rather than typing\n\nA `\u003Cselect>` for state names prevents typos that a free-text field would allow. A date picker prevents impossible dates. A typeahead constrained to known values prevents misspelled selections.\n\n### Physical \u002F hardware analogies\n\nThe USB-C connector that can't be inserted upside-down. The pill organizer that shows visual state. The medical injector that can't deliver a dangerous dose.\n\n### Required-field marking + blocked submit\n\n```html\n\u003Cform>\n  \u003Clabel>Email \u003Cspan class=\"required\">*\u003C\u002Fspan>\n    \u003Cinput type=\"email\" required \u002F>\n  \u003C\u002Flabel>\n  \u003Cbutton>Submit\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nThe browser blocks submission with focus on the missing field. Native scaffolding for prevention.\n\n## Anti-patterns\n\n- **Confirmation fatigue.** \"Are you sure you want to save? \u002F open? \u002F apply?\" Every routine action confirmed. Users dismiss everything on autopilot.\n- **Pre-selected destructive option.** A confirm dialog with the destructive button as default Enter target. Users who hit Enter without reading commit the destruction.\n- **Trivial type-to-confirm.** Forcing users to type \"DELETE\" for a routine archive operation. Heavy friction for low-stakes action.\n- **Hidden cancellation path.** A confirm dialog with no Esc, no backdrop dismiss, just two buttons. The user feels trapped.\n- **Confirmation as the *only* forgiveness.** Apps where every destructive action is confirmed but nothing is reversible. Confirmation alone is insufficient — users still make mistakes.\n- **Sneaky double-negatives.** \"Are you sure you don't want to keep your account?\" Users misread; mistakes happen.\n\n## Calibrating friction to stakes\n\nA useful framing: every confirmation step is a tax. Ask whether the tax is worth it for *this specific action*.\n\n| Action | Reversibility | Stakes | Recommended confirmation |\n|---|---|---|---|\n| Save | Reversible | Low | None |\n| Apply filter | Reversible | Low | None |\n| Archive item | Reversible (toast undo) | Low | None |\n| Delete (soft) | Recoverable in trash | Medium | None |\n| Empty trash | Irreversible | Medium | Light dialog |\n| Delete project | Irreversible | High | Strong dialog with summary |\n| Delete account | Irreversible | Very high | Type-to-confirm + reauth |\n| Transfer ownership | Irreversible | Very high | Type-to-confirm + reauth + email verification |\n\nEach step up the friction ladder should correspond to a step up in stakes.\n\n## Heuristics\n\n1. **The reversibility-first check.** Before adding any confirmation, ask: can this be made reversible instead? If yes, do that.\n2. **The autopilot test.** If a typical user would dismiss the confirmation without reading, the confirmation isn't doing its job. Either remove it or make it harder to dismiss without reading.\n3. **The \"what would they regret?\" test.** For irreversible actions, imagine the user a week later realizing they made a mistake. Did the confirmation do enough to prevent that?\n4. **The disabled-button question.** When you reach for confirmation, ask whether structural prevention (disabling the action when it shouldn't apply) would work better.\n\n## Related sub-skills\n\n- **`forgiveness`** (parent).\n- **`forgiveness-undo-and-soft-delete`** — the preferred alternative when reversibility is possible.\n- **`affordance-false-and-anti`** — disabled states and structural prevention.\n- **`constraint`** — input constraints prevent invalid actions.\n- **`expectation-effect`** — confirmation buttons in unexpected positions surprise users.\n- **`accessibility-understandable`** (process) — confirmation flows must be operable for all users.\n","# Forgiveness through confirmation and prevention\n\nWhen an action can't be made reversible, the next-best forgiveness is requiring deliberate intent. The user must take an explicit, considered step before the irreversible thing happens. The challenge: confirmation overuse trains users to dismiss it on autopilot, defeating the purpose. Confirmation must be reserved for the moments when it earns its friction.\n\n## When confirmation is appropriate\n\nA useful test before adding confirmation: is the action irreversible *and* high-stakes?\n\n- **Irreversible + high-stakes** → confirm. (Account deletion, ownership transfer, large financial transaction.)\n- **Reversible + high-stakes** → use undo \u002F soft-delete instead. Confirmation here is fatigue-inducing.\n- **Irreversible + low-stakes** → consider whether it should be reversible. If it must be irreversible, a light confirmation may suffice.\n- **Reversible + low-stakes** → no confirmation. Just do it; let undo catch mistakes.\n\n## Confirmation strength\n\nMatch confirmation friction to action severity:\n\n### Light confirmation: \"Yes \u002F No\" dialog\n\n```\nCancel reservation?\n[ Cancel ]   [ Cancel reservation ]\n```\n\nFor actions the user clearly initiated, where the dialog mostly catches accidental clicks. The user reads the title, picks an option.\n\n### Medium confirmation: dialog with summary\n\n```\nDelete project \"Acme Q4\"?\n\nThis deletes 24 tasks and 8 attached files.\n\n[ Cancel ]   [ Delete project ]\n```\n\nFor actions where the user benefits from seeing what they're about to lose. The summary gives them a chance to step back.\n\n### Strong confirmation: type-to-confirm\n\n```\nDelete project \"Acme Q4\"?\n\nThis deletes 24 tasks and 8 attached files. Cannot be undone.\n\nTo confirm, type the project name below:\n[ Acme Q4__________ ]\n\n[ Cancel ]   [ Delete project ]   (button enabled only when name matches)\n```\n\nFor irreversible high-stakes actions. The user must actively type the resource name, breaking autopilot. The button stays disabled until the confirmation matches.\n\n### Strongest: re-authentication\n\n```\nThis action requires re-authentication.\nEnter your password to continue.\n\n[ Password__________ ]\n\n[ Cancel ]   [ Continue ]\n```\n\nFor account-affecting actions: deleting account, changing email, transferring ownership, viewing audit logs. Re-authentication catches both autopilot mistakes and someone-else-using-my-session attacks.\n\n## Type-to-confirm: the canonical pattern for irreversible action\n\n```html\n\u003Cdialog id=\"delete-dialog\">\n  \u003Ch2>Delete workspace \"Acme Inc\"?\u003C\u002Fh2>\n  \u003Cp>\n    This permanently deletes the workspace, all 47 projects, all 12 members'\n    access, and 3.2 GB of files. This cannot be undone.\n  \u003C\u002Fp>\n  \u003Cp>To confirm, type the workspace name below:\u003C\u002Fp>\n  \u003Cinput id=\"confirm\" placeholder=\"Acme Inc\" autocomplete=\"off\" \u002F>\n  \u003Cdiv class=\"actions\">\n    \u003Cbutton onclick=\"closeDialog()\">Cancel\u003C\u002Fbutton>\n    \u003Cbutton id=\"confirm-btn\" disabled class=\"destructive\">\n      Delete workspace permanently\n    \u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\u003C\u002Fdialog>\n\n\u003Cscript>\nconst input = document.getElementById('confirm');\nconst btn = document.getElementById('confirm-btn');\ninput.addEventListener('input', () => {\n  btn.disabled = input.value !== workspace.name;\n});\n\u003C\u002Fscript>\n```\n\nWhat this achieves:\n\n- The dialog must be opened deliberately.\n- The consequences are stated plainly.\n- The user must type — an active gesture that breaks autopilot.\n- The button is disabled until the typed name matches, so even autopilot Enter doesn't trigger.\n\nFor actions that should genuinely never happen by accident, this stack is appropriate.\n\n## Re-authentication for security-sensitive operations\n\n```html\n\u003Cbutton onclick=\"requireReauthThen('delete-account')\">\n  Delete account\n\u003C\u002Fbutton>\n\n\u003Cdialog id=\"reauth-dialog\">\n  \u003Ch2>Confirm your identity\u003C\u002Fh2>\n  \u003Cp>For your security, please re-enter your password to continue.\u003C\u002Fp>\n  \u003Cinput type=\"password\" id=\"reauth-password\" autofocus \u002F>\n  \u003Cdiv class=\"actions\">\n    \u003Cbutton onclick=\"closeDialog()\">Cancel\u003C\u002Fbutton>\n    \u003Cbutton id=\"reauth-submit\">Continue\u003C\u002Fbutton>\n  \u003C\u002Fdiv>\n\u003C\u002Fdialog>\n```\n\nUse re-authentication when:\n\n- The action affects security or billing.\n- The action affects other users' access.\n- The action would be devastating if performed by someone with stolen session access.\n- Compliance requires it.\n\nThe cost: an extra password entry. The benefit: a second opportunity for the user to reconsider, plus protection against session theft.\n\n## Structural prevention (the highest forgiveness)\n\nStronger than any confirmation: making the wrong action impossible.\n\n### Disable the action when invalid\n\nA \"Submit\" button disabled when the form has errors. The user can't trigger the failure path. (Pair with inline error explanations so the user knows what's missing — see `affordance-false-and-anti`.)\n\n### Type-restricted inputs\n\n`\u003Cinput type=\"email\">` rejects non-email format. `\u003Cinput type=\"number\">` rejects non-numeric. `\u003Cinput type=\"tel\">` shows a numeric keyboard on mobile. Each is structural prevention of certain input errors.\n\n### Constraint by selection rather than typing\n\nA `\u003Cselect>` for state names prevents typos that a free-text field would allow. A date picker prevents impossible dates. A typeahead constrained to known values prevents misspelled selections.\n\n### Physical \u002F hardware analogies\n\nThe USB-C connector that can't be inserted upside-down. The pill organizer that shows visual state. The medical injector that can't deliver a dangerous dose.\n\n### Required-field marking + blocked submit\n\n```html\n\u003Cform>\n  \u003Clabel>Email \u003Cspan class=\"required\">*\u003C\u002Fspan>\n    \u003Cinput type=\"email\" required \u002F>\n  \u003C\u002Flabel>\n  \u003Cbutton>Submit\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nThe browser blocks submission with focus on the missing field. Native scaffolding for prevention.\n\n## Anti-patterns\n\n- **Confirmation fatigue.** \"Are you sure you want to save? \u002F open? \u002F apply?\" Every routine action confirmed. Users dismiss everything on autopilot.\n- **Pre-selected destructive option.** A confirm dialog with the destructive button as default Enter target. Users who hit Enter without reading commit the destruction.\n- **Trivial type-to-confirm.** Forcing users to type \"DELETE\" for a routine archive operation. Heavy friction for low-stakes action.\n- **Hidden cancellation path.** A confirm dialog with no Esc, no backdrop dismiss, just two buttons. The user feels trapped.\n- **Confirmation as the *only* forgiveness.** Apps where every destructive action is confirmed but nothing is reversible. Confirmation alone is insufficient — users still make mistakes.\n- **Sneaky double-negatives.** \"Are you sure you don't want to keep your account?\" Users misread; mistakes happen.\n\n## Calibrating friction to stakes\n\nA useful framing: every confirmation step is a tax. Ask whether the tax is worth it for *this specific action*.\n\n| Action | Reversibility | Stakes | Recommended confirmation |\n|---|---|---|---|\n| Save | Reversible | Low | None |\n| Apply filter | Reversible | Low | None |\n| Archive item | Reversible (toast undo) | Low | None |\n| Delete (soft) | Recoverable in trash | Medium | None |\n| Empty trash | Irreversible | Medium | Light dialog |\n| Delete project | Irreversible | High | Strong dialog with summary |\n| Delete account | Irreversible | Very high | Type-to-confirm + reauth |\n| Transfer ownership | Irreversible | Very high | Type-to-confirm + reauth + email verification |\n\nEach step up the friction ladder should correspond to a step up in stakes.\n\n## Heuristics\n\n1. **The reversibility-first check.** Before adding any confirmation, ask: can this be made reversible instead? If yes, do that.\n2. **The autopilot test.** If a typical user would dismiss the confirmation without reading, the confirmation isn't doing its job. Either remove it or make it harder to dismiss without reading.\n3. **The \"what would they regret?\" test.** For irreversible actions, imagine the user a week later realizing they made a mistake. Did the confirmation do enough to prevent that?\n4. **The disabled-button question.** When you reach for confirmation, ask whether structural prevention (disabling the action when it shouldn't apply) would work better.\n\n## Related sub-skills\n\n- **`forgiveness`** (parent).\n- **`forgiveness-undo-and-soft-delete`** — the preferred alternative when reversibility is possible.\n- **`affordance-false-and-anti`** — disabled states and structural prevention.\n- **`constraint`** — input constraints prevent invalid actions.\n- **`expectation-effect`** — confirmation buttons in unexpected positions surprise users.\n- **`accessibility-understandable`** (process) — confirmation flows must be operable for all users.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Fforgiveness-confirmation-and-prevention",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill forgiveness-confirmation-and-prevention",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill forgiveness-confirmation-and-prevention",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill forgiveness-confirmation-and-prevention","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Fforgiveness-confirmation-and-prevention\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fconfirmation-design-research.md","REFERENCE","参考文档",4377,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Fforgiveness-confirmation-and-prevention\u002Freferences\u002Fconfirmation-design-research.md",[77,87,95,103,111,119],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":86},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":86},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":86},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":86},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":86},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]