[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJ448X7TRSW7YB3235TRXX":3,"skill-same:01M6MJ448X7TRSW7YB3235TRXX":72},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6MJ448X7TRSW7YB3235TRXX","stop-that-shit",null,"Complete requested work while preventing speculative defenses and scope creep. Use when considering extra hardening, reviewing possible overengineering, resolving repeated verification loops, following explicit task boundaries, or when the user invokes Stop That Shit. Ordinary use of validation, retries, or dependencies alone is not a trigger.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstop-that-shit\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"stop that shit","stop","dependencies","when","scope creep","loops","retries","complete","scope","trigger","validation","task","use","user","extra","work","hardening","verification","2026-11-10 10:12:30",false,"---\nname: stop-that-shit\ndescription: Complete requested work while preventing speculative defenses and scope creep. Use when considering extra hardening, reviewing possible overengineering, resolving repeated verification loops, following explicit task boundaries, or when the user invokes Stop That Shit. Ordinary use of validation, retries, or dependencies alone is not a trigger.\nlicense: MIT\n---\n\n# Stop That Shit\n\nMeet the task's responsibilities in full. Let real needs drive complexity.\n\nThis Skill is advisory and works without the Guard hooks. It cannot guarantee\nmodel behavior. When the Guard is installed, the same directives also provide\nmachine-enforced boundaries on supported host action paths.\n\n## Follow the Stop Ladder\n\nApply this ladder when choosing an implementation, adding a mechanism, or\nextending verification. These are engineering decisions within normal work;\nthey do not require a new checklist, proof file, or reviewing agent.\n\n1. **Understand the current responsibility.** Establish the requested result,\n   explicit boundaries, and existing guarantees the change must preserve. Use\n   the request, later corrections, project requirements, and relevant code.\n   Trace affected callers and failure paths before choosing a fix. Complete\n   necessary caller, data, test, and documentation changes within that authority.\n   A plan or an easier subset does not fulfill the requested result.\n2. **Start with a direct solution.** Check suitable code already in the project,\n   standard-library or platform features, and installed dependencies. Compare\n   actual behavior, failure handling, and state lifetime. Proceed when a clear,\n   maintainable option satisfies the responsibility; do not exhaust the ecosystem.\n3. **Expand to close a concrete gap.** Identify the supported input, consumer,\n   failure, or obligation the direct solution does not cover. Adapt or implement\n   that missing behavior at the responsible layer. Existing support commitments\n   count as current needs; hypothetical future flexibility alone does not.\n   A larger diff is justified when it completes the affected flow.\n4. **Judge defenses by their effect.** Identify what a mechanism detects and\n   what its rejection, recovery, or diagnosis changes. Keep effective protection.\n   Omit optional additions without a grounded purpose or additional value.\n   Within the task scope, remove or narrow work shown to be redundant, unused,\n   or too broad. Repair defenses that hide failures, duplicate side effects, or\n   prevent legitimate work, even when the repair adds code.\n5. **Verify the result and finish.** Use the project's intended checks for the\n   affected behavior and guarantees. Honor explicit acceptance criteria and\n   mandatory checks. Reuse evidence while it remains valid for the final state.\n   Finish when the requested result exists, the required evidence supports it,\n   and no known in-scope blocker remains.\n\n## Resolve uncertainty without inventing work\n\nA supported trust boundary, failure mode, existing data, or applicable obligation\ncan establish a need before an incident occurs. Preserve necessary validation,\nauthentication, authorization, data integrity, recovery, compatibility,\nmigration, and accessibility. Mechanism names and line counts do not determine\nwhether protection is useful.\n\nNew optional work without a purpose can wait. An existing protection whose role\nis unclear needs inspection of the relevant path before removal. Missing\nevidence is not proof that it is unnecessary. Adding a verifier solely to read a\nnew optional manifest does not establish their value; trace the chain back to a\ntask requirement or an existing guarantee.\n\nFor example, a release consumer can make a checksum necessary. A TTL requirement\ncan require more than an available cache provides. A catch that turns a failed\nread into a successful empty result can require repair. Choose from the actual\ncontract and behavior in each case.\n\nResolve ordinary choices from available context. Ask only for missing information\nthat cannot be resolved from context and would materially change the result,\nauthorization, or a choice that is hard to reverse. Do not request authorization\nalready given.\n\nWait for an operation before retrying it or starting work that depends on it.\nIf a necessary check is blocked, repair the specific cause when feasible within\nthe task and continue independent necessary work. Change methods when they can\nresolve the gap; an unrelated successful command cannot replace the missing\nevidence. Report an unresolved blocker accurately without claiming completion.\n\n## Keep the deliverable focused\n\nReport the result and relevant verification. Include a tradeoff, warning, or\nlimitation when requested or when it changes how the reader should interpret or\nuse the result. Put required disclosure at the decision point. Keep internal\nprocess notes and unrequested cautionary prose out of the product; narrow or\nattribute uncertain claims instead of surrounding them with disclaimers.\n\n## Respect the task mode\n\n- `review`, `answer`, and `monitor` are read-only unless the user authorizes a\n  change.\n- `change` permits only requested work and necessary consequences.\n- Necessary work does not override an explicit file lock or a narrower action\n  boundary. Explain a required boundary change before acting outside it.\n\nWith Skill only, treat the mode as an instruction. With the Guard installed,\nuse the host-native invocation form.\n\nClaude Code plugin:\n\n```text\n\u002Fstop-that-shit:stop-that-shit change -- Fix the failing config test.\n\u002Fstop-that-shit:stop-that-shit review -- Review this diff. Report findings; do not edit.\n```\n\nCodex plugin or host-neutral directive at the start of a prompt:\n\n```text\n$stop-that-shit change -- Fix the failing config test.\n$stop-that-shit review -- Review this diff. Report findings; do not edit.\n```\n\nSubmit one directive on the first non-empty line, outside quotes and code\nblocks. Put task text after `--`, `: `, or a newline. Embedded examples do not\nset directive fields. Unknown fields or conflicting values leave the previous\ncontract unchanged and require a corrected directive.\n\nAn installed Guard begins in observation-only `unconfirmed` mode. Do not claim\nthat an action was blocked unless an explicit mode armed the Guard and the Guard\nreturned a host-specific denial. Even then, describe the host effect as\nunobserved.\n\nWith Codex `change deps=ask`, a supported direct dependency command can produce\none native approval question tied to that exact command and its proposed target\ndirectory. Choose the explicit allow or deny option in the question. Closing it,\nleaving it unanswered, or replying with ordinary text does not grant\npermission. An allow permits one matching retry within ten minutes; the session\npolicy remains `deps=ask`. In a delegated Codex agent, the proposal, answer and\none-time runner ticket stay in that agent's child state. The child is evaluated\nagainst the latest parent and child contract, and a parent approval cannot be\nreused by a child. If the host does not provide its child-state API, scoped\napproval questions and child contract changes are refused; ordinary child\nclarification and non-approval tools keep their normal path.\n\nThe following inspection commands do not change the current task contract. In\nClaude Code, pass the text after the namespaced slash command; in Codex, use the\n`$stop-that-shit` form shown below.\n\n```text\n$stop-that-shit status\n$stop-that-shit runtime\n$stop-that-shit explain evt_...\n$stop-that-shit label evt_... correct|incorrect|inconclusive\n```\n\nUse a hard file lock only when the complete boundary is already known:\n\n```text\n$stop-that-shit lock change files=src\u002Fconfig.cjs|test\u002Fconfig.test.cjs -- Fix this behavior.\n```\n\nThe active delegation limit is a session control:\n\n```text\n$stop-that-shit change agents=N -- Run the task.\n```\n\n`agents=N` limits reserved concurrent capacity. It defaults to unlimited, and\n`0` forbids new delegation. A batch that exceeds the limit is rejected\natomically. Request parameters do not prove completion: the host must confirm\nthat a call did not execute, joined all its children, or ended an associated\nrun. Unknown results keep their existing capacity; session-end alone does not\nprove completion. Permitted unbounded or unversioned resume calls remain\nunresolved until matching terminal evidence arrives. With unresolved activity,\nfinite Guard requires that evidence or a new host session. Migration preserves\nvalid budgets including `0`. Lifecycle association uses explicit host identities,\nnever event arrival order.\n\nClaude Code equivalent:\n\n```text\n\u002Fstop-that-shit:stop-that-shit lock change files=src\u002Fconfig.cjs|test\u002Fconfig.test.cjs -- Fix this behavior.\n```\n\nDo not invent a file list to appear precise. Inspect proportionately and explain\nmaterial expansion before acting.\n\n## Finish\n\nReport the requested result, necessary consequences, and the evidence that makes\nthe task complete. Do not add a final audit loop only to satisfy this Skill.\n","# Stop That Shit\n\nMeet the task's responsibilities in full. Let real needs drive complexity.\n\nThis Skill is advisory and works without the Guard hooks. It cannot guarantee\nmodel behavior. When the Guard is installed, the same directives also provide\nmachine-enforced boundaries on supported host action paths.\n\n## Follow the Stop Ladder\n\nApply this ladder when choosing an implementation, adding a mechanism, or\nextending verification. These are engineering decisions within normal work;\nthey do not require a new checklist, proof file, or reviewing agent.\n\n1. **Understand the current responsibility.** Establish the requested result,\n   explicit boundaries, and existing guarantees the change must preserve. Use\n   the request, later corrections, project requirements, and relevant code.\n   Trace affected callers and failure paths before choosing a fix. Complete\n   necessary caller, data, test, and documentation changes within that authority.\n   A plan or an easier subset does not fulfill the requested result.\n2. **Start with a direct solution.** Check suitable code already in the project,\n   standard-library or platform features, and installed dependencies. Compare\n   actual behavior, failure handling, and state lifetime. Proceed when a clear,\n   maintainable option satisfies the responsibility; do not exhaust the ecosystem.\n3. **Expand to close a concrete gap.** Identify the supported input, consumer,\n   failure, or obligation the direct solution does not cover. Adapt or implement\n   that missing behavior at the responsible layer. Existing support commitments\n   count as current needs; hypothetical future flexibility alone does not.\n   A larger diff is justified when it completes the affected flow.\n4. **Judge defenses by their effect.** Identify what a mechanism detects and\n   what its rejection, recovery, or diagnosis changes. Keep effective protection.\n   Omit optional additions without a grounded purpose or additional value.\n   Within the task scope, remove or narrow work shown to be redundant, unused,\n   or too broad. Repair defenses that hide failures, duplicate side effects, or\n   prevent legitimate work, even when the repair adds code.\n5. **Verify the result and finish.** Use the project's intended checks for the\n   affected behavior and guarantees. Honor explicit acceptance criteria and\n   mandatory checks. Reuse evidence while it remains valid for the final state.\n   Finish when the requested result exists, the required evidence supports it,\n   and no known in-scope blocker remains.\n\n## Resolve uncertainty without inventing work\n\nA supported trust boundary, failure mode, existing data, or applicable obligation\ncan establish a need before an incident occurs. Preserve necessary validation,\nauthentication, authorization, data integrity, recovery, compatibility,\nmigration, and accessibility. Mechanism names and line counts do not determine\nwhether protection is useful.\n\nNew optional work without a purpose can wait. An existing protection whose role\nis unclear needs inspection of the relevant path before removal. Missing\nevidence is not proof that it is unnecessary. Adding a verifier solely to read a\nnew optional manifest does not establish their value; trace the chain back to a\ntask requirement or an existing guarantee.\n\nFor example, a release consumer can make a checksum necessary. A TTL requirement\ncan require more than an available cache provides. A catch that turns a failed\nread into a successful empty result can require repair. Choose from the actual\ncontract and behavior in each case.\n\nResolve ordinary choices from available context. Ask only for missing information\nthat cannot be resolved from context and would materially change the result,\nauthorization, or a choice that is hard to reverse. Do not request authorization\nalready given.\n\nWait for an operation before retrying it or starting work that depends on it.\nIf a necessary check is blocked, repair the specific cause when feasible within\nthe task and continue independent necessary work. Change methods when they can\nresolve the gap; an unrelated successful command cannot replace the missing\nevidence. Report an unresolved blocker accurately without claiming completion.\n\n## Keep the deliverable focused\n\nReport the result and relevant verification. Include a tradeoff, warning, or\nlimitation when requested or when it changes how the reader should interpret or\nuse the result. Put required disclosure at the decision point. Keep internal\nprocess notes and unrequested cautionary prose out of the product; narrow or\nattribute uncertain claims instead of surrounding them with disclaimers.\n\n## Respect the task mode\n\n- `review`, `answer`, and `monitor` are read-only unless the user authorizes a\n  change.\n- `change` permits only requested work and necessary consequences.\n- Necessary work does not override an explicit file lock or a narrower action\n  boundary. Explain a required boundary change before acting outside it.\n\nWith Skill only, treat the mode as an instruction. With the Guard installed,\nuse the host-native invocation form.\n\nClaude Code plugin:\n\n```text\n\u002Fstop-that-shit:stop-that-shit change -- Fix the failing config test.\n\u002Fstop-that-shit:stop-that-shit review -- Review this diff. Report findings; do not edit.\n```\n\nCodex plugin or host-neutral directive at the start of a prompt:\n\n```text\n$stop-that-shit change -- Fix the failing config test.\n$stop-that-shit review -- Review this diff. Report findings; do not edit.\n```\n\nSubmit one directive on the first non-empty line, outside quotes and code\nblocks. Put task text after `--`, `: `, or a newline. Embedded examples do not\nset directive fields. Unknown fields or conflicting values leave the previous\ncontract unchanged and require a corrected directive.\n\nAn installed Guard begins in observation-only `unconfirmed` mode. Do not claim\nthat an action was blocked unless an explicit mode armed the Guard and the Guard\nreturned a host-specific denial. Even then, describe the host effect as\nunobserved.\n\nWith Codex `change deps=ask`, a supported direct dependency command can produce\none native approval question tied to that exact command and its proposed target\ndirectory. Choose the explicit allow or deny option in the question. Closing it,\nleaving it unanswered, or replying with ordinary text does not grant\npermission. An allow permits one matching retry within ten minutes; the session\npolicy remains `deps=ask`. In a delegated Codex agent, the proposal, answer and\none-time runner ticket stay in that agent's child state. The child is evaluated\nagainst the latest parent and child contract, and a parent approval cannot be\nreused by a child. If the host does not provide its child-state API, scoped\napproval questions and child contract changes are refused; ordinary child\nclarification and non-approval tools keep their normal path.\n\nThe following inspection commands do not change the current task contract. In\nClaude Code, pass the text after the namespaced slash command; in Codex, use the\n`$stop-that-shit` form shown below.\n\n```text\n$stop-that-shit status\n$stop-that-shit runtime\n$stop-that-shit explain evt_...\n$stop-that-shit label evt_... correct|incorrect|inconclusive\n```\n\nUse a hard file lock only when the complete boundary is already known:\n\n```text\n$stop-that-shit lock change files=src\u002Fconfig.cjs|test\u002Fconfig.test.cjs -- Fix this behavior.\n```\n\nThe active delegation limit is a session control:\n\n```text\n$stop-that-shit change agents=N -- Run the task.\n```\n\n`agents=N` limits reserved concurrent capacity. It defaults to unlimited, and\n`0` forbids new delegation. A batch that exceeds the limit is rejected\natomically. Request parameters do not prove completion: the host must confirm\nthat a call did not execute, joined all its children, or ended an associated\nrun. Unknown results keep their existing capacity; session-end alone does not\nprove completion. Permitted unbounded or unversioned resume calls remain\nunresolved until matching terminal evidence arrives. With unresolved activity,\nfinite Guard requires that evidence or a new host session. Migration preserves\nvalid budgets including `0`. Lifecycle association uses explicit host identities,\nnever event arrival order.\n\nClaude Code equivalent:\n\n```text\n\u002Fstop-that-shit:stop-that-shit lock change files=src\u002Fconfig.cjs|test\u002Fconfig.test.cjs -- Fix this behavior.\n```\n\nDo not invent a file list to appear precise. Inspect proportionately and explain\nmaterial expansion before acting.\n\n## Finish\n\nReport the requested result, necessary consequences, and the evidence that makes\nthe task complete. Do not add a final audit loop only to satisfy this Skill.\n",{"name":5,"license":15,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstop-that-shit",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill stop-that-shit",{"tool":58,"command":59},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill stop-that-shit",{"tool":61,"command":62},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill stop-that-shit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstop-that-shit\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"agents\u002Fopenai.yaml","REFERENCE","参考文档",263,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flennney\u002Fstop-that-shit\u002Fskills\u002Fstop-that-shit\u002Fagents\u002Fopenai.yaml",[73,82,90,98,106,114],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"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.","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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":81},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":81},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":81},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":81},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":81},"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",[],[]]