[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MMF00THE2ABNTCE1YCAFD4":3,"skill-same:01M6MMF00THE2ABNTCE1YCAFD4":104},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":74,"commitSha":75,"skillDirectory":76,"forksCount":77,"repositoryHtmlUrl":78,"repositoryHomepageUrl":79,"ownerHtmlUrl":80,"ownerBlogUrl":81,"ownerDescription":82,"updatedAt":83,"install":84,"resources":97},"01M6MMF00THE2ABNTCE1YCAFD4","adversarial-review",null,"敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法\n（Pre-mortem \u002F War Game \u002F Logic Torturing）と、宣言・主張と実態の乖離を突く\nclaim-vs-actual 検出3パターン（Self-Contradiction \u002F Refactor-Claim Audit \u002F\nCross-File Leakage）へルーティングし、通常のレビューでは見えない設計の盲点・\n防御の穴・論理の弱点・宣言と実装のズレを可視化する。","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\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Fadversarial-review\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[24,25,26,27,28,5,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"review","adversarial","adversarial review","diff","design","jsx","pages","bias","self","upstream","claim","tsx","adr","src","game","refactor","actions","audit","file","routing","2026-11-10 10:12:30",false,"---\nid: adversarial-review\nname: adversarial-review\ndescription: |\n  敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法\n  （Pre-mortem \u002F War Game \u002F Logic Torturing）と、宣言・主張と実態の乖離を突く\n  claim-vs-actual 検出3パターン（Self-Contradiction \u002F Refactor-Claim Audit \u002F\n  Cross-File Leakage）へルーティングし、通常のレビューでは見えない設計の盲点・\n  防御の穴・論理の弱点・宣言と実装のズレを可視化する。\ncategory: midstream\nphase: [upstream, midstream]\nseverity: major\napplyTo:\n  - 'src\u002F**\u002F*.{ts,tsx,js,jsx,mjs}'\n  - 'docs\u002F**\u002F*design*.md'\n  - 'docs\u002Fadr\u002F**\u002F*'\n  - 'pages\u002F**\u002F*design*.md'\ninputContext: [diff, fullFile]\noutputKind: [findings, questions, actions]\ntags:\n  [\n    adversarial,\n    pre-mortem,\n    war-game,\n    logic-torturing,\n    self-contradiction,\n    refactor-claim,\n    cross-file-leakage,\n    claim-vs-actual,\n    cognitive-bias,\n    entry,\n    routing,\n  ]\nversion: '0.1.0'\nlicense: MIT\n---\n\n# Adversarial Review（敵対的レビュー）\n\n通常のコードレビューは「正しさの確認」に集中する。\n敵対的レビューは **「どう壊れるか」「どう攻撃されるか」「どこが論理的に弱いか」** に集中する。\n\n## 背景 \u002F Background\n\nAIをレビューに使う最大の価値は、情報の整理ではなく **思考の死角を映す鏡** としての活用にある。\nこのスキルは、2系統の敵対的手法を体系化し、レビューの質を根本的に引き上げる。\n\n### 認知バイアス対策（思考の死角）\n\n| 手法            | 対策するバイアス           | 核心の問い                           |\n| --------------- | -------------------------- | ------------------------------------ |\n| Pre-mortem      | 生存バイアス・楽観バイアス | 「失敗した**として**、なぜ？」       |\n| War Game        | 自己中心バイアス           | 「敵の立場**から**、どう攻撃する？」 |\n| Logic Torturing | 確証バイアス               | 「この論理の穴を**潰して**」         |\n\n### claim-vs-actual 検出（宣言・主張と実態の乖離）\n\n| 手法                 | 対象とするズレ           | 核心の問い                                    |\n| -------------------- | ------------------------ | --------------------------------------------- |\n| Self-Contradiction   | 宣言と同一ファイルの実装 | 「規則 X を宣言した本人が**破って**いない？」 |\n| Refactor-Claim Audit | 完了主張と残骸           | 「『全部やった』を grep で**反証**できる？」  |\n| Cross-File Leakage   | 構造変更と caller 側     | 「直したのは変更元だけ、**参照元**は？」      |\n\n## When to Use \u002F いつ使うか\n\n- 設計判断やアーキテクチャ変更を含むPRのレビュー時\n- セキュリティに影響する変更のレビュー時\n- 重要な技術選択の妥当性を検証したいとき\n- 「本当にこれで大丈夫か？」という不安があるとき\n\n## Routing \u002F ルーティング\n\n入力に応じて、適切な手法へルーティングする。複数手法の併用も可能。\n\n| キーワード                                          | 手法                 | スキルID               |\n| --------------------------------------------------- | -------------------- | ---------------------- |\n| 失敗, リスク, 負債, インシデント, pre-mortem        | Pre-mortem           | `pre-mortem`           |\n| 攻撃, セキュリティ, 悪用, 脆弱性, war-game          | War Game             | `war-game`             |\n| 論理, 判断, 根拠, なぜ, 代替案, logic               | Logic Torturing      | `logic-torturing`      |\n| 自己矛盾, contradiction, 宣言と実装, declared but   | Self-Contradiction   | `self-contradiction`   |\n| 削減, 完了, 全て置換, all replaced, -N%, リファクタ | Refactor-Claim Audit | `refactor-claim-audit` |\n| caller, 残骸, 参照漏れ, 再採番, leakage             | Cross-File Leakage   | `cross-file-leakage`   |\n| 敵対的, adversarial, 全部, フル                     | **全手法実行**       | 上記6つすべて          |\n\n### デフォルト動作\n\n- キーワード指定なし → 変更内容から自動判定:\n  - 設計ドキュメント\u002FADR → Pre-mortem + Logic Torturing\n  - セキュリティ関連コード → War Game + Logic Torturing\n  - 一般的なコード変更 → Logic Torturing\n  - 宣言的フレーズ（「禁止」「必ず」「MUST」等）を含む変更 → Self-Contradiction\n  - 完了主張（「全置換」「-N%」等）を含む commit\u002FPR → Refactor-Claim Audit\n  - 構造変更（再採番・シンボル改名・分割）を含む変更 → Cross-File Leakage\n  - 大規模変更（ファイル数10以上or差分500行以上）→ 全手法実行\n\n## Execution Flow \u002F 実行フロー\n\n```text\n1. 変更内容の分類\n   ├─ 設計\u002FADR → Pre-mortem を優先実行\n   ├─ セキュリティ関連 → War Game を優先実行\n   ├─ 判断を含む変更 → Logic Torturing を実行\n   ├─ 宣言的フレーズ → Self-Contradiction を実行\n   ├─ 完了主張 → Refactor-Claim Audit を実行\n   └─ 構造変更 → Cross-File Leakage を実行\n\n2. 各手法の実行（並列可能）\n   ├─ Pre-mortem: 失敗シナリオ × 最大5件\n   ├─ War Game: 攻撃シナリオ × 最大5件\n   ├─ Logic Torturing: 論理検証 × 最大5件\n   ├─ Self-Contradiction: 宣言と実装の乖離 × 最大5件\n   ├─ Refactor-Claim Audit: 完了主張の反証 × 最大5件\n   └─ Cross-File Leakage: caller 側残骸 × 最大5件\n\n3. 統合サマリの生成\n   ├─ 重複する指摘の統合\n   ├─ 重大度による優先順位付け\n   └─ Human Handoff 条件の判定\n```\n\n## Output Format \u002F 出力形式\n\n```markdown\n## ? Adversarial Review Summary\n\n### 検出された盲点: N件\n\n- Pre-mortem: X件 (失敗シナリオ)\n- War Game: Y件 (攻撃シナリオ)\n- Logic Torturing: Z件 (論理的な穴)\n- Self-Contradiction: A件 (宣言と実装の乖離)\n- Refactor-Claim Audit: B件 (完了主張の反証)\n- Cross-File Leakage: C件 (caller 側残骸)\n\n### 最も重大な発見\n\n\u003C最も致命的な1件の要約>\n\n### 詳細\n\n(各手法の出力を統合)\n```\n\n## 他スキルとの関係\n\n| 既存スキル                   | 関係 | 棲み分け                                                                                                          |\n| ---------------------------- | ---- | ----------------------------------------------------------------------------------------------------------------- |\n| `architecture-risk-register` | 補完 | risk-register は「リスクが文書化されているか」を確認。Pre-mortem は「文書化されていないリスクを発見」する         |\n| `security-basic`             | 補完 | security-basic は既知パターン（SQLi, XSS等）を検出。War Game は「既知パターンに当てはまらない攻撃経路」を発見する |\n| `adr-decision-quality`       | 補完 | adr-decision は ADR の形式品質を確認。Logic Torturing は「記述された判断の論理的強度」を検証する                  |\n\n## References\n\n- [TECHNIQUES.md](.\u002Freferences\u002FTECHNIQUES.md): 3手法の理論的背景と実践ガイド\n","# Adversarial Review（敵対的レビュー）\n\n通常のコードレビューは「正しさの確認」に集中する。\n敵対的レビューは **「どう壊れるか」「どう攻撃されるか」「どこが論理的に弱いか」** に集中する。\n\n## 背景 \u002F Background\n\nAIをレビューに使う最大の価値は、情報の整理ではなく **思考の死角を映す鏡** としての活用にある。\nこのスキルは、2系統の敵対的手法を体系化し、レビューの質を根本的に引き上げる。\n\n### 認知バイアス対策（思考の死角）\n\n| 手法            | 対策するバイアス           | 核心の問い                           |\n| --------------- | -------------------------- | ------------------------------------ |\n| Pre-mortem      | 生存バイアス・楽観バイアス | 「失敗した**として**、なぜ？」       |\n| War Game        | 自己中心バイアス           | 「敵の立場**から**、どう攻撃する？」 |\n| Logic Torturing | 確証バイアス               | 「この論理の穴を**潰して**」         |\n\n### claim-vs-actual 検出（宣言・主張と実態の乖離）\n\n| 手法                 | 対象とするズレ           | 核心の問い                                    |\n| -------------------- | ------------------------ | --------------------------------------------- |\n| Self-Contradiction   | 宣言と同一ファイルの実装 | 「規則 X を宣言した本人が**破って**いない？」 |\n| Refactor-Claim Audit | 完了主張と残骸           | 「『全部やった』を grep で**反証**できる？」  |\n| Cross-File Leakage   | 構造変更と caller 側     | 「直したのは変更元だけ、**参照元**は？」      |\n\n## When to Use \u002F いつ使うか\n\n- 設計判断やアーキテクチャ変更を含むPRのレビュー時\n- セキュリティに影響する変更のレビュー時\n- 重要な技術選択の妥当性を検証したいとき\n- 「本当にこれで大丈夫か？」という不安があるとき\n\n## Routing \u002F ルーティング\n\n入力に応じて、適切な手法へルーティングする。複数手法の併用も可能。\n\n| キーワード                                          | 手法                 | スキルID               |\n| --------------------------------------------------- | -------------------- | ---------------------- |\n| 失敗, リスク, 負債, インシデント, pre-mortem        | Pre-mortem           | `pre-mortem`           |\n| 攻撃, セキュリティ, 悪用, 脆弱性, war-game          | War Game             | `war-game`             |\n| 論理, 判断, 根拠, なぜ, 代替案, logic               | Logic Torturing      | `logic-torturing`      |\n| 自己矛盾, contradiction, 宣言と実装, declared but   | Self-Contradiction   | `self-contradiction`   |\n| 削減, 完了, 全て置換, all replaced, -N%, リファクタ | Refactor-Claim Audit | `refactor-claim-audit` |\n| caller, 残骸, 参照漏れ, 再採番, leakage             | Cross-File Leakage   | `cross-file-leakage`   |\n| 敵対的, adversarial, 全部, フル                     | **全手法実行**       | 上記6つすべて          |\n\n### デフォルト動作\n\n- キーワード指定なし → 変更内容から自動判定:\n  - 設計ドキュメント\u002FADR → Pre-mortem + Logic Torturing\n  - セキュリティ関連コード → War Game + Logic Torturing\n  - 一般的なコード変更 → Logic Torturing\n  - 宣言的フレーズ（「禁止」「必ず」「MUST」等）を含む変更 → Self-Contradiction\n  - 完了主張（「全置換」「-N%」等）を含む commit\u002FPR → Refactor-Claim Audit\n  - 構造変更（再採番・シンボル改名・分割）を含む変更 → Cross-File Leakage\n  - 大規模変更（ファイル数10以上or差分500行以上）→ 全手法実行\n\n## Execution Flow \u002F 実行フロー\n\n```text\n1. 変更内容の分類\n   ├─ 設計\u002FADR → Pre-mortem を優先実行\n   ├─ セキュリティ関連 → War Game を優先実行\n   ├─ 判断を含む変更 → Logic Torturing を実行\n   ├─ 宣言的フレーズ → Self-Contradiction を実行\n   ├─ 完了主張 → Refactor-Claim Audit を実行\n   └─ 構造変更 → Cross-File Leakage を実行\n\n2. 各手法の実行（並列可能）\n   ├─ Pre-mortem: 失敗シナリオ × 最大5件\n   ├─ War Game: 攻撃シナリオ × 最大5件\n   ├─ Logic Torturing: 論理検証 × 最大5件\n   ├─ Self-Contradiction: 宣言と実装の乖離 × 最大5件\n   ├─ Refactor-Claim Audit: 完了主張の反証 × 最大5件\n   └─ Cross-File Leakage: caller 側残骸 × 最大5件\n\n3. 統合サマリの生成\n   ├─ 重複する指摘の統合\n   ├─ 重大度による優先順位付け\n   └─ Human Handoff 条件の判定\n```\n\n## Output Format \u002F 出力形式\n\n```markdown\n## ? Adversarial Review Summary\n\n### 検出された盲点: N件\n\n- Pre-mortem: X件 (失敗シナリオ)\n- War Game: Y件 (攻撃シナリオ)\n- Logic Torturing: Z件 (論理的な穴)\n- Self-Contradiction: A件 (宣言と実装の乖離)\n- Refactor-Claim Audit: B件 (完了主張の反証)\n- Cross-File Leakage: C件 (caller 側残骸)\n\n### 最も重大な発見\n\n\u003C最も致命的な1件の要約>\n\n### 詳細\n\n(各手法の出力を統合)\n```\n\n## 他スキルとの関係\n\n| 既存スキル                   | 関係 | 棲み分け                                                                                                          |\n| ---------------------------- | ---- | ----------------------------------------------------------------------------------------------------------------- |\n| `architecture-risk-register` | 補完 | risk-register は「リスクが文書化されているか」を確認。Pre-mortem は「文書化されていないリスクを発見」する         |\n| `security-basic`             | 補完 | security-basic は既知パターン（SQLi, XSS等）を検出。War Game は「既知パターンに当てはまらない攻撃経路」を発見する |\n| `adr-decision-quality`       | 補完 | adr-decision は ADR の形式品質を確認。Logic Torturing は「記述された判断の論理的強度」を検証する                  |\n\n## References\n\n- [TECHNIQUES.md](.\u002Freferences\u002FTECHNIQUES.md): 3手法の理論的背景と実践ガイド\n",{"id":5,"name":5,"tags":49,"phase":59,"applyTo":61,"license":15,"version":66,"category":60,"severity":67,"outputKind":68,"description":71,"inputContext":72},[25,50,51,52,53,54,55,56,57,58,43],"pre-mortem","war-game","logic-torturing","self-contradiction","refactor-claim","cross-file-leakage","claim-vs-actual","cognitive-bias","entry",[33,60],"midstream",[62,63,64,65],"src\u002F**\u002F*.{ts,tsx,js,jsx,mjs}","docs\u002F**\u002F*design*.md","docs\u002Fadr\u002F**\u002F*","pages\u002F**\u002F*design*.md","0.1.0","major",[69,70,40],"findings","questions","敵対的分析手法を統合したレビューの entry skill。認知バイアス対策の3手法\n（Pre-mortem \u002F War Game \u002F Logic Torturing）と、宣言・主張と実態の乖離を突く\nclaim-vs-actual 検出3パターン（Self-Contradiction \u002F Refactor-Claim Audit \u002F\nCross-File Leakage）へルーティングし、通常のレビューでは見えない設計の盲点・\n防御の穴・論理の弱点・宣言と実装のズレを可視化する。\n",[27,73],"fullFile","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Fadversarial-review",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":85,"prompt":95,"zipAvailable":96},[86,89,92],{"tool":87,"command":88},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill adversarial-review",{"tool":90,"command":91},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill adversarial-review",{"tool":93,"command":94},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill adversarial-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Fadversarial-review\u002FSKILL.md",true,[98],{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002FTECHNIQUES.md","REFERENCE","参考文档",6288,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fs977043\u002Friver-review\u002Fskills\u002Fagent-skills\u002Fadversarial-review\u002Freferences\u002FTECHNIQUES.md",[105,114,122,130,138,146],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":113},"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":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":113},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":113},"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":113},"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":113},"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":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":150,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":113},"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",[],[]]