[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MGJEX85AXA73PJA437VW87":3,"skill-same:01M6MGJEX85AXA73PJA437VW87":75},{"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":23,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6MGJEX85AXA73PJA437VW87","sdlc-deploy",null,"Prepare a verified change for human PR review by running REVIEW.md passes through the sdlc-reviewer subagent and posting ranked findings. Do NOT use for intent or scope decisions, accepting organizational risk, self-approval, merging, deploying, or bypassing branch protection.","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\u002Fghiaog123\u002Fai-native-sdlc\u002Fskills\u002Fsdlc-deploy\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"sdlc deploy","deploy","sdlc","use","running","for","verified","scope","posting","human","self","do","intent","review","decisions","branch","reviewer","subagent","risk","pr","pr review","change","2026-11-10 10:12:30",false,"---\nname: sdlc-deploy\ndescription: Prepare a verified change for human PR review by running REVIEW.md passes through the sdlc-reviewer subagent and posting ranked findings. Do NOT use for intent or scope decisions, accepting organizational risk, self-approval, merging, deploying, or bypassing branch protection.\n---\n\n# SDLC Deploy\n\nRun Stage 5 of 6 in the AI-Native SDLC playbook described in `docs\u002FPLAYBOOK.md`.\n\n## Purpose\n\nPrepare the pull request and review evidence. This stage posts findings and stops\nfor a human; it never merges or deploys.\n\nDo not judge whether the original intent was worthwhile. Do not accept risk for the\norganization.\n\n## Entry gate\n\nProceed only when `sdlc-test` has completed with green verification evidence and\nthe code is ready for review.\n\nRead the test report. Confirm it includes actual passing output and applicable\neval evidence for any changed `CLAUDE.md`, skill, or hook.\n\nIf verification is incomplete, stale after changes, missing, or red, return to\n`sdlc-test` and stop.\n\n## Procedure\n\n0. Identify the slug for this change and read `.sdlc\u002F\u003Cslug>\u002Fspec.md` and\n   `.sdlc\u002F\u003Cslug>\u002Fplan.md`. The PR description must link them, so a reviewer can see\n   the accepted intent, spec, and plan behind the diff without leaving the PR. A\n   fast-path change has only `plan.md`: link that, and quote its `## Fast path`\n   declaration in the PR so the reviewer sees who called the change low-risk and why.\n1. Locate the project's `REVIEW.md`.\n2. If it exists, read every applicable review pass, the depth setting, the round\n   cap, the sensitive-path list, and the nit cap.\n3. If it does not exist, record that fact and continue with the required review\n   passes using sound judgment.\n4. Read `.sdlc\u002F\u003Cslug>\u002Freview-findings.md` if it exists. It carries the round\n   number, the SHA each earlier round reviewed, and every finding already posted.\n5. If the change took the fast path, compare the real diff against the\n   sensitive-path list now. A diff touching any sensitive path revokes the fast\n   path: say which path it reached, and route the change to `sdlc-plan` to enter\n   through Stage 1 and Stage 2, exactly as `sdlc-build` would have refused the\n   declaration had the file been declared. Do not review it onward.\n6. Determine the round number. If this would be round 4, stop reviewing: record\n   that the cap is reached and return the author to `plan.md` to reconsider the\n   approach rather than fixing findings one by one.\n7. Determine the review scope. Round 1 reviews the whole change; later rounds\n   review only the diff since the previous round's recorded SHA.\n8. Assemble the changes in scope, verification evidence, and `REVIEW.md`\n   instructions.\n9. Invoke the `sdlc-reviewer` subagent in review mode with the changes and the\n   passes `REVIEW.md` names for this depth. At Standard and Deep that is Bugs,\n   Security, and Compliance; at Quick it is Bugs and Security. Security runs at\n   every depth.\n10. Drop every finding an earlier round already posted. Count them.\n11. Invoke the `sdlc-reviewer` subagent again in verify mode, in a fresh context,\n    with the surviving findings and the diff they cite, and without the reasoning\n    that produced them. Discard every finding it judges not real. Count them.\n12. Require each surviving finding to carry a `REVIEW.md` severity: `Important`,\n    `Minor`, `Nit`, or `Pre-existing`.\n13. Enforce the nit cap from `REVIEW.md`; for example, if it says `max 5 nits`,\n    include at most five nits.\n14. If `REVIEW.md` has no cap, use judgment and keep nits actionable.\n15. Append this round to `.sdlc\u002F\u003Cslug>\u002Freview-findings.md` using the plugin's\n    template: round number, stage, reviewed SHA, scope, passes run, findings,\n    suppressed count, and verifier-rejected count.\n16. Scan `.sdlc\u002F*\u002Freview-findings.md` for a finding class that now appears in two\n    or more changes, and record it under **Recurring** in this change's file, with\n    what encodes it.\n17. Create or update the pull request with context, test evidence, and findings.\n18. Post the findings as a PR comment or include them in the PR body.\n19. Cite the review findings and explicitly stop for human approval.\n\nGive the reviewer only evidence and review scope, not authority to waive risks.\n\n## Reviewer request\n\nTell the `sdlc-reviewer` subagent to inspect the actual diff and report:\n\n- Bugs found by the Bugs pass.\n- Security concerns found by the Security pass.\n- Compliance concerns found by the Compliance pass.\n- Severity for each finding: `Important`, `Minor`, `Nit`, or `Pre-existing`.\n- File and line references where available.\n- Concise rationale and a suggested remediation when appropriate.\n- How many findings it suppressed as already posted in an earlier round.\n\nA real defect in code this change did not introduce is `Pre-existing`. The reviewer\nreports it; it does not block merge and is not counted against the author. A\npre-existing defect that is a security finding stays under Security at its real\nseverity and blocks merge like any other.\n\nThe verifier runs as the same subagent in verify mode, in its own context, and sees\nonly the findings and the cited code. Do not pass it the reviewer's reasoning, and\ndo not let it change a severity or add a finding. It answers one question per\nfinding: does this failure actually happen?\n\nPass through the project's `REVIEW.md` rules. Do not replace them with an invented\nreview rubric.\n\nIf no findings exist, record that the passes found none rather than fabricating\ncomments.\n\n## Findings and PR content\n\nSeparate Important findings from Nits in the PR content.\n\nKeep the number of nits within the `REVIEW.md` cap. Important findings are not\nnits and must not be hidden by the cap.\n\nList every `Pre-existing` finding in the PR under its own heading, with the\nlocation and a proposed disposition: fix now, a backlog reference, or accepted\nwith a reason. A pre-existing finding is never silently dropped. Nothing else in\nthis loop looks for old defects, so this list is the only place they surface.\n\nInclude test evidence from Stage 4 so a human can evaluate the change.\n\nState whether `REVIEW.md` was found and, if so, which passes governed the review,\nat which depth, and which round this is.\n\nState the round's counts: findings posted, suppressed as already reported, and\nrejected by the verifier.\n\nDo not alter code merely to make findings disappear without returning to the test\nstage for fresh verification.\n\n## Running in CI\n\nThe same review runs unattended. In CI, invoke Claude non-interactively inside a\nsandbox with filesystem and network isolation, scoped to the repository and the\nreview passes. A sandboxed CI run posts findings exactly as an interactive run does;\nit gains no authority to merge, deploy, or waive a finding.\n\nTreat a CI review as evidence for the human reviewer, never as a substitute for one.\n\n## Prohibitions\n\nNever merge the PR.\n\nNever deploy the code.\n\nNever bypass, disable, or work around the approval-gate hook. It fires on its own,\nand branch protection enforces the merge gate; an agent cannot override either.\n\nNever accept a security, compliance, operational, or product risk on behalf of the\norganization.\n\nNever treat your own PR post as human approval.\n\n## Exit gate\n\nBefore posting, check **Recurring** in `.sdlc\u002F\u003Cslug>\u002Freview-findings.md`. Every\nfinding class now seen in two or more changes must name what encodes it: a line in\n`CLAUDE.md`, a lint rule, or a rule in `REVIEW.md`. A row with no encoding holds\nthis gate. Fixing the instance is not fixing the class — the third occurrence is\nthe one this prevents.\n\nPost the PR and cite the ranked findings. Then explicitly stop.\n\nThe next step must be a human approval, either through branch protection or an\nexplicit `LGTM`.\n\nIf human approval has not happened, do not hand off to maintenance.\n\n## Handoff\n\nOnly once a human approves merge through branch protection or explicit `LGTM`,\nproceed to `sdlc-maintain` after the code is deployed.\n\nCarry forward the PR link, approval evidence, review findings, and deployment\nidentity if available.\n","# SDLC Deploy\n\nRun Stage 5 of 6 in the AI-Native SDLC playbook described in `docs\u002FPLAYBOOK.md`.\n\n## Purpose\n\nPrepare the pull request and review evidence. This stage posts findings and stops\nfor a human; it never merges or deploys.\n\nDo not judge whether the original intent was worthwhile. Do not accept risk for the\norganization.\n\n## Entry gate\n\nProceed only when `sdlc-test` has completed with green verification evidence and\nthe code is ready for review.\n\nRead the test report. Confirm it includes actual passing output and applicable\neval evidence for any changed `CLAUDE.md`, skill, or hook.\n\nIf verification is incomplete, stale after changes, missing, or red, return to\n`sdlc-test` and stop.\n\n## Procedure\n\n0. Identify the slug for this change and read `.sdlc\u002F\u003Cslug>\u002Fspec.md` and\n   `.sdlc\u002F\u003Cslug>\u002Fplan.md`. The PR description must link them, so a reviewer can see\n   the accepted intent, spec, and plan behind the diff without leaving the PR. A\n   fast-path change has only `plan.md`: link that, and quote its `## Fast path`\n   declaration in the PR so the reviewer sees who called the change low-risk and why.\n1. Locate the project's `REVIEW.md`.\n2. If it exists, read every applicable review pass, the depth setting, the round\n   cap, the sensitive-path list, and the nit cap.\n3. If it does not exist, record that fact and continue with the required review\n   passes using sound judgment.\n4. Read `.sdlc\u002F\u003Cslug>\u002Freview-findings.md` if it exists. It carries the round\n   number, the SHA each earlier round reviewed, and every finding already posted.\n5. If the change took the fast path, compare the real diff against the\n   sensitive-path list now. A diff touching any sensitive path revokes the fast\n   path: say which path it reached, and route the change to `sdlc-plan` to enter\n   through Stage 1 and Stage 2, exactly as `sdlc-build` would have refused the\n   declaration had the file been declared. Do not review it onward.\n6. Determine the round number. If this would be round 4, stop reviewing: record\n   that the cap is reached and return the author to `plan.md` to reconsider the\n   approach rather than fixing findings one by one.\n7. Determine the review scope. Round 1 reviews the whole change; later rounds\n   review only the diff since the previous round's recorded SHA.\n8. Assemble the changes in scope, verification evidence, and `REVIEW.md`\n   instructions.\n9. Invoke the `sdlc-reviewer` subagent in review mode with the changes and the\n   passes `REVIEW.md` names for this depth. At Standard and Deep that is Bugs,\n   Security, and Compliance; at Quick it is Bugs and Security. Security runs at\n   every depth.\n10. Drop every finding an earlier round already posted. Count them.\n11. Invoke the `sdlc-reviewer` subagent again in verify mode, in a fresh context,\n    with the surviving findings and the diff they cite, and without the reasoning\n    that produced them. Discard every finding it judges not real. Count them.\n12. Require each surviving finding to carry a `REVIEW.md` severity: `Important`,\n    `Minor`, `Nit`, or `Pre-existing`.\n13. Enforce the nit cap from `REVIEW.md`; for example, if it says `max 5 nits`,\n    include at most five nits.\n14. If `REVIEW.md` has no cap, use judgment and keep nits actionable.\n15. Append this round to `.sdlc\u002F\u003Cslug>\u002Freview-findings.md` using the plugin's\n    template: round number, stage, reviewed SHA, scope, passes run, findings,\n    suppressed count, and verifier-rejected count.\n16. Scan `.sdlc\u002F*\u002Freview-findings.md` for a finding class that now appears in two\n    or more changes, and record it under **Recurring** in this change's file, with\n    what encodes it.\n17. Create or update the pull request with context, test evidence, and findings.\n18. Post the findings as a PR comment or include them in the PR body.\n19. Cite the review findings and explicitly stop for human approval.\n\nGive the reviewer only evidence and review scope, not authority to waive risks.\n\n## Reviewer request\n\nTell the `sdlc-reviewer` subagent to inspect the actual diff and report:\n\n- Bugs found by the Bugs pass.\n- Security concerns found by the Security pass.\n- Compliance concerns found by the Compliance pass.\n- Severity for each finding: `Important`, `Minor`, `Nit`, or `Pre-existing`.\n- File and line references where available.\n- Concise rationale and a suggested remediation when appropriate.\n- How many findings it suppressed as already posted in an earlier round.\n\nA real defect in code this change did not introduce is `Pre-existing`. The reviewer\nreports it; it does not block merge and is not counted against the author. A\npre-existing defect that is a security finding stays under Security at its real\nseverity and blocks merge like any other.\n\nThe verifier runs as the same subagent in verify mode, in its own context, and sees\nonly the findings and the cited code. Do not pass it the reviewer's reasoning, and\ndo not let it change a severity or add a finding. It answers one question per\nfinding: does this failure actually happen?\n\nPass through the project's `REVIEW.md` rules. Do not replace them with an invented\nreview rubric.\n\nIf no findings exist, record that the passes found none rather than fabricating\ncomments.\n\n## Findings and PR content\n\nSeparate Important findings from Nits in the PR content.\n\nKeep the number of nits within the `REVIEW.md` cap. Important findings are not\nnits and must not be hidden by the cap.\n\nList every `Pre-existing` finding in the PR under its own heading, with the\nlocation and a proposed disposition: fix now, a backlog reference, or accepted\nwith a reason. A pre-existing finding is never silently dropped. Nothing else in\nthis loop looks for old defects, so this list is the only place they surface.\n\nInclude test evidence from Stage 4 so a human can evaluate the change.\n\nState whether `REVIEW.md` was found and, if so, which passes governed the review,\nat which depth, and which round this is.\n\nState the round's counts: findings posted, suppressed as already reported, and\nrejected by the verifier.\n\nDo not alter code merely to make findings disappear without returning to the test\nstage for fresh verification.\n\n## Running in CI\n\nThe same review runs unattended. In CI, invoke Claude non-interactively inside a\nsandbox with filesystem and network isolation, scoped to the repository and the\nreview passes. A sandboxed CI run posts findings exactly as an interactive run does;\nit gains no authority to merge, deploy, or waive a finding.\n\nTreat a CI review as evidence for the human reviewer, never as a substitute for one.\n\n## Prohibitions\n\nNever merge the PR.\n\nNever deploy the code.\n\nNever bypass, disable, or work around the approval-gate hook. It fires on its own,\nand branch protection enforces the merge gate; an agent cannot override either.\n\nNever accept a security, compliance, operational, or product risk on behalf of the\norganization.\n\nNever treat your own PR post as human approval.\n\n## Exit gate\n\nBefore posting, check **Recurring** in `.sdlc\u002F\u003Cslug>\u002Freview-findings.md`. Every\nfinding class now seen in two or more changes must name what encodes it: a line in\n`CLAUDE.md`, a lint rule, or a rule in `REVIEW.md`. A row with no encoding holds\nthis gate. Fixing the instance is not fixing the class — the third occurrence is\nthe one this prevents.\n\nPost the PR and cite the ranked findings. Then explicitly stop.\n\nThe next step must be a human approval, either through branch protection or an\nexplicit `LGTM`.\n\nIf human approval has not happened, do not hand off to maintenance.\n\n## Handoff\n\nOnly once a human approves merge through branch protection or explicit `LGTM`,\nproceed to `sdlc-maintain` after the code is deployed.\n\nCarry forward the PR link, approval evidence, review findings, and deployment\nidentity if available.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fghiaog123\u002Fai-native-sdlc\u002Fskills\u002Fsdlc-deploy",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sdlc-deploy",{"tool":67,"command":68},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sdlc-deploy",{"tool":70,"command":71},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill sdlc-deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fghiaog123\u002Fai-native-sdlc\u002Fskills\u002Fsdlc-deploy\u002FSKILL.md",true,[],[76,86,94,102,110,118],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":81,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":85},"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":85},"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":85},"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":85},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":85},"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":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":80,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":85},"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",[],[]]