[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MEPX4CTSG02M8BG1AEYVV3":3,"skill-same:01M6MEPX4CTSG02M8BG1AEYVV3":133},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":82,"commitSha":83,"skillDirectory":84,"forksCount":85,"repositoryHtmlUrl":86,"repositoryHomepageUrl":87,"ownerHtmlUrl":88,"ownerBlogUrl":89,"ownerDescription":90,"updatedAt":91,"install":92,"resources":104},"01M6MEPX4CTSG02M8BG1AEYVV3","idea-genie",null,"Brainstorm evidence-backed options for what to build, or stress-test an idea. Use when: deciding what to build next, comparing options or testing an idea.","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\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"idea","genie","idea genie","when","write","scripts","options","customer","generate","portfolio","next","plan","stress-test","question","design","eval","challenge","brainstorm","testing","lean","mode","2026-11-10 10:12:30",false,"---\nname: idea-genie\ndescription: 'Brainstorm evidence-backed options for what to build, or stress-test an idea. Use when: deciding what to build next, comparing options or testing an idea.'\npractices: [lean-startup, bdd-gherkin, design-by-contract, llm-eval-harness, adr]\nhexagonal_role: domain\nconsumes: [repo-context, task-question, idea-portfolio.v1]\nproduces: [idea-portfolio.v1, idea-challenge.v1]\ncontext_rel:\n- kind: customer-of\n  with: research\n- kind: supplier-to\n  with: plan\nskill_api_version: 1\nuser-invocable: true\nmetadata:\n  tier: execution\n  dependencies: []\n  capabilities: [generate_evidenced_options, dueling_idea_genies]\n  effects: [write_idea_portfolio]\n  canonical_status: canonical\n  disposition: keep_strategy\noutput_contract: idea-portfolio.v1 JSON validated by this skill's scripts\u002Fvalidate-output.sh (elicit mode), or idea-challenge.v1 JSON validated by this skill's scripts\u002Fvalidate-challenge.sh (duel mode)\n---\n\n# Idea Genie\n\nReturn evidence-backed options: every candidate cites an observation, overlap\nwith what already exists is checked before novelty is claimed, and nothing is\nranked or picked. That is elicit mode, the entry mode. Duel mode challenges one\nconsequential choice with sealed independent perspectives. Both modes advise;\nneither selects, schedules, tracks, implements or validates work.\n\n| Use instead | When |\n|---|---|\n| [Navigate](..\u002Fnavigate\u002FSKILL.md) | the next item in an existing epic or bead graph |\n| [Council](..\u002Fcouncil\u002FSKILL.md) | members scoring each other's ideas, or several views on any question |\n| [Premortem](..\u002Fpremortem\u002FSKILL.md) | how a plan could fail |\n\nBoth validators live in this skill's `scripts\u002F` directory and need `jq`; exit 2\nmeans nothing was checked. Then check the fields by hand against the shape and\nsay the validator did not run.\n\n`\u003Cskill-dir>` is the directory that contains this SKILL.md. Claude Code shows it\nas \"Base directory for this skill\"; Codex lists this skill's SKILL.md path; in\nan AgentOps source checkout it is `skills\u002Fidea-genie`. Replace `\u003Cskill-dir>`\nwith that absolute path before running a command. The working directory stays\nthe user's repository. If the host did not show where this skill is installed,\nuse the directory of the SKILL.md you read. If you cannot determine it, do not\nguess a path or run a same-named script from the current repository; say the\nbundled script is unavailable and check the fields by hand against the shape,\nas without `jq`.\n\n## Elicit mode\n\nThese rules carry the value:\n\n1. **Observations cite a source:** a file and line, issue, doc or measurement.\n   Anything uncited is an assumption, listed apart and never used as support.\n2. **Every candidate cites the observations behind it.** No cited support, no\n   candidate; an unsupported idea may stay listed as an assumption. Never pad\n   the list to a count.\n3. **Check overlap before claiming novelty.** Compare each candidate with what\n   the product already does and with earlier decisions that still apply (an\n   ADR, closed issue or recorded lesson). A request an existing capability\n   already covers is not new: record it under `overlaps` of the candidate it\n   sharpens, or leave it out. Keep an idea a decision rejected only with new\n   evidence that answers its reason, citing the decision under `overlaps`.\n4. **One Given\u002FWhen\u002FThen per candidate**, a normal or edge case whose Then\n   shows the cited problem easing; a Then that could hold while the problem\n   remains aims at a proxy. A goal or a symptom is not yet the problem: cite\n   its cause, or list the cause as an assumption and let the Then show the\n   cited symptom easing.\n5. **Do not rank, pick, schedule or start work.** The caller or Plan selects.\n6. **Stop at saturation.** Merge equivalents, and run another pass only while\n   it adds a materially new evidenced candidate. Zero candidates is valid.\n7. **Generate before judging.** Split the subject into the parts its evidence\n   shows, named in its own words rather than as a directory listing, and draft\n   across each before filtering. Then reshape the predictable first ideas:\n   remove or invert a step, break an assumption treated as fixed, push a\n   constraint to an extreme, borrow how another field solves the same problem,\n   or find a move that makes later moves cheaper. A candidate any project could\n   list unchanged gets a specific observation or is dropped. Keep a one-line\n   reason for each dropped idea in `dropped` so a later pass does not\n   regenerate it, and list there any part left with no supported candidate.\n8. **Behavior outweighs stated interest.** \"Users asked for it\" is weaker than\n   what they do now: the workaround they already use, what it costs them, and\n   observed adoption of anything similar. Name the status quo each candidate\n   must beat in `status_quo`; if nobody is working around the problem today,\n   say so there.\n\nState the question, constraints, non-goals and sources first. Read only the\nsources this question needs and cite each one; do not build a merged context\nstore.\n\nInside a named part (a flow, command, page or stage), go as far as the\nevidence allows: a candidate that reshapes the wider product is a scope\noverrun, and one that swaps the subject for another domain replaces it. Drop\neither with that reason unless a cited observation shows the part cannot\nchange without it. With no named subject, sample each top-level area and the\nrecent commits instead of guessing one focus, and let each candidate's\nevidence show why its subject deserves attention.\n\nReturn the portfolio in this shape:\n\n```json\n{\n  \"schema_version\": \"idea-portfolio.v1\",\n  \"status\": \"candidates\",\n  \"observations\": [{\"claim\": \"\u003Cwhat is true>\", \"evidence\": \"\u003Ccited source>\"}],\n  \"assumptions\": [\"\u003Cbelief no cited source supports>\"],\n  \"candidates\": [{\n    \"id\": \"I1\",\n    \"idea\": \"\u003Cshort name>\",\n    \"evidence\": [\"\u003Ccited source>\"],\n    \"overlaps\": [\"\u003Cexisting capability or decision it extends or repeats>\"],\n    \"status_quo\": \"\u003Cwhat people do today instead, or none>\",\n    \"scenario\": {\"given\": \"\u003Cstate>\", \"when\": \"\u003Cevent>\", \"then\": \"\u003Cobservable result>\"}\n  }],\n  \"dropped\": [{\"idea\": \"\u003Cshort name>\", \"reason\": \"\u003Coverlap, no evidence, or why it lost>\"}]\n}\n```\n\nEach candidate `evidence` entry repeats an observation's `evidence` exactly.\nCandidate ids are unique and `overlaps` may be empty. `dropped` is optional\nwhile there are candidates. When every idea overlaps or lacks support, set\n`status` to `no-new-work`, leave `candidates` empty and list each idea in\n`dropped` with the capability, decision or missing evidence that removed it.\n`observations` still needs one entry or more: cite what you read, even when it\nsupports no candidate. The validator rejects any other field, so no rank or\nwinner rides along. For a person, render the same fields as a short list, one\nblock per candidate. Write a file only to a destination the caller names,\noutside the user's work tree unless the caller asks for a path inside it; with\nno destination, return the portfolio inline and write no file. Check it with\n`bash \"\u003Cskill-dir>\u002Fscripts\u002Fvalidate-output.sh\" \u003Cpath>`, or with `-` and the\nJSON on stdin when nothing was written, before returning it to the caller.\nElicit worked when the validator accepts the portfolio, each candidate's Then\nshows its cited problem easing, and no rank or winner appears.\n\n## Duel mode\n\nProduce independent challenges for a consequential choice. The result is\nadvisory evidence for Plan: return it to the caller, who may supply it to\nPlan beside research and operator intent. It never decides whether a plan is\nready and never turns a later optional Premortem challenge into an approval\ngate. Emit no readiness, approval, quorum, retry, budget, helper, delivery, or\ntracker state: this strategy supplies evidence, not lifecycle authority.\nConsensus, transport availability or a self-score never becomes readiness.\n\n**Door class.** Ask what undoing the choice after it lands would cost. A\none-way door needs a migration, breaks a published contract or caller, loses\ndata, or has an external effect that cannot be recalled: open the\n[duel workflow](references\u002Fduel-mode.md), which owns the steps and the\n`idea-challenge.v1` packet. A cheap two-way door is undone by a revert or a\nflag: run Plan's [one fresh challenge](..\u002Fplan\u002Freferences\u002Fchallenge.md) instead\nand return its findings, with no packet, panel, pane manager or model-family\nrule. Duel mode worked when a one-way door returns a packet that the validator\naccepts, with every perspective cross-reviewed and dissent kept, and a two-way\ndoor returns no packet.\n\n## References\n\n- [Idea Genie behavior](references\u002Fidea-genie.feature)\n- [Idea challenge behavior](references\u002Fidea-challenge.feature)\n- [Duel mode workflow](references\u002Fduel-mode.md)\n- [Sealed perspectives](references\u002Fsealed-perspectives.md)\n","# Idea Genie\n\nReturn evidence-backed options: every candidate cites an observation, overlap\nwith what already exists is checked before novelty is claimed, and nothing is\nranked or picked. That is elicit mode, the entry mode. Duel mode challenges one\nconsequential choice with sealed independent perspectives. Both modes advise;\nneither selects, schedules, tracks, implements or validates work.\n\n| Use instead | When |\n|---|---|\n| [Navigate](..\u002Fnavigate\u002FSKILL.md) | the next item in an existing epic or bead graph |\n| [Council](..\u002Fcouncil\u002FSKILL.md) | members scoring each other's ideas, or several views on any question |\n| [Premortem](..\u002Fpremortem\u002FSKILL.md) | how a plan could fail |\n\nBoth validators live in this skill's `scripts\u002F` directory and need `jq`; exit 2\nmeans nothing was checked. Then check the fields by hand against the shape and\nsay the validator did not run.\n\n`\u003Cskill-dir>` is the directory that contains this SKILL.md. Claude Code shows it\nas \"Base directory for this skill\"; Codex lists this skill's SKILL.md path; in\nan AgentOps source checkout it is `skills\u002Fidea-genie`. Replace `\u003Cskill-dir>`\nwith that absolute path before running a command. The working directory stays\nthe user's repository. If the host did not show where this skill is installed,\nuse the directory of the SKILL.md you read. If you cannot determine it, do not\nguess a path or run a same-named script from the current repository; say the\nbundled script is unavailable and check the fields by hand against the shape,\nas without `jq`.\n\n## Elicit mode\n\nThese rules carry the value:\n\n1. **Observations cite a source:** a file and line, issue, doc or measurement.\n   Anything uncited is an assumption, listed apart and never used as support.\n2. **Every candidate cites the observations behind it.** No cited support, no\n   candidate; an unsupported idea may stay listed as an assumption. Never pad\n   the list to a count.\n3. **Check overlap before claiming novelty.** Compare each candidate with what\n   the product already does and with earlier decisions that still apply (an\n   ADR, closed issue or recorded lesson). A request an existing capability\n   already covers is not new: record it under `overlaps` of the candidate it\n   sharpens, or leave it out. Keep an idea a decision rejected only with new\n   evidence that answers its reason, citing the decision under `overlaps`.\n4. **One Given\u002FWhen\u002FThen per candidate**, a normal or edge case whose Then\n   shows the cited problem easing; a Then that could hold while the problem\n   remains aims at a proxy. A goal or a symptom is not yet the problem: cite\n   its cause, or list the cause as an assumption and let the Then show the\n   cited symptom easing.\n5. **Do not rank, pick, schedule or start work.** The caller or Plan selects.\n6. **Stop at saturation.** Merge equivalents, and run another pass only while\n   it adds a materially new evidenced candidate. Zero candidates is valid.\n7. **Generate before judging.** Split the subject into the parts its evidence\n   shows, named in its own words rather than as a directory listing, and draft\n   across each before filtering. Then reshape the predictable first ideas:\n   remove or invert a step, break an assumption treated as fixed, push a\n   constraint to an extreme, borrow how another field solves the same problem,\n   or find a move that makes later moves cheaper. A candidate any project could\n   list unchanged gets a specific observation or is dropped. Keep a one-line\n   reason for each dropped idea in `dropped` so a later pass does not\n   regenerate it, and list there any part left with no supported candidate.\n8. **Behavior outweighs stated interest.** \"Users asked for it\" is weaker than\n   what they do now: the workaround they already use, what it costs them, and\n   observed adoption of anything similar. Name the status quo each candidate\n   must beat in `status_quo`; if nobody is working around the problem today,\n   say so there.\n\nState the question, constraints, non-goals and sources first. Read only the\nsources this question needs and cite each one; do not build a merged context\nstore.\n\nInside a named part (a flow, command, page or stage), go as far as the\nevidence allows: a candidate that reshapes the wider product is a scope\noverrun, and one that swaps the subject for another domain replaces it. Drop\neither with that reason unless a cited observation shows the part cannot\nchange without it. With no named subject, sample each top-level area and the\nrecent commits instead of guessing one focus, and let each candidate's\nevidence show why its subject deserves attention.\n\nReturn the portfolio in this shape:\n\n```json\n{\n  \"schema_version\": \"idea-portfolio.v1\",\n  \"status\": \"candidates\",\n  \"observations\": [{\"claim\": \"\u003Cwhat is true>\", \"evidence\": \"\u003Ccited source>\"}],\n  \"assumptions\": [\"\u003Cbelief no cited source supports>\"],\n  \"candidates\": [{\n    \"id\": \"I1\",\n    \"idea\": \"\u003Cshort name>\",\n    \"evidence\": [\"\u003Ccited source>\"],\n    \"overlaps\": [\"\u003Cexisting capability or decision it extends or repeats>\"],\n    \"status_quo\": \"\u003Cwhat people do today instead, or none>\",\n    \"scenario\": {\"given\": \"\u003Cstate>\", \"when\": \"\u003Cevent>\", \"then\": \"\u003Cobservable result>\"}\n  }],\n  \"dropped\": [{\"idea\": \"\u003Cshort name>\", \"reason\": \"\u003Coverlap, no evidence, or why it lost>\"}]\n}\n```\n\nEach candidate `evidence` entry repeats an observation's `evidence` exactly.\nCandidate ids are unique and `overlaps` may be empty. `dropped` is optional\nwhile there are candidates. When every idea overlaps or lacks support, set\n`status` to `no-new-work`, leave `candidates` empty and list each idea in\n`dropped` with the capability, decision or missing evidence that removed it.\n`observations` still needs one entry or more: cite what you read, even when it\nsupports no candidate. The validator rejects any other field, so no rank or\nwinner rides along. For a person, render the same fields as a short list, one\nblock per candidate. Write a file only to a destination the caller names,\noutside the user's work tree unless the caller asks for a path inside it; with\nno destination, return the portfolio inline and write no file. Check it with\n`bash \"\u003Cskill-dir>\u002Fscripts\u002Fvalidate-output.sh\" \u003Cpath>`, or with `-` and the\nJSON on stdin when nothing was written, before returning it to the caller.\nElicit worked when the validator accepts the portfolio, each candidate's Then\nshows its cited problem easing, and no rank or winner appears.\n\n## Duel mode\n\nProduce independent challenges for a consequential choice. The result is\nadvisory evidence for Plan: return it to the caller, who may supply it to\nPlan beside research and operator intent. It never decides whether a plan is\nready and never turns a later optional Premortem challenge into an approval\ngate. Emit no readiness, approval, quorum, retry, budget, helper, delivery, or\ntracker state: this strategy supplies evidence, not lifecycle authority.\nConsensus, transport availability or a self-score never becomes readiness.\n\n**Door class.** Ask what undoing the choice after it lands would cost. A\none-way door needs a migration, breaks a published contract or caller, loses\ndata, or has an external effect that cannot be recalled: open the\n[duel workflow](references\u002Fduel-mode.md), which owns the steps and the\n`idea-challenge.v1` packet. A cheap two-way door is undone by a revert or a\nflag: run Plan's [one fresh challenge](..\u002Fplan\u002Freferences\u002Fchallenge.md) instead\nand return its findings, with no packet, panel, pane manager or model-family\nrule. Duel mode worked when a one-way door returns a packet that the validator\naccepts, with every perspective cross-reviewed and dissent kept, and a two-way\ndoor returns no packet.\n\n## References\n\n- [Idea Genie behavior](references\u002Fidea-genie.feature)\n- [Idea challenge behavior](references\u002Fidea-challenge.feature)\n- [Duel mode workflow](references\u002Fduel-mode.md)\n- [Sealed perspectives](references\u002Fsealed-perspectives.md)\n",{"name":5,"consumes":50,"metadata":54,"produces":64,"practices":66,"context_rel":72,"description":7,"hexagonal_role":78,"user-invocable":79,"output_contract":80,"skill_api_version":81},[51,52,53],"repo-context","task-question","idea-portfolio.v1",{"tier":55,"effects":56,"disposition":58,"capabilities":59,"dependencies":62,"canonical_status":63},"execution",[57],"write_idea_portfolio","keep_strategy",[60,61],"generate_evidenced_options","dueling_idea_genies",[],"canonical",[53,65],"idea-challenge.v1",[67,68,69,70,71],"lean-startup","bdd-gherkin","design-by-contract","llm-eval-harness","adr",[73,76],{"kind":74,"with":75},"customer-of","research",{"kind":77,"with":35},"supplier-to","domain",true,"idea-portfolio.v1 JSON validated by this skill's scripts\u002Fvalidate-output.sh (elicit mode), or idea-challenge.v1 JSON validated by this skill's scripts\u002Fvalidate-challenge.sh (duel mode)",1,"main","347aedf8480cd92b21f761e97b7343a45898f5fa","plugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie",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":93,"prompt":103,"zipAvailable":79},[94,97,100],{"tool":95,"command":96},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill idea-genie",{"tool":98,"command":99},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill idea-genie",{"tool":101,"command":102},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill idea-genie","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002FSKILL.md",[105,111,115,119,123,129],{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fduel-mode.md","REFERENCE","参考文档",4019,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002Freferences\u002Fduel-mode.md",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fidea-challenge.feature",866,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002Freferences\u002Fidea-challenge.feature",{"path":116,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fidea-genie.feature",953,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002Freferences\u002Fidea-genie.feature",{"path":120,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fsealed-perspectives.md",1581,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002Freferences\u002Fsealed-perspectives.md",{"path":124,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":127,"sourceHtmlUrl":128},"scripts\u002Fvalidate-challenge.sh","SCRIPT","脚本",2511,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002Fscripts\u002Fvalidate-challenge.sh",{"path":130,"resourceType":125,"resourceTypeDesc":126,"sizeBytes":131,"sourceHtmlUrl":132},"scripts\u002Fvalidate-output.sh",2138,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fboshu2\u002Fagentops\u002Fskills\u002Fidea-genie\u002Fscripts\u002Fvalidate-output.sh",[134,144,152,160,168,176],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":139,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":143},"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":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":148,"sourceHtmlUrl":149,"categories":150,"keywords":151,"publishedAt":143},"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":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":156,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":143},"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":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":164,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":143},"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":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":143},"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":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":138,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":143},"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",[],[]]