[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JW7M3F5845DNZJ0TQ56K01":3,"skill-same:01M6JW7M3F5845DNZJ0TQ56K01":84},{"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":26,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6JW7M3F5845DNZJ0TQ56K01","fitts-law-pointer-acceleration",null,"Use this skill when the question involves cursor speed, pointer acceleration curves, or interaction with input devices that vary in precision (mouse, trackpad, stylus, touchscreen, eye-tracking). Trigger when designing for varied input devices, building drag interactions, designing scrubbers \u002F sliders \u002F handles, or analyzing why a UI feels \"fiddly.\" Sub-aspect of `fitts-law`; read that first if you haven't already.","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\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-pointer-acceleration\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"fitts law","fitts law pointer acceleration","trigger","curves","when","for","you","with","drag","input","interaction","ui","speed","use","cursor","tracking","read","question","why","first","devices","analyzing","2026-11-10 10:12:30",false,"---\nname: fitts-law-pointer-acceleration\ndescription: 'Use this skill when the question involves cursor speed, pointer acceleration curves, or interaction with input devices that vary in precision (mouse, trackpad, stylus, touchscreen, eye-tracking). Trigger when designing for varied input devices, building drag interactions, designing scrubbers \u002F sliders \u002F handles, or analyzing why a UI feels \"fiddly.\" Sub-aspect of `fitts-law`; read that first if you haven''t already.'\n---\n\n# Fitts's Law and pointer acceleration\n\nThe mouse and trackpad are not \"raw\" inputs — operating systems apply *acceleration curves* that translate physical movement into cursor displacement. Fast physical motion produces disproportionately fast cursor motion; slow physical motion produces precise, slow cursor motion. This curve interacts with Fitts's Law in ways that affect how target size and distance are perceived.\n\n## What pointer acceleration does\n\nA non-accelerated cursor maps physical motion to screen motion 1:1. To cross 1000 pixels, the user must move the mouse 1000 mouse-equivalent units. Fast or slow physical motion makes no difference to the resulting distance.\n\nAn accelerated cursor varies the multiplier based on physical speed:\n\n- **Slow physical motion → low multiplier** (e.g., 0.5×). Used for precise positioning over small targets.\n- **Fast physical motion → high multiplier** (e.g., 3–8×). Used for crossing large screen distances quickly.\n\nThe acceleration curve is what lets a single mouse on a 4K display traverse the full screen without lifting and re-anchoring (a problem 1990s mice without acceleration had).\n\nFor Fitts's Law, this means:\n\n- **Distance is partly free.** Long traversals are accelerated, so movement time grows much less than the linear formula predicts.\n- **Target size still matters.** Once the user is *near* the target, they slow down for fine positioning, and target size dominates again.\n- **Trackpads and mice have different curves.** Same Fitts's task, different time outcomes.\n\n## Implications for UI design\n\n### 1. Distance matters less than naive Fitts's Law suggests on accelerated pointers\n\nA toolbar at the top of a 1440px-wide window vs. one halfway down: the difference in actual cursor travel time is smaller than the geometric distance suggests. Don't sacrifice layout sense to \"place everything close together\" — acceleration absorbs much of the cost.\n\n### 2. Target size matters *more* than naive Fitts's Law suggests near the target\n\nWhen the cursor decelerates for fine positioning, small targets become disproportionately hard. A 16×16 button is much harder than a 24×24 button — more than the 50% size increase would suggest, because deceleration phase amplifies precision cost.\n\nThe takeaway: when in doubt, prefer *bigger* targets to *closer* targets. Acceleration handles distance; nothing handles fine-positioning except size.\n\n### 3. Drag operations are sensitive to acceleration\n\nA drag-and-drop interaction asks the user to move while pressing the button. Acceleration is still active, so a small physical motion can become a large cursor motion. This causes:\n\n- **Overshoot on rapid drags.** The user releases past the target.\n- **Jitter on fine drags.** Slow drags feel \"sticky\" or imprecise as the curve transitions.\n\nMitigations:\n\n- **Provide visible drop zones** that are larger than the dragged item's footprint. The user has slop room.\n- **Snap-to-grid or snap-to-target** for positioning interactions. Reduces precision burden.\n- **Hold-modifier for fine control.** Hold `Shift` (or similar) to disable acceleration during drag. Common in drawing and layout tools.\n\n### 4. Sliders and scrubbers benefit from gain control\n\nA volume slider, a video scrubber, a date-range picker: the user is dragging to a precise value. With raw acceleration, large values are easy to skip past.\n\nPatterns:\n\n- **Variable gain on slider drag.** Drag near the slider track for fast scrubbing; drag away from the track (off-axis) for fine scrubbing. iOS scrubbers use this.\n- **Snap-to-tick** for slider values that should land on integers or other discrete values.\n- **Display the current value during drag** so the user can correct without lifting.\n\n### 5. Different input devices, different curves\n\nThe same web app is used with:\n\n- **Desktop mouse** — moderate acceleration, medium precision.\n- **Trackpad** — high acceleration, lower precision (small physical surface), gestures.\n- **Stylus \u002F pen** — low\u002Fno acceleration, high precision.\n- **Touchscreen** — no acceleration (1:1), but finger contact width adds imprecision.\n- **Eye-tracking** — low precision, no fine positioning, dwell-based selection.\n\nA UI that works on a 27\" monitor with a precise mouse may be unusable with a trackpad on a 13\" laptop. Test both.\n\nFor accessibility:\n\n- **Switch devices** (single-button accessibility input) — every interactive element must be reachable through scanning, not pointer acquisition.\n- **Sip-and-puff and other adaptive devices** — same.\n\n## Worked examples\n\n### Example 1: a slider with click-to-position\n\n```html\n\u003Cinput type=\"range\" min=\"0\" max=\"100\" value=\"50\" \u002F>\n```\n\nNative `\u003Cinput type=\"range\">` works across input devices. The user can click anywhere on the track to jump to that value (no drag required); drag the thumb for fine adjustment; tap arrow keys for precise stepping. All of this is built in.\n\nFor custom sliders:\n\n- **Make the track full-width clickable** (not just the thumb).\n- **Make the thumb hit area ≥ 24×24** (often the visible thumb is smaller, but the hit area extends).\n- **Support arrow keys** for keyboard increment.\n\n### Example 2: a draggable list item\n\n```html\n\u003Cli draggable=\"true\" class=\"task\">\n  \u003Cspan class=\"drag-handle\" aria-label=\"Drag to reorder\">⋮⋮\u003C\u002Fspan>\n  Task name\n\u003C\u002Fli>\n```\n\nThe drag handle is visually small but should have a 32×32+ hit area. During drag:\n\n- Show a visible placeholder where the item will drop (large drop target).\n- Display drop indicators between rows.\n- Provide a keyboard alternative (e.g., arrow keys to reorder) for users who can't drag.\n\n### Example 3: a color picker\n\nA 256×256 color square asks for very fine positioning (each pixel = a different color). Pointer acceleration makes this hard.\n\nMitigations:\n\n- Provide numeric inputs (RGB \u002F HSL \u002F HEX) for users who need precision.\n- Provide preset palette swatches for common selections.\n- Allow `Shift+click` (or another modifier) for fine-position mode.\n\n### Example 4: pinch-and-zoom (touch)\n\nTouch has no acceleration, but two-finger gestures benefit from velocity-aware behavior:\n\n- **Slow pinch** = precise zoom (small zoom factor change per pixel).\n- **Fast pinch** = rapid zoom (larger zoom factor change per pixel).\n\nImplementations: track pinch velocity; multiply zoom delta by a function of velocity.\n\n## Anti-patterns\n\n- **Custom sliders without keyboard support.** A drag-only slider is unusable for keyboard, switch-device, and many assistive-tech users. Always support arrow-key increment.\n- **Tiny drag handles.** A 16×16 drag handle on a list row. The user can't reliably grab it; reordering becomes painful.\n- **Drag-only reordering.** Reordering that requires drag-and-drop with no keyboard alternative. Inaccessible by default.\n- **No snap on positioning.** A drag-to-arrange canvas with no grid, no snap-to-edge, no align-with-neighbor. Every placement requires fine positioning that pointer acceleration sabotages.\n- **Hover-precision interactions.** A hover-only menu where the dropdown is below the trigger and the user must traverse a wedge-shaped path to reach the items. The trackpad user, with high acceleration, overshoots into adjacent menu items. Either use click-to-open or design wider safe traversal areas.\n\n## Heuristics\n\n1. **Test on a trackpad.** If your interaction requires a mouse to be usable, it's broken for ~half your users.\n2. **Test with arrow keys.** Every interactive element should respond meaningfully to keyboard alternatives. (This is also accessibility.)\n3. **The fine-positioning audit.** Walk through every interaction that asks for precision. Is there a coarser alternative (typed value, snap, increment buttons)?\n\n## Related sub-skills\n\n- **`fitts-law`** (parent).\n- **`fitts-law-touch-targets`** — touch has no acceleration but its own precision constraints.\n- **`affordance`** — drag handles need visible affordance.\n- **`accessibility-operable`** (process plugin) — pointer-precision interactions must have non-pointer alternatives.\n- **`mapping`** (cognition) — sliders and scrubbers map control motion to value change; mapping must be intuitive.\n","# Fitts's Law and pointer acceleration\n\nThe mouse and trackpad are not \"raw\" inputs — operating systems apply *acceleration curves* that translate physical movement into cursor displacement. Fast physical motion produces disproportionately fast cursor motion; slow physical motion produces precise, slow cursor motion. This curve interacts with Fitts's Law in ways that affect how target size and distance are perceived.\n\n## What pointer acceleration does\n\nA non-accelerated cursor maps physical motion to screen motion 1:1. To cross 1000 pixels, the user must move the mouse 1000 mouse-equivalent units. Fast or slow physical motion makes no difference to the resulting distance.\n\nAn accelerated cursor varies the multiplier based on physical speed:\n\n- **Slow physical motion → low multiplier** (e.g., 0.5×). Used for precise positioning over small targets.\n- **Fast physical motion → high multiplier** (e.g., 3–8×). Used for crossing large screen distances quickly.\n\nThe acceleration curve is what lets a single mouse on a 4K display traverse the full screen without lifting and re-anchoring (a problem 1990s mice without acceleration had).\n\nFor Fitts's Law, this means:\n\n- **Distance is partly free.** Long traversals are accelerated, so movement time grows much less than the linear formula predicts.\n- **Target size still matters.** Once the user is *near* the target, they slow down for fine positioning, and target size dominates again.\n- **Trackpads and mice have different curves.** Same Fitts's task, different time outcomes.\n\n## Implications for UI design\n\n### 1. Distance matters less than naive Fitts's Law suggests on accelerated pointers\n\nA toolbar at the top of a 1440px-wide window vs. one halfway down: the difference in actual cursor travel time is smaller than the geometric distance suggests. Don't sacrifice layout sense to \"place everything close together\" — acceleration absorbs much of the cost.\n\n### 2. Target size matters *more* than naive Fitts's Law suggests near the target\n\nWhen the cursor decelerates for fine positioning, small targets become disproportionately hard. A 16×16 button is much harder than a 24×24 button — more than the 50% size increase would suggest, because deceleration phase amplifies precision cost.\n\nThe takeaway: when in doubt, prefer *bigger* targets to *closer* targets. Acceleration handles distance; nothing handles fine-positioning except size.\n\n### 3. Drag operations are sensitive to acceleration\n\nA drag-and-drop interaction asks the user to move while pressing the button. Acceleration is still active, so a small physical motion can become a large cursor motion. This causes:\n\n- **Overshoot on rapid drags.** The user releases past the target.\n- **Jitter on fine drags.** Slow drags feel \"sticky\" or imprecise as the curve transitions.\n\nMitigations:\n\n- **Provide visible drop zones** that are larger than the dragged item's footprint. The user has slop room.\n- **Snap-to-grid or snap-to-target** for positioning interactions. Reduces precision burden.\n- **Hold-modifier for fine control.** Hold `Shift` (or similar) to disable acceleration during drag. Common in drawing and layout tools.\n\n### 4. Sliders and scrubbers benefit from gain control\n\nA volume slider, a video scrubber, a date-range picker: the user is dragging to a precise value. With raw acceleration, large values are easy to skip past.\n\nPatterns:\n\n- **Variable gain on slider drag.** Drag near the slider track for fast scrubbing; drag away from the track (off-axis) for fine scrubbing. iOS scrubbers use this.\n- **Snap-to-tick** for slider values that should land on integers or other discrete values.\n- **Display the current value during drag** so the user can correct without lifting.\n\n### 5. Different input devices, different curves\n\nThe same web app is used with:\n\n- **Desktop mouse** — moderate acceleration, medium precision.\n- **Trackpad** — high acceleration, lower precision (small physical surface), gestures.\n- **Stylus \u002F pen** — low\u002Fno acceleration, high precision.\n- **Touchscreen** — no acceleration (1:1), but finger contact width adds imprecision.\n- **Eye-tracking** — low precision, no fine positioning, dwell-based selection.\n\nA UI that works on a 27\" monitor with a precise mouse may be unusable with a trackpad on a 13\" laptop. Test both.\n\nFor accessibility:\n\n- **Switch devices** (single-button accessibility input) — every interactive element must be reachable through scanning, not pointer acquisition.\n- **Sip-and-puff and other adaptive devices** — same.\n\n## Worked examples\n\n### Example 1: a slider with click-to-position\n\n```html\n\u003Cinput type=\"range\" min=\"0\" max=\"100\" value=\"50\" \u002F>\n```\n\nNative `\u003Cinput type=\"range\">` works across input devices. The user can click anywhere on the track to jump to that value (no drag required); drag the thumb for fine adjustment; tap arrow keys for precise stepping. All of this is built in.\n\nFor custom sliders:\n\n- **Make the track full-width clickable** (not just the thumb).\n- **Make the thumb hit area ≥ 24×24** (often the visible thumb is smaller, but the hit area extends).\n- **Support arrow keys** for keyboard increment.\n\n### Example 2: a draggable list item\n\n```html\n\u003Cli draggable=\"true\" class=\"task\">\n  \u003Cspan class=\"drag-handle\" aria-label=\"Drag to reorder\">⋮⋮\u003C\u002Fspan>\n  Task name\n\u003C\u002Fli>\n```\n\nThe drag handle is visually small but should have a 32×32+ hit area. During drag:\n\n- Show a visible placeholder where the item will drop (large drop target).\n- Display drop indicators between rows.\n- Provide a keyboard alternative (e.g., arrow keys to reorder) for users who can't drag.\n\n### Example 3: a color picker\n\nA 256×256 color square asks for very fine positioning (each pixel = a different color). Pointer acceleration makes this hard.\n\nMitigations:\n\n- Provide numeric inputs (RGB \u002F HSL \u002F HEX) for users who need precision.\n- Provide preset palette swatches for common selections.\n- Allow `Shift+click` (or another modifier) for fine-position mode.\n\n### Example 4: pinch-and-zoom (touch)\n\nTouch has no acceleration, but two-finger gestures benefit from velocity-aware behavior:\n\n- **Slow pinch** = precise zoom (small zoom factor change per pixel).\n- **Fast pinch** = rapid zoom (larger zoom factor change per pixel).\n\nImplementations: track pinch velocity; multiply zoom delta by a function of velocity.\n\n## Anti-patterns\n\n- **Custom sliders without keyboard support.** A drag-only slider is unusable for keyboard, switch-device, and many assistive-tech users. Always support arrow-key increment.\n- **Tiny drag handles.** A 16×16 drag handle on a list row. The user can't reliably grab it; reordering becomes painful.\n- **Drag-only reordering.** Reordering that requires drag-and-drop with no keyboard alternative. Inaccessible by default.\n- **No snap on positioning.** A drag-to-arrange canvas with no grid, no snap-to-edge, no align-with-neighbor. Every placement requires fine positioning that pointer acceleration sabotages.\n- **Hover-precision interactions.** A hover-only menu where the dropdown is below the trigger and the user must traverse a wedge-shaped path to reach the items. The trackpad user, with high acceleration, overshoots into adjacent menu items. Either use click-to-open or design wider safe traversal areas.\n\n## Heuristics\n\n1. **Test on a trackpad.** If your interaction requires a mouse to be usable, it's broken for ~half your users.\n2. **Test with arrow keys.** Every interactive element should respond meaningfully to keyboard alternatives. (This is also accessibility.)\n3. **The fine-positioning audit.** Walk through every interaction that asks for precision. Is there a coarser alternative (typed value, snap, increment buttons)?\n\n## Related sub-skills\n\n- **`fitts-law`** (parent).\n- **`fitts-law-touch-targets`** — touch has no acceleration but its own precision constraints.\n- **`affordance`** — drag handles need visible affordance.\n- **`accessibility-operable`** (process plugin) — pointer-precision interactions must have non-pointer alternatives.\n- **`mapping`** (cognition) — sliders and scrubbers map control motion to value change; mapping must be intuitive.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-pointer-acceleration",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fitts-law-pointer-acceleration",{"tool":70,"command":71},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fitts-law-pointer-acceleration",{"tool":73,"command":74},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fitts-law-pointer-acceleration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-pointer-acceleration\u002FSKILL.md",true,[78],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fpointer-mechanics.md","REFERENCE","参考文档",4458,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Finteraction-and-control-principles\u002Fskills\u002Ffitts-law-pointer-acceleration\u002Freferences\u002Fpointer-mechanics.md",[85,95,103,111,119,127],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":94},"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":94},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":94},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":94},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":94},"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":89,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":94},"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",[],[]]