[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWJXFCNTQFRPDNAQ9AQVYC":3,"skill-same:01M6JWJXFCNTQFRPDNAQ9AQVYC":85},{"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":28,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M6JWJXFCNTQFRPDNAQ9AQVYC","iteration-prototype-fidelity",null,"Use this skill when picking the appropriate prototype fidelity for an iteration cycle — sketches vs. wireframes vs. clickable Figma vs. code prototypes vs. production beta. Trigger when planning a research session, when a project is over- or under-investing in prototypes, or when the prototype fidelity is mismatched to the question being asked. Sub-aspect of `iteration`; read that first.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Fiteration-prototype-fidelity\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"prototype","iteration prototype fidelity","iteration","when","mismatched","for","trigger","wireframes","project","investing","cycle","use","session","read","question","first","beta","figma","planning","code","research","2026-11-10 10:12:30",false,"---\nname: iteration-prototype-fidelity\ndescription: 'Use this skill when picking the appropriate prototype fidelity for an iteration cycle — sketches vs. wireframes vs. clickable Figma vs. code prototypes vs. production beta. Trigger when planning a research session, when a project is over- or under-investing in prototypes, or when the prototype fidelity is mismatched to the question being asked. Sub-aspect of `iteration`; read that first.'\n---\n\n# Picking the right prototype fidelity\n\nEach prototype fidelity is a tool with a cost and a use. Sketches are nearly free but answer only structural questions. Code prototypes cost more but answer performance and behavior questions. The discipline is matching fidelity to the question being asked — not always going lowest, not always going highest.\n\n## The fidelity ladder\n\nFrom cheapest to most expensive:\n\n### 1. Paper sketches\n\nA pen and paper. Cost: 5–30 minutes per option. Answers:\n\n- Does this layout structure make sense?\n- Are the right elements present?\n- What's the rough information architecture?\n\nDoesn't answer:\n\n- How does it feel to interact with this?\n- Does the typography work?\n- Are colors right?\n\nWhen to stop here: structural questions only; very early discovery.\n\n### 2. Wireframes (low-fidelity digital)\n\nBoxy, monochrome, no real content. Cost: 1–4 hours per screen. Answers:\n\n- Layout proportions on screen.\n- Reading order and hierarchy.\n- Information grouping.\n\nDoesn't answer:\n\n- Visual style.\n- Interaction feel.\n- Real-content edge cases.\n\nWhen to stop here: when structure is the question; before visual design begins.\n\n### 3. Mockups (high-fidelity static)\n\nReal fonts, colors, content; static image. Cost: 4–16 hours per screen. Answers:\n\n- Visual style.\n- Polish and brand fit.\n- Stakeholder alignment (\"does this look right?\").\n\nDoesn't answer:\n\n- Interaction.\n- Edge cases.\n- Performance.\n\nCommon misuse: building high-fidelity mockups before structure is settled. The mockups become anchors that prevent structural changes.\n\n### 4. Clickable prototypes (Figma, Framer, ProtoPie)\n\nMockups linked together with click-throughs. Cost: 1–3 days per major flow. Answers:\n\n- Does the interaction sequence make sense?\n- Where do users get confused?\n- Are the affordances clear?\n\nDoesn't answer:\n\n- Real-content edge cases.\n- Performance.\n- Cross-device behavior.\n\nSweet spot for most user research; cheap enough to revise, real enough to test.\n\n### 5. Code prototypes\n\nWorking code with real or seeded data, but not production-ready. Cost: 1–3 weeks. Answers:\n\n- Performance.\n- Cross-device behavior.\n- Real-data edge cases.\n- Implementation complexity.\n\nDoesn't answer:\n\n- Long-term scale issues.\n- Production reliability.\n\nUseful when implementation has unknowns or when performance is a concern.\n\n### 6. Production beta\n\nShipped to a small percentage of real users. Cost: high (full implementation). Answers:\n\n- Real usage at scale.\n- Bug rates.\n- Long-term retention.\n- Real edge cases.\n\nDoesn't answer (well):\n\n- Counterfactual: would users have liked the alternative more?\n\nWhen to use: late-stage validation; gradual rollout.\n\n## Picking the right fidelity for each question\n\nA useful rule: pick the **cheapest fidelity that answers the question**.\n\n| Question | Recommended fidelity |\n|---|---|\n| Does the IA make sense? | Sketches or wireframes |\n| Is the visual style right? | High-fidelity mockup |\n| Does the flow work for users? | Clickable prototype + 5 interviews |\n| Will the load time be acceptable? | Code prototype with seeded data |\n| Will users adopt it? | Production beta with measurement |\n\nGoing higher than needed wastes time. Going lower means you don't get the answer.\n\n## When to stay low fidelity longer\n\nCounterintuitively, low fidelity is often better for user research:\n\n- **Users critique the prototype's polish, not its structure.** A high-fidelity mockup gets feedback like \"I don't love this blue\" instead of \"I don't understand what this page is for.\" The polish distracts.\n- **Low fidelity invites criticism.** Users feel comfortable suggesting changes to a sketch; they hesitate to challenge a polished mockup.\n- **Low fidelity is faster to revise.** You can make 5 sketch variations in the time it takes to make 1 mockup variation.\n\nFor early-stage user research, sketches and wireframes often outperform high-fidelity prototypes despite \"feeling unprofessional.\"\n\n## When to go high fidelity earlier\n\nA few cases where polish matters:\n\n- **Stakeholder buy-in.** Some stakeholders only react meaningfully to high-fidelity mockups. Build them for those reviews.\n- **Brand-perception research.** Testing whether a design feels like the brand requires polish.\n- **Competitive comparison.** Comparing your design's appeal to a competitor's polished product needs comparable polish.\n\n## Anti-patterns\n\n- **Pixel-perfect early.** Polishing visual details before structure is settled. The pixels then have to be redone.\n- **Test with the prototype that was easy to build.** Using a Figma prototype to test load-time performance, or a code prototype to test layout structure. Wrong fidelity for the question.\n- **Skip prototyping entirely.** \"We're agile, we'll just build it.\" Then iterate expensively in production.\n- **Production-quality prototypes.** Building prototypes to production code quality. Defeats the cost advantage of prototyping.\n- **Treating prototypes as products.** Shipping a prototype as the product because it \"works.\" Usually missing edge cases, accessibility, performance.\n\n## Worked example: layered prototyping for a new feature\n\nA team designs a new collaboration feature.\n\n- **Week 1**: paper sketches; internal review. Decide structural concept.\n- **Week 2**: wireframes; design crit. Refine information architecture.\n- **Week 3**: clickable Figma prototype; 5 user interviews. Discover one critical flow is confusing; redesign.\n- **Week 4**: refined Figma prototype; 5 more interviews. Confirm the redesign works.\n- **Week 5–6**: code prototype with real data. Surface a performance issue; design adapts.\n- **Week 7–10**: production build. Ship to 10% beta.\n- **Week 11–12**: full release.\n\nEach cycle uses the cheapest fidelity that answers the cycle's question.\n\n## Heuristics\n\n1. **The \"what question is this prototype answering?\" check.** Before building the prototype, name the question. Pick the fidelity that answers it.\n2. **The \"could a sketch have caught this?\" retrospective.** When issues are discovered late, ask whether earlier prototyping at lower fidelity would have caught them.\n3. **The user-reaction signal.** If users critique your prototype's visual polish, you're at too high fidelity for the question. Drop down.\n\n## Related sub-skills\n\n- **`iteration`** (parent).\n- **`iteration-design-vs-development`** — moving up the fidelity ladder is part of moving from design to development.\n- **`prototyping`** — the broader technique.\n- **`factor-of-safety`** — prototypes are a form of designing-with-margin.\n","# Picking the right prototype fidelity\n\nEach prototype fidelity is a tool with a cost and a use. Sketches are nearly free but answer only structural questions. Code prototypes cost more but answer performance and behavior questions. The discipline is matching fidelity to the question being asked — not always going lowest, not always going highest.\n\n## The fidelity ladder\n\nFrom cheapest to most expensive:\n\n### 1. Paper sketches\n\nA pen and paper. Cost: 5–30 minutes per option. Answers:\n\n- Does this layout structure make sense?\n- Are the right elements present?\n- What's the rough information architecture?\n\nDoesn't answer:\n\n- How does it feel to interact with this?\n- Does the typography work?\n- Are colors right?\n\nWhen to stop here: structural questions only; very early discovery.\n\n### 2. Wireframes (low-fidelity digital)\n\nBoxy, monochrome, no real content. Cost: 1–4 hours per screen. Answers:\n\n- Layout proportions on screen.\n- Reading order and hierarchy.\n- Information grouping.\n\nDoesn't answer:\n\n- Visual style.\n- Interaction feel.\n- Real-content edge cases.\n\nWhen to stop here: when structure is the question; before visual design begins.\n\n### 3. Mockups (high-fidelity static)\n\nReal fonts, colors, content; static image. Cost: 4–16 hours per screen. Answers:\n\n- Visual style.\n- Polish and brand fit.\n- Stakeholder alignment (\"does this look right?\").\n\nDoesn't answer:\n\n- Interaction.\n- Edge cases.\n- Performance.\n\nCommon misuse: building high-fidelity mockups before structure is settled. The mockups become anchors that prevent structural changes.\n\n### 4. Clickable prototypes (Figma, Framer, ProtoPie)\n\nMockups linked together with click-throughs. Cost: 1–3 days per major flow. Answers:\n\n- Does the interaction sequence make sense?\n- Where do users get confused?\n- Are the affordances clear?\n\nDoesn't answer:\n\n- Real-content edge cases.\n- Performance.\n- Cross-device behavior.\n\nSweet spot for most user research; cheap enough to revise, real enough to test.\n\n### 5. Code prototypes\n\nWorking code with real or seeded data, but not production-ready. Cost: 1–3 weeks. Answers:\n\n- Performance.\n- Cross-device behavior.\n- Real-data edge cases.\n- Implementation complexity.\n\nDoesn't answer:\n\n- Long-term scale issues.\n- Production reliability.\n\nUseful when implementation has unknowns or when performance is a concern.\n\n### 6. Production beta\n\nShipped to a small percentage of real users. Cost: high (full implementation). Answers:\n\n- Real usage at scale.\n- Bug rates.\n- Long-term retention.\n- Real edge cases.\n\nDoesn't answer (well):\n\n- Counterfactual: would users have liked the alternative more?\n\nWhen to use: late-stage validation; gradual rollout.\n\n## Picking the right fidelity for each question\n\nA useful rule: pick the **cheapest fidelity that answers the question**.\n\n| Question | Recommended fidelity |\n|---|---|\n| Does the IA make sense? | Sketches or wireframes |\n| Is the visual style right? | High-fidelity mockup |\n| Does the flow work for users? | Clickable prototype + 5 interviews |\n| Will the load time be acceptable? | Code prototype with seeded data |\n| Will users adopt it? | Production beta with measurement |\n\nGoing higher than needed wastes time. Going lower means you don't get the answer.\n\n## When to stay low fidelity longer\n\nCounterintuitively, low fidelity is often better for user research:\n\n- **Users critique the prototype's polish, not its structure.** A high-fidelity mockup gets feedback like \"I don't love this blue\" instead of \"I don't understand what this page is for.\" The polish distracts.\n- **Low fidelity invites criticism.** Users feel comfortable suggesting changes to a sketch; they hesitate to challenge a polished mockup.\n- **Low fidelity is faster to revise.** You can make 5 sketch variations in the time it takes to make 1 mockup variation.\n\nFor early-stage user research, sketches and wireframes often outperform high-fidelity prototypes despite \"feeling unprofessional.\"\n\n## When to go high fidelity earlier\n\nA few cases where polish matters:\n\n- **Stakeholder buy-in.** Some stakeholders only react meaningfully to high-fidelity mockups. Build them for those reviews.\n- **Brand-perception research.** Testing whether a design feels like the brand requires polish.\n- **Competitive comparison.** Comparing your design's appeal to a competitor's polished product needs comparable polish.\n\n## Anti-patterns\n\n- **Pixel-perfect early.** Polishing visual details before structure is settled. The pixels then have to be redone.\n- **Test with the prototype that was easy to build.** Using a Figma prototype to test load-time performance, or a code prototype to test layout structure. Wrong fidelity for the question.\n- **Skip prototyping entirely.** \"We're agile, we'll just build it.\" Then iterate expensively in production.\n- **Production-quality prototypes.** Building prototypes to production code quality. Defeats the cost advantage of prototyping.\n- **Treating prototypes as products.** Shipping a prototype as the product because it \"works.\" Usually missing edge cases, accessibility, performance.\n\n## Worked example: layered prototyping for a new feature\n\nA team designs a new collaboration feature.\n\n- **Week 1**: paper sketches; internal review. Decide structural concept.\n- **Week 2**: wireframes; design crit. Refine information architecture.\n- **Week 3**: clickable Figma prototype; 5 user interviews. Discover one critical flow is confusing; redesign.\n- **Week 4**: refined Figma prototype; 5 more interviews. Confirm the redesign works.\n- **Week 5–6**: code prototype with real data. Surface a performance issue; design adapts.\n- **Week 7–10**: production build. Ship to 10% beta.\n- **Week 11–12**: full release.\n\nEach cycle uses the cheapest fidelity that answers the cycle's question.\n\n## Heuristics\n\n1. **The \"what question is this prototype answering?\" check.** Before building the prototype, name the question. Pick the fidelity that answers it.\n2. **The \"could a sketch have caught this?\" retrospective.** When issues are discovered late, ask whether earlier prototyping at lower fidelity would have caught them.\n3. **The user-reaction signal.** If users critique your prototype's visual polish, you're at too high fidelity for the question. Drop down.\n\n## Related sub-skills\n\n- **`iteration`** (parent).\n- **`iteration-design-vs-development`** — moving up the fidelity ladder is part of moving from design to development.\n- **`prototyping`** — the broader technique.\n- **`factor-of-safety`** — prototypes are a form of designing-with-margin.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Fiteration-prototype-fidelity",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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill iteration-prototype-fidelity",{"tool":71,"command":72},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill iteration-prototype-fidelity",{"tool":74,"command":75},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill iteration-prototype-fidelity","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Fiteration-prototype-fidelity\u002FSKILL.md",true,[79],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fprototyping-tools-and-research.md","REFERENCE","参考文档",3627,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Fiteration-prototype-fidelity\u002Freferences\u002Fprototyping-tools-and-research.md",[86,96,104,112,120,128],{"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":90,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":95},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":95},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":95},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":95},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":124,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":95},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":90,"licenseFileUrl":132,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":95},"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",[],[]]