[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW2XA9AQXEB1HAHRSZE8NP":3,"skill-same:01M6JW2XA9AQXEB1HAHRSZE8NP":76},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JW2XA9AQXEB1HAHRSZE8NP","wayfinding-physical-spatial-metaphors",null,"Use this skill when deciding whether (and how) to borrow physical-world wayfinding metaphors for software — rooms, doors, paths, maps, landmarks. Trigger when designing app shells with multiple \"spaces,\" when picking metaphors for navigation (workspace, channel, board, project), when reviewing skeuomorphic vs. flat navigation choices, or when the user mentions \"feels like a maze\" or \"where's the front door of this app.\" Sub-aspect of `wayfinding`; 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\u002Fwayfinding-physical-spatial-metaphors\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"wayfinding","wayfinding physical spatial metaphors","Spatial","physical","app","when","for","front","spaces","with","paths","trigger","software","first","project","world","maps","use","read","board","workspace","how","2026-11-10 10:12:30",false,"---\nname: wayfinding-physical-spatial-metaphors\ndescription: 'Use this skill when deciding whether (and how) to borrow physical-world wayfinding metaphors for software — rooms, doors, paths, maps, landmarks. Trigger when designing app shells with multiple \"spaces,\" when picking metaphors for navigation (workspace, channel, board, project), when reviewing skeuomorphic vs. flat navigation choices, or when the user mentions \"feels like a maze\" or \"where''s the front door of this app.\" Sub-aspect of `wayfinding`; read that first.'\n---\n\n# Wayfinding through physical-spatial metaphors\n\nSoftware navigation borrows from physical-world wayfinding all the time — sometimes deliberately, often by accident. \"Folders\" mimic filing cabinets; \"rooms\" and \"channels\" mimic conference rooms; \"boards\" and \"lists\" mimic whiteboards; \"drilling down\" and \"zooming out\" are spatial verbs. Used well, these metaphors give users an instant cognitive map. Used carelessly, they create expectations the software can't meet.\n\n## When physical metaphors help\n\nThe metaphor must satisfy three conditions to be net-positive:\n\n1. **The user already knows the source.** A \"folder\" works because filing cabinets are universal. A \"Kanban board\" works for users who know Kanban; less for those who don't.\n2. **The mapping is consistent.** If your \"rooms\" can be entered, exited, and have walls, then they should *behave* like rooms — opening one closes the other (or layers it visibly), entering signals a context shift, leaving returns to the previous space.\n3. **The user gains something the metaphor uniquely provides.** Spatial metaphors usually provide spatial intuitions: where things are relative to each other, what's nearby, what's deeper.\n\nWhen all three hold, the metaphor offloads cognitive work to the user's existing model.\n\n## When metaphors backfire\n\n- **Mismatch between metaphor and behavior.** A \"Trash\" that empties itself silently every 30 days is not a trash — physical trash sits there until you take it out. The metaphor implies one behavior, the system does another, and trust degrades.\n- **Forced metaphors that don't fit.** Apple's mid-2000s reach for skeuomorphism (leather-bound calendars, felt-textured Game Center) borrowed metaphors that added no informational value and aged poorly.\n- **Cross-cultural assumptions.** A \"front porch\" or \"lobby\" metaphor presumes architectural conventions that don't translate universally.\n- **Mixing incompatible metaphors.** \"Drag this folder into the room you want to share it with\" combines a filing-cabinet verb with a building-room metaphor; it works only if the user squints.\n\n## Useful spatial metaphors in modern software\n\n### Rooms \u002F Channels \u002F Spaces\n\nSlack channels, Discord servers, Notion workspaces, Microsoft Teams. The metaphor: a named container with members and a context. Each room has its own conversations and norms.\n\nWayfinding implications:\n- Switching rooms feels like changing context (visual transition; current-room highlighted).\n- Entering a room you've never visited shouldn't feel arbitrary — recent activity, who's there, what's pinned should orient you.\n- A \"lobby\" or \"general\" channel acts as the entry-room equivalent.\n\n### Boards \u002F Lanes \u002F Cards\n\nTrello, Linear, Asana boards. The metaphor: a flat surface (board) with regions (lanes\u002Fcolumns) and movable items (cards). Maps to whiteboards, post-it walls, kanban systems.\n\nWayfinding implications:\n- The whole board is visible at once — no drilling down required for the primary view.\n- Cards have positions; moving them carries meaning.\n- Zooming out to see \"all boards\" requires a different metaphor (a folder of boards, a workspace).\n\n### Folders \u002F Trees \u002F Hierarchies\n\nThe original spatial metaphor: file systems. Folders within folders within folders.\n\nWayfinding implications:\n- Depth reads as \"deeper into\" — backwards\u002Fup is the universal escape.\n- Tree views show siblings and parents simultaneously; flat folder views show only contents (the file manager pattern).\n- Breadcrumbs make hierarchy navigable without committing to a tree view.\n\nThe trap: deep hierarchies are easier to *create* than to *navigate*. Wayfinding research consistently finds that 4+ levels of depth become frustrating; users prefer broader, shallower structures.\n\n### Maps and Canvases\n\nFigma, Miro, FigJam. The metaphor: an infinite 2D plane that the user pans and zooms across.\n\nWayfinding implications:\n- Position carries meaning; spatial proximity is grouping.\n- Mini-maps and zoom-to-fit are wayfinding tools borrowed directly from physical maps.\n- Without these tools, users get lost on infinite canvases (\"where's the design I made yesterday?\").\n\n### Stacks \u002F Decks \u002F Stories\n\nCard-stack metaphors (Stories on Instagram, swipeable decks). The metaphor: a stack of cards consumed sequentially.\n\nWayfinding implications:\n- Position-in-sequence is the orientation (3 of 7).\n- Forward\u002Fback are the only navigation verbs; usually no \"jump to\" without breaking the metaphor.\n- Works well for short sequences; fails for long ones (no random access).\n\n## Cross-domain examples\n\n### Museum and gallery wayfinding\n\nMuseums have used spatial metaphors for centuries: rooms grouped by period, by region, by artist. Visitors orient by which \"room\" they're in. Modern museum apps mirror this — the audio tour app shows you which room corresponds to your current location, and tapping a room reveals its contents.\n\nThe lesson: when the physical space is well-organized, the digital equivalent inherits that organization for free.\n\n### City vs. suburban wayfinding\n\nCities organized on grids (Manhattan, parts of Tokyo) are easier to wayfind than organic-grown cities (Boston, Lisbon, much of London). Grid metaphors translate to software well: a settings page laid out as a grid of categories (Profile, Notifications, Security, Billing) is easier to navigate than one organized by some idiosyncratic logic.\n\nWhen your IA naturally has a grid-like structure, expose it. When it has an organic structure, lean into landmarks.\n\n### \"Skeuomorphism revisited\"\n\nThe flat-design movement (post-2013) rejected literal skeuomorphism (leather-bound calendars, felt poker tables). What survived: *spatial intuitions* without literal visual mimicry. Sliding panels still feel like opening drawers; cards still feel like tangible objects. The visual style went flat; the spatial metaphors stayed.\n\nThe current trend (post-2020) is \"neo-skeuomorphism\" — subtle depth cues, careful shadows, motion that respects spatial logic. The principle: borrow the *physics*, not the *textures*.\n\n## Anti-patterns\n\n- **Inventing metaphors no user has ever encountered.** \"Rendezvous Spaces\" or \"Wisdom Pods\" sound clever in design reviews and confuse everyone in production.\n- **Treating containers as both folders and tags.** A folder is exclusive (a file lives in one folder); a tag is inclusive (a file can have many tags). Hybrid systems where a \"folder\" can also be applied as a tag confuse users.\n- **The infinite map without a home.** Infinite-canvas tools without a \"go to my home\" or \"fit to content\" are wayfinding deserts.\n- **Animation that contradicts the spatial metaphor.** Closing a sheet and having it shrink to a corner unrelated to where it opened from breaks the spatial intuition.\n\n## Heuristics\n\n1. **Name the metaphor explicitly.** \"We're treating these as rooms — that means entering signals a context shift, exiting returns to where you were.\" Once named, the team can audit consistency.\n2. **The \"what would the physical version do?\" check.** When in doubt about a behavior, ask: what would the physical-world equivalent do? Does the software match?\n3. **The new-user metaphor test.** Onboard a new user without explaining your metaphors. If they intuit \"channel,\" \"board,\" \"folder\" correctly, the metaphor is doing its work. If they ask \"what's a Space?\", the metaphor is too clever.\n\n## Related sub-skills\n\n- **`wayfinding`** (parent) — the principle and four-stage framework.\n- **`wayfinding-search-and-recovery`** — when spatial metaphors fail, search recovers.\n- **`wayfinding-breadcrumbs-and-context`** — making the \"where am I\" answer load-bearing.\n- **`mental-model`** — physical metaphors work because they leverage existing mental models.\n- **`mimicry`** — the broader principle of borrowing successful patterns.\n","# Wayfinding through physical-spatial metaphors\n\nSoftware navigation borrows from physical-world wayfinding all the time — sometimes deliberately, often by accident. \"Folders\" mimic filing cabinets; \"rooms\" and \"channels\" mimic conference rooms; \"boards\" and \"lists\" mimic whiteboards; \"drilling down\" and \"zooming out\" are spatial verbs. Used well, these metaphors give users an instant cognitive map. Used carelessly, they create expectations the software can't meet.\n\n## When physical metaphors help\n\nThe metaphor must satisfy three conditions to be net-positive:\n\n1. **The user already knows the source.** A \"folder\" works because filing cabinets are universal. A \"Kanban board\" works for users who know Kanban; less for those who don't.\n2. **The mapping is consistent.** If your \"rooms\" can be entered, exited, and have walls, then they should *behave* like rooms — opening one closes the other (or layers it visibly), entering signals a context shift, leaving returns to the previous space.\n3. **The user gains something the metaphor uniquely provides.** Spatial metaphors usually provide spatial intuitions: where things are relative to each other, what's nearby, what's deeper.\n\nWhen all three hold, the metaphor offloads cognitive work to the user's existing model.\n\n## When metaphors backfire\n\n- **Mismatch between metaphor and behavior.** A \"Trash\" that empties itself silently every 30 days is not a trash — physical trash sits there until you take it out. The metaphor implies one behavior, the system does another, and trust degrades.\n- **Forced metaphors that don't fit.** Apple's mid-2000s reach for skeuomorphism (leather-bound calendars, felt-textured Game Center) borrowed metaphors that added no informational value and aged poorly.\n- **Cross-cultural assumptions.** A \"front porch\" or \"lobby\" metaphor presumes architectural conventions that don't translate universally.\n- **Mixing incompatible metaphors.** \"Drag this folder into the room you want to share it with\" combines a filing-cabinet verb with a building-room metaphor; it works only if the user squints.\n\n## Useful spatial metaphors in modern software\n\n### Rooms \u002F Channels \u002F Spaces\n\nSlack channels, Discord servers, Notion workspaces, Microsoft Teams. The metaphor: a named container with members and a context. Each room has its own conversations and norms.\n\nWayfinding implications:\n- Switching rooms feels like changing context (visual transition; current-room highlighted).\n- Entering a room you've never visited shouldn't feel arbitrary — recent activity, who's there, what's pinned should orient you.\n- A \"lobby\" or \"general\" channel acts as the entry-room equivalent.\n\n### Boards \u002F Lanes \u002F Cards\n\nTrello, Linear, Asana boards. The metaphor: a flat surface (board) with regions (lanes\u002Fcolumns) and movable items (cards). Maps to whiteboards, post-it walls, kanban systems.\n\nWayfinding implications:\n- The whole board is visible at once — no drilling down required for the primary view.\n- Cards have positions; moving them carries meaning.\n- Zooming out to see \"all boards\" requires a different metaphor (a folder of boards, a workspace).\n\n### Folders \u002F Trees \u002F Hierarchies\n\nThe original spatial metaphor: file systems. Folders within folders within folders.\n\nWayfinding implications:\n- Depth reads as \"deeper into\" — backwards\u002Fup is the universal escape.\n- Tree views show siblings and parents simultaneously; flat folder views show only contents (the file manager pattern).\n- Breadcrumbs make hierarchy navigable without committing to a tree view.\n\nThe trap: deep hierarchies are easier to *create* than to *navigate*. Wayfinding research consistently finds that 4+ levels of depth become frustrating; users prefer broader, shallower structures.\n\n### Maps and Canvases\n\nFigma, Miro, FigJam. The metaphor: an infinite 2D plane that the user pans and zooms across.\n\nWayfinding implications:\n- Position carries meaning; spatial proximity is grouping.\n- Mini-maps and zoom-to-fit are wayfinding tools borrowed directly from physical maps.\n- Without these tools, users get lost on infinite canvases (\"where's the design I made yesterday?\").\n\n### Stacks \u002F Decks \u002F Stories\n\nCard-stack metaphors (Stories on Instagram, swipeable decks). The metaphor: a stack of cards consumed sequentially.\n\nWayfinding implications:\n- Position-in-sequence is the orientation (3 of 7).\n- Forward\u002Fback are the only navigation verbs; usually no \"jump to\" without breaking the metaphor.\n- Works well for short sequences; fails for long ones (no random access).\n\n## Cross-domain examples\n\n### Museum and gallery wayfinding\n\nMuseums have used spatial metaphors for centuries: rooms grouped by period, by region, by artist. Visitors orient by which \"room\" they're in. Modern museum apps mirror this — the audio tour app shows you which room corresponds to your current location, and tapping a room reveals its contents.\n\nThe lesson: when the physical space is well-organized, the digital equivalent inherits that organization for free.\n\n### City vs. suburban wayfinding\n\nCities organized on grids (Manhattan, parts of Tokyo) are easier to wayfind than organic-grown cities (Boston, Lisbon, much of London). Grid metaphors translate to software well: a settings page laid out as a grid of categories (Profile, Notifications, Security, Billing) is easier to navigate than one organized by some idiosyncratic logic.\n\nWhen your IA naturally has a grid-like structure, expose it. When it has an organic structure, lean into landmarks.\n\n### \"Skeuomorphism revisited\"\n\nThe flat-design movement (post-2013) rejected literal skeuomorphism (leather-bound calendars, felt poker tables). What survived: *spatial intuitions* without literal visual mimicry. Sliding panels still feel like opening drawers; cards still feel like tangible objects. The visual style went flat; the spatial metaphors stayed.\n\nThe current trend (post-2020) is \"neo-skeuomorphism\" — subtle depth cues, careful shadows, motion that respects spatial logic. The principle: borrow the *physics*, not the *textures*.\n\n## Anti-patterns\n\n- **Inventing metaphors no user has ever encountered.** \"Rendezvous Spaces\" or \"Wisdom Pods\" sound clever in design reviews and confuse everyone in production.\n- **Treating containers as both folders and tags.** A folder is exclusive (a file lives in one folder); a tag is inclusive (a file can have many tags). Hybrid systems where a \"folder\" can also be applied as a tag confuse users.\n- **The infinite map without a home.** Infinite-canvas tools without a \"go to my home\" or \"fit to content\" are wayfinding deserts.\n- **Animation that contradicts the spatial metaphor.** Closing a sheet and having it shrink to a corner unrelated to where it opened from breaks the spatial intuition.\n\n## Heuristics\n\n1. **Name the metaphor explicitly.** \"We're treating these as rooms — that means entering signals a context shift, exiting returns to where you were.\" Once named, the team can audit consistency.\n2. **The \"what would the physical version do?\" check.** When in doubt about a behavior, ask: what would the physical-world equivalent do? Does the software match?\n3. **The new-user metaphor test.** Onboard a new user without explaining your metaphors. If they intuit \"channel,\" \"board,\" \"folder\" correctly, the metaphor is doing its work. If they ask \"what's a Space?\", the metaphor is too clever.\n\n## Related sub-skills\n\n- **`wayfinding`** (parent) — the principle and four-stage framework.\n- **`wayfinding-search-and-recovery`** — when spatial metaphors fail, search recovers.\n- **`wayfinding-breadcrumbs-and-context`** — making the \"where am I\" answer load-bearing.\n- **`mental-model`** — physical metaphors work because they leverage existing mental models.\n- **`mimicry`** — the broader principle of borrowing successful patterns.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fwayfinding-physical-spatial-metaphors",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wayfinding-physical-spatial-metaphors",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wayfinding-physical-spatial-metaphors",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill wayfinding-physical-spatial-metaphors","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fwayfinding-physical-spatial-metaphors\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fmetaphor-cases.md","REFERENCE","参考文档",6792,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fwayfinding-physical-spatial-metaphors\u002Freferences\u002Fmetaphor-cases.md",[77,87,95,103,111,119],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":86},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":86},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":86},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":86},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":86},"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",[],[]]