[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVY6JS4AP811T3PZN6DSJN":3,"skill-same:01M6JVY6JS4AP811T3PZN6DSJN":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":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6JVY6JS4AP811T3PZN6DSJN","chunking-form-grouping",null,"Use this skill when designing or fixing long forms that ask the user for many fields — sign-up flows, profile setup, settings panels, checkout, intake forms, applications. Trigger when forms exceed ~6 fields, when users complain forms are \"too long,\" when seeing high mid-form drop-off, or when picking how to break a form into sections. Sub-aspect of `chunking`; 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\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-form-grouping\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"chunking form grouping","grouping","form","chunking","trigger","when","break","for","too long","flows","checkout","how to","panels","intake","drop","forms","up","read","ask","how","applications","2026-11-10 10:12:30",false,"---\nname: chunking-form-grouping\ndescription: 'Use this skill when designing or fixing long forms that ask the user for many fields — sign-up flows, profile setup, settings panels, checkout, intake forms, applications. Trigger when forms exceed ~6 fields, when users complain forms are \"too long,\" when seeing high mid-form drop-off, or when picking how to break a form into sections. Sub-aspect of `chunking`; read that first.'\n---\n\n# Chunking applied to forms\n\nA form with 25 fields in one continuous scroll is a wall. The same 25 fields organized into 4–5 named sections of 5–6 fields each is a list of small tasks. The total content is identical; the perceived complexity drops dramatically.\n\n## When to chunk a form\n\n- The form has more than ~7 fields.\n- Drop-off analytics show users abandoning mid-form.\n- Users describe the form as \"long,\" \"complicated,\" or \"I don't know where I am.\"\n- The fields fall into natural categories (account info, profile info, preferences).\n\nIf the form is short (3–5 fields) or all fields belong to a single concept, chunking adds noise without benefit.\n\n## Section structure\n\nThree patterns for chunked forms:\n\n### Single-page with named sections\n\nAll sections visible on one page; user scrolls through and fills in.\n\n```html\n\u003Cform class=\"long-form\">\n  \u003Csection>\n    \u003Ch2>Account\u003C\u002Fh2>\n    \u003Cp class=\"hint\">How you'll sign in.\u003C\u002Fp>\n    \u003C!-- 4-5 fields -->\n  \u003C\u002Fsection>\n\n  \u003Csection>\n    \u003Ch2>Profile\u003C\u002Fh2>\n    \u003Cp class=\"hint\">How others see you.\u003C\u002Fp>\n    \u003C!-- 4-5 fields -->\n  \u003C\u002Fsection>\n\n  \u003Csection>\n    \u003Ch2>Workspace\u003C\u002Fh2>\n    \u003Cp class=\"hint\">Set up your team space.\u003C\u002Fp>\n    \u003C!-- 4-5 fields -->\n  \u003C\u002Fsection>\n\n  \u003Cbutton>Create account\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nPros: user sees total scope; can fill in any order; one save action.\n\nCons: the scroll can still feel long; mid-form abandonment possible.\n\n### Accordion sections (one open at a time)\n\nSections collapse to headers; user opens one at a time.\n\nPros: less visual mass; user focuses on current chunk.\n\nCons: total scope is hidden; users may not realize how many sections remain.\n\n### Multi-step wizard\n\nEach section is its own page; \"Continue\" advances; \"Back\" returns.\n\nPros: focused attention on one chunk; easier mobile experience.\n\nCons: more clicks; loss of context between steps; back-button management complexity.\n\nThe right pattern depends on form length, mobile context, and whether the user benefits from seeing total scope (probably yes for sign-up; maybe not for long government forms).\n\n## Naming sections\n\nSection names should:\n\n- **Match the user's mental model** — \"Profile\" not \"User Information Subsystem.\"\n- **Suggest what's inside** without requiring the user to open it.\n- **Be parallel** in grammar — all noun phrases, or all verb phrases, not mixed.\n\nBad section names:\n\n- \"Section 1 of 5\" — generic; provides no structure.\n- \"Required Information\" — vague; everything is information.\n- \"Etc.\" — gives up.\n\nGood section names:\n\n- \"Account credentials\"\n- \"Notification preferences\"\n- \"Billing address\"\n\n## Section progress signals\n\nFor long single-page forms, a sticky table-of-contents or progress indicator helps:\n\n```html\n\u003Caside class=\"form-toc\">\n  \u003Col>\n    \u003Cli>\u003Ca href=\"#account\" class=\"done\">Account\u003C\u002Fa>\u003C\u002Fli>\n    \u003Cli>\u003Ca href=\"#profile\" class=\"active\">Profile\u003C\u002Fa>\u003C\u002Fli>\n    \u003Cli>\u003Ca href=\"#workspace\">Workspace\u003C\u002Fa>\u003C\u002Fli>\n  \u003C\u002Fol>\n\u003C\u002Faside>\n```\n\nFor multi-step wizards, a stepper:\n\n```html\n\u003Cnav class=\"stepper\" aria-label=\"Progress\">\n  \u003Col>\n    \u003Cli class=\"done\">1. Account\u003C\u002Fli>\n    \u003Cli class=\"active\">2. Profile\u003C\u002Fli>\n    \u003Cli>3. Workspace\u003C\u002Fli>\n  \u003C\u002Fol>\n\u003C\u002Fnav>\n```\n\nBoth let the user see where they are and how much remains.\n\n## Field count per section\n\nAim for 4–7 fields per section. More than that and the section itself becomes a wall; less and the section overhead exceeds its benefit.\n\nIf you find yourself with 12 fields in one logical section, ask:\n\n- Are all 12 actually required? (Often not; cut.)\n- Can the section split into two? (E.g., \"Personal\" and \"Contact.\")\n- Can some fields move to \"later\" via progressive disclosure?\n\n## Single-page vs. multi-step decision\n\nA useful matrix:\n\n| Length | Mobile-primary | Recommended |\n|---|---|---|\n| ≤ 5 fields | Either | Single page, no sections |\n| 6–15 fields | Desktop | Single page with named sections |\n| 6–15 fields | Mobile | Multi-step or accordion |\n| 16–30 fields | Either | Multi-step wizard |\n| 30+ fields | Either | Multi-step + reconsider scope |\n\nThe question after 30+: do you really need all this data up front? Most products can defer 60% of fields until the user has experienced value.\n\n## Anti-patterns\n\n- **Sections without names.** Visual breaks (a horizontal rule) without headings provide visual chunking but no semantic chunking. The user doesn't know what's in each.\n- **Inconsistent section size.** Five fields, two fields, fourteen fields. The user can't predict what's coming.\n- **Required + optional mixed within sections.** A user finishing what looked like a required field discovers more required fields hidden among optional ones. Worse: discovers there are required fields in a section they thought was optional.\n- **Auto-advance on field change.** A field that automatically moves focus or advances steps when value changes surprises the user.\n- **Save state per section unclear.** Multi-step wizards that don't save state per step can lose user data on navigation.\n\n## Heuristics\n\n1. **The \"name each section in 2–3 words\" test.** If you can't, the chunking isn't meaningful.\n2. **The completion-rate audit.** If sign-up completion drops below ~70% (varies by industry), the form is too long; cut, defer, or chunk better.\n3. **The mobile walkthrough.** Walk the form on a 375px screen. Single-page sections that feel manageable on desktop often feel oppressive on mobile.\n\n## Related sub-skills\n\n- **`chunking`** (parent).\n- **`chunking-numeric-and-otp`** — chunking within field values.\n- **`progressive-disclosure`** — defer optional fields rather than showing them all.\n- **`proximity-form-fields`** (perception) — visual proximity within and between sections.\n- **`hicks-law`** — fewer fields = faster decisions.\n","# Chunking applied to forms\n\nA form with 25 fields in one continuous scroll is a wall. The same 25 fields organized into 4–5 named sections of 5–6 fields each is a list of small tasks. The total content is identical; the perceived complexity drops dramatically.\n\n## When to chunk a form\n\n- The form has more than ~7 fields.\n- Drop-off analytics show users abandoning mid-form.\n- Users describe the form as \"long,\" \"complicated,\" or \"I don't know where I am.\"\n- The fields fall into natural categories (account info, profile info, preferences).\n\nIf the form is short (3–5 fields) or all fields belong to a single concept, chunking adds noise without benefit.\n\n## Section structure\n\nThree patterns for chunked forms:\n\n### Single-page with named sections\n\nAll sections visible on one page; user scrolls through and fills in.\n\n```html\n\u003Cform class=\"long-form\">\n  \u003Csection>\n    \u003Ch2>Account\u003C\u002Fh2>\n    \u003Cp class=\"hint\">How you'll sign in.\u003C\u002Fp>\n    \u003C!-- 4-5 fields -->\n  \u003C\u002Fsection>\n\n  \u003Csection>\n    \u003Ch2>Profile\u003C\u002Fh2>\n    \u003Cp class=\"hint\">How others see you.\u003C\u002Fp>\n    \u003C!-- 4-5 fields -->\n  \u003C\u002Fsection>\n\n  \u003Csection>\n    \u003Ch2>Workspace\u003C\u002Fh2>\n    \u003Cp class=\"hint\">Set up your team space.\u003C\u002Fp>\n    \u003C!-- 4-5 fields -->\n  \u003C\u002Fsection>\n\n  \u003Cbutton>Create account\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nPros: user sees total scope; can fill in any order; one save action.\n\nCons: the scroll can still feel long; mid-form abandonment possible.\n\n### Accordion sections (one open at a time)\n\nSections collapse to headers; user opens one at a time.\n\nPros: less visual mass; user focuses on current chunk.\n\nCons: total scope is hidden; users may not realize how many sections remain.\n\n### Multi-step wizard\n\nEach section is its own page; \"Continue\" advances; \"Back\" returns.\n\nPros: focused attention on one chunk; easier mobile experience.\n\nCons: more clicks; loss of context between steps; back-button management complexity.\n\nThe right pattern depends on form length, mobile context, and whether the user benefits from seeing total scope (probably yes for sign-up; maybe not for long government forms).\n\n## Naming sections\n\nSection names should:\n\n- **Match the user's mental model** — \"Profile\" not \"User Information Subsystem.\"\n- **Suggest what's inside** without requiring the user to open it.\n- **Be parallel** in grammar — all noun phrases, or all verb phrases, not mixed.\n\nBad section names:\n\n- \"Section 1 of 5\" — generic; provides no structure.\n- \"Required Information\" — vague; everything is information.\n- \"Etc.\" — gives up.\n\nGood section names:\n\n- \"Account credentials\"\n- \"Notification preferences\"\n- \"Billing address\"\n\n## Section progress signals\n\nFor long single-page forms, a sticky table-of-contents or progress indicator helps:\n\n```html\n\u003Caside class=\"form-toc\">\n  \u003Col>\n    \u003Cli>\u003Ca href=\"#account\" class=\"done\">Account\u003C\u002Fa>\u003C\u002Fli>\n    \u003Cli>\u003Ca href=\"#profile\" class=\"active\">Profile\u003C\u002Fa>\u003C\u002Fli>\n    \u003Cli>\u003Ca href=\"#workspace\">Workspace\u003C\u002Fa>\u003C\u002Fli>\n  \u003C\u002Fol>\n\u003C\u002Faside>\n```\n\nFor multi-step wizards, a stepper:\n\n```html\n\u003Cnav class=\"stepper\" aria-label=\"Progress\">\n  \u003Col>\n    \u003Cli class=\"done\">1. Account\u003C\u002Fli>\n    \u003Cli class=\"active\">2. Profile\u003C\u002Fli>\n    \u003Cli>3. Workspace\u003C\u002Fli>\n  \u003C\u002Fol>\n\u003C\u002Fnav>\n```\n\nBoth let the user see where they are and how much remains.\n\n## Field count per section\n\nAim for 4–7 fields per section. More than that and the section itself becomes a wall; less and the section overhead exceeds its benefit.\n\nIf you find yourself with 12 fields in one logical section, ask:\n\n- Are all 12 actually required? (Often not; cut.)\n- Can the section split into two? (E.g., \"Personal\" and \"Contact.\")\n- Can some fields move to \"later\" via progressive disclosure?\n\n## Single-page vs. multi-step decision\n\nA useful matrix:\n\n| Length | Mobile-primary | Recommended |\n|---|---|---|\n| ≤ 5 fields | Either | Single page, no sections |\n| 6–15 fields | Desktop | Single page with named sections |\n| 6–15 fields | Mobile | Multi-step or accordion |\n| 16–30 fields | Either | Multi-step wizard |\n| 30+ fields | Either | Multi-step + reconsider scope |\n\nThe question after 30+: do you really need all this data up front? Most products can defer 60% of fields until the user has experienced value.\n\n## Anti-patterns\n\n- **Sections without names.** Visual breaks (a horizontal rule) without headings provide visual chunking but no semantic chunking. The user doesn't know what's in each.\n- **Inconsistent section size.** Five fields, two fields, fourteen fields. The user can't predict what's coming.\n- **Required + optional mixed within sections.** A user finishing what looked like a required field discovers more required fields hidden among optional ones. Worse: discovers there are required fields in a section they thought was optional.\n- **Auto-advance on field change.** A field that automatically moves focus or advances steps when value changes surprises the user.\n- **Save state per section unclear.** Multi-step wizards that don't save state per step can lose user data on navigation.\n\n## Heuristics\n\n1. **The \"name each section in 2–3 words\" test.** If you can't, the chunking isn't meaningful.\n2. **The completion-rate audit.** If sign-up completion drops below ~70% (varies by industry), the form is too long; cut, defer, or chunk better.\n3. **The mobile walkthrough.** Walk the form on a 375px screen. Single-page sections that feel manageable on desktop often feel oppressive on mobile.\n\n## Related sub-skills\n\n- **`chunking`** (parent).\n- **`chunking-numeric-and-otp`** — chunking within field values.\n- **`progressive-disclosure`** — defer optional fields rather than showing them all.\n- **`proximity-form-fields`** (perception) — visual proximity within and between sections.\n- **`hicks-law`** — fewer fields = faster decisions.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-form-grouping",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-form-grouping",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-form-grouping",{"tool":64,"command":65},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-form-grouping","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-form-grouping\u002FSKILL.md",true,[69],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Flong-form-patterns.md","REFERENCE","参考文档",2553,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-form-grouping\u002Freferences\u002Flong-form-patterns.md",[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",[],[]]