[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JVYB0ARY6AVH4TSDTYCF0E":3,"skill-same:01M6JVYB0ARY6AVH4TSDTYCF0E":79},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6JVYB0ARY6AVH4TSDTYCF0E","chunking-numeric-and-otp",null,"Use this skill when designing inputs or displays for numeric strings — phone numbers, OTP \u002F verification codes, credit card numbers, account IDs, license keys, currency, dates, social security numbers. Trigger when picking a format for displaying numbers, designing OTP entry UIs, or formatting identifiers in tables and receipts. 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-numeric-and-otp\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"chunking numeric and otp","otp","chunking","formatting","when","dates","for","keys","strings","tables","codes","card","trigger","currency","security","social","phone","use","read","format","receipts","first","ids","license","verification","2026-11-10 10:12:30",false,"---\nname: chunking-numeric-and-otp\ndescription: 'Use this skill when designing inputs or displays for numeric strings — phone numbers, OTP \u002F verification codes, credit card numbers, account IDs, license keys, currency, dates, social security numbers. Trigger when picking a format for displaying numbers, designing OTP entry UIs, or formatting identifiers in tables and receipts. Sub-aspect of `chunking`; read that first.'\n---\n\n# Chunking applied to numeric strings\n\nNumbers are the canonical chunking case. A 10-digit phone number, a 16-digit credit card, a 6-digit OTP — without chunking, these are working-memory overloads. With chunking, they're manageable.\n\n## Standard chunkings\n\nConventions that have evolved across industries:\n\n| Type | Standard chunking | Example |\n|---|---|---|\n| US phone | 3-3-4 | 555-867-5309 |\n| International phone | varies; usually 2-3-3-2 or similar | +44 20 7946 0958 |\n| Credit card | 4-4-4-4 (most) or 4-6-5 (Amex) | 4242 4242 4242 4242 |\n| Social Security (US) | 3-2-4 | 123-45-6789 |\n| OTP \u002F verification | 3-3 (6-digit) or 4-4 (8-digit) | 123-456 |\n| Bank account (US) | varies; often grouped with type | 110000000 → routing display |\n| ISBN | 1-3-3-5-1 (ISBN-13) | 978-3-16-148410-0 |\n| IP address | 4 octets separated by dots | 192.168.1.1 |\n| Date (ISO) | 4-2-2 | 2026-05-02 |\n| Currency | 3-digit groups | $1,234,567.89 |\n\nWhen in doubt, follow the convention. Users have already learned it.\n\n## OTP \u002F verification code entry\n\nThe most common modern chunking case in product UI. A 6-digit code from email or SMS, entered into a verification field.\n\n### Single field vs. chunked fields\n\nSingle field:\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"6\" pattern=\"\\d{6}\" \u002F>\n```\n\nChunked fields (one per digit):\n```html\n\u003Cdiv class=\"otp-input\" role=\"group\" aria-label=\"Verification code\">\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" autocomplete=\"one-time-code\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cspan class=\"separator\" aria-hidden>—\u003C\u002Fspan>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n\u003C\u002Fdiv>\n```\n\nThe chunked version:\n\n- Visually matches how the code is presented in email\u002FSMS.\n- Lets the user verify each digit's position mid-entry.\n- Auto-advances focus on each digit (with JS).\n- Supports paste-spread (paste into first input fills all).\n\nThe single-field version is simpler to implement and supports SMS-autofill on iOS via `autocomplete=\"one-time-code\"`. Modern apps often offer both: a single field on mobile (where autofill is critical) and chunked on desktop.\n\n### OTP UX details\n\n- **Auto-advance** focus to the next digit on input.\n- **Auto-back** focus to previous digit on backspace.\n- **Paste support**: pasting a 6-digit string into the first input should distribute across all six.\n- **`autocomplete=\"one-time-code\"`** on at least one input enables iOS Messages autofill.\n- **Numeric keyboard on mobile** via `inputmode=\"numeric\"`.\n- **Optional auto-submit** when the last digit is entered (debate: some users dislike auto-submit because it commits before they can verify).\n\n## Phone number entry\n\nPhone numbers vary widely by country. Patterns:\n\n- **US-only forms**: enforce 3-3-4 with format mask or chunked inputs.\n- **International forms**: use a country selector + a free-text number field; format on display rather than enforcing entry format.\n- **Dual-purpose** (international users + US-heavy): use [libphonenumber](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Flibphonenumber) or similar to validate and format dynamically.\n\n```html\n\u003Clabel>\n  Phone\n  \u003Cdiv class=\"phone-input\">\n    \u003Cselect name=\"country-code\">\n      \u003Coption value=\"+1\">?? +1\u003C\u002Foption>\n      \u003Coption value=\"+44\">?? +44\u003C\u002Foption>\n      \u003C!-- ... -->\n    \u003C\u002Fselect>\n    \u003Cinput type=\"tel\" name=\"phone\" placeholder=\"555-867-5309\" \u002F>\n  \u003C\u002Fdiv>\n\u003C\u002Flabel>\n```\n\n## Credit card display\n\nIn production, never display full card numbers — show the last 4 digits chunked with masking:\n\n```\n**** **** **** 4242\n```\n\nFor entry, use 4-4-4-4 chunking with auto-advance, paste support, and card-type detection:\n\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" autocomplete=\"cc-number\"\n       placeholder=\"1234 5678 9012 3456\" \u002F>\n```\n\nBuilt-in browsers and password managers handle most of this if you use the right `autocomplete` value.\n\n## Account IDs and identifiers\n\nFor internal IDs (account IDs, transaction IDs, session IDs):\n\n- **Display chunked** if the user might read or transcribe them.\n- **Display monospaced** so digits and letters align (`font-family: monospace; font-variant-numeric: tabular-nums;`).\n- **Provide one-click copy** so users don't have to manually select.\n\n```html\n\u003Cdiv class=\"id-display\">\n  \u003Cspan class=\"id-value\">ws_8f3c-7a92-1b04\u003C\u002Fspan>\n  \u003Cbutton onclick=\"copyToClipboard('ws_8f3c-7a92-1b04')\" aria-label=\"Copy\">?\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n```\n\nThe chunking aids reading aloud (support calls) and verification.\n\n## Currency\n\nCurrency should always use locale-appropriate digit grouping:\n\n- US English: `$1,234,567.89` (3-digit groups, period decimal).\n- European: `€1.234.567,89` (period grouping, comma decimal).\n- Indian: `₹12,34,567.89` (mixed grouping: 2-2-3).\n\nUse `Intl.NumberFormat` to get this right per locale:\n\n```js\nnew Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' })\n  .format(1234567.89);\n\u002F\u002F \"$1,234,567.89\"\n```\n\nNumeric columns in tables should use `font-variant-numeric: tabular-nums` so digits align vertically.\n\n## Anti-patterns\n\n- **Continuous strings**: a 16-digit credit card with no chunking. Users can't verify.\n- **Inconsistent chunk sizes within a context**: phone numbers shown as 3-4-3 here and 5-2-3 there. Each format is a re-learn.\n- **Wrong locale grouping**: showing `1,234.56` to a German user (who reads it as 1,234.56 = roughly 1,234 plus 56\u002F100 instead of 1234.56).\n- **Missing `inputmode`**: a numeric field that opens the alphabet keyboard on mobile. Easy fix; commonly missed.\n- **OTP with no auto-advance \u002F paste support**: users tab manually between fields; if they paste, only the first field fills.\n- **Unmasked credit card display**: privacy and security violation. Always mask all but the last 4.\n\n## Heuristics\n\n1. **The \"read it aloud\" test.** Try reading the chunked number aloud. If it requires re-grouping mentally, the chunking is wrong.\n2. **The cross-locale check.** For currency and dates, test in at least 2–3 locales. Format mismatches are common.\n3. **The clipboard \u002F autofill check.** Does pasting the user's clipboard into your input work cleanly? Do password managers fill correctly?\n4. **The mobile keyboard check.** Numeric inputs should produce numeric keyboards on mobile (`inputmode=\"numeric\"`).\n\n## Related sub-skills\n\n- **`chunking`** (parent).\n- **`chunking-form-grouping`** — chunking at the form-section level.\n- **`legibility`** (perception) — tabular numerals for column alignment.\n- **`accessibility-perceivable`** (process) — number formatting affects screen-reader pronunciation.\n","# Chunking applied to numeric strings\n\nNumbers are the canonical chunking case. A 10-digit phone number, a 16-digit credit card, a 6-digit OTP — without chunking, these are working-memory overloads. With chunking, they're manageable.\n\n## Standard chunkings\n\nConventions that have evolved across industries:\n\n| Type | Standard chunking | Example |\n|---|---|---|\n| US phone | 3-3-4 | 555-867-5309 |\n| International phone | varies; usually 2-3-3-2 or similar | +44 20 7946 0958 |\n| Credit card | 4-4-4-4 (most) or 4-6-5 (Amex) | 4242 4242 4242 4242 |\n| Social Security (US) | 3-2-4 | 123-45-6789 |\n| OTP \u002F verification | 3-3 (6-digit) or 4-4 (8-digit) | 123-456 |\n| Bank account (US) | varies; often grouped with type | 110000000 → routing display |\n| ISBN | 1-3-3-5-1 (ISBN-13) | 978-3-16-148410-0 |\n| IP address | 4 octets separated by dots | 192.168.1.1 |\n| Date (ISO) | 4-2-2 | 2026-05-02 |\n| Currency | 3-digit groups | $1,234,567.89 |\n\nWhen in doubt, follow the convention. Users have already learned it.\n\n## OTP \u002F verification code entry\n\nThe most common modern chunking case in product UI. A 6-digit code from email or SMS, entered into a verification field.\n\n### Single field vs. chunked fields\n\nSingle field:\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"6\" pattern=\"\\d{6}\" \u002F>\n```\n\nChunked fields (one per digit):\n```html\n\u003Cdiv class=\"otp-input\" role=\"group\" aria-label=\"Verification code\">\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" autocomplete=\"one-time-code\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cspan class=\"separator\" aria-hidden>—\u003C\u002Fspan>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n  \u003Cinput type=\"text\" inputmode=\"numeric\" maxlength=\"1\" \u002F>\n\u003C\u002Fdiv>\n```\n\nThe chunked version:\n\n- Visually matches how the code is presented in email\u002FSMS.\n- Lets the user verify each digit's position mid-entry.\n- Auto-advances focus on each digit (with JS).\n- Supports paste-spread (paste into first input fills all).\n\nThe single-field version is simpler to implement and supports SMS-autofill on iOS via `autocomplete=\"one-time-code\"`. Modern apps often offer both: a single field on mobile (where autofill is critical) and chunked on desktop.\n\n### OTP UX details\n\n- **Auto-advance** focus to the next digit on input.\n- **Auto-back** focus to previous digit on backspace.\n- **Paste support**: pasting a 6-digit string into the first input should distribute across all six.\n- **`autocomplete=\"one-time-code\"`** on at least one input enables iOS Messages autofill.\n- **Numeric keyboard on mobile** via `inputmode=\"numeric\"`.\n- **Optional auto-submit** when the last digit is entered (debate: some users dislike auto-submit because it commits before they can verify).\n\n## Phone number entry\n\nPhone numbers vary widely by country. Patterns:\n\n- **US-only forms**: enforce 3-3-4 with format mask or chunked inputs.\n- **International forms**: use a country selector + a free-text number field; format on display rather than enforcing entry format.\n- **Dual-purpose** (international users + US-heavy): use [libphonenumber](https:\u002F\u002Fgithub.com\u002Fgoogle\u002Flibphonenumber) or similar to validate and format dynamically.\n\n```html\n\u003Clabel>\n  Phone\n  \u003Cdiv class=\"phone-input\">\n    \u003Cselect name=\"country-code\">\n      \u003Coption value=\"+1\">?? +1\u003C\u002Foption>\n      \u003Coption value=\"+44\">?? +44\u003C\u002Foption>\n      \u003C!-- ... -->\n    \u003C\u002Fselect>\n    \u003Cinput type=\"tel\" name=\"phone\" placeholder=\"555-867-5309\" \u002F>\n  \u003C\u002Fdiv>\n\u003C\u002Flabel>\n```\n\n## Credit card display\n\nIn production, never display full card numbers — show the last 4 digits chunked with masking:\n\n```\n**** **** **** 4242\n```\n\nFor entry, use 4-4-4-4 chunking with auto-advance, paste support, and card-type detection:\n\n```html\n\u003Cinput type=\"text\" inputmode=\"numeric\" autocomplete=\"cc-number\"\n       placeholder=\"1234 5678 9012 3456\" \u002F>\n```\n\nBuilt-in browsers and password managers handle most of this if you use the right `autocomplete` value.\n\n## Account IDs and identifiers\n\nFor internal IDs (account IDs, transaction IDs, session IDs):\n\n- **Display chunked** if the user might read or transcribe them.\n- **Display monospaced** so digits and letters align (`font-family: monospace; font-variant-numeric: tabular-nums;`).\n- **Provide one-click copy** so users don't have to manually select.\n\n```html\n\u003Cdiv class=\"id-display\">\n  \u003Cspan class=\"id-value\">ws_8f3c-7a92-1b04\u003C\u002Fspan>\n  \u003Cbutton onclick=\"copyToClipboard('ws_8f3c-7a92-1b04')\" aria-label=\"Copy\">?\u003C\u002Fbutton>\n\u003C\u002Fdiv>\n```\n\nThe chunking aids reading aloud (support calls) and verification.\n\n## Currency\n\nCurrency should always use locale-appropriate digit grouping:\n\n- US English: `$1,234,567.89` (3-digit groups, period decimal).\n- European: `€1.234.567,89` (period grouping, comma decimal).\n- Indian: `₹12,34,567.89` (mixed grouping: 2-2-3).\n\nUse `Intl.NumberFormat` to get this right per locale:\n\n```js\nnew Intl.NumberFormat('en-US', { style: 'currency', currency: 'USD' })\n  .format(1234567.89);\n\u002F\u002F \"$1,234,567.89\"\n```\n\nNumeric columns in tables should use `font-variant-numeric: tabular-nums` so digits align vertically.\n\n## Anti-patterns\n\n- **Continuous strings**: a 16-digit credit card with no chunking. Users can't verify.\n- **Inconsistent chunk sizes within a context**: phone numbers shown as 3-4-3 here and 5-2-3 there. Each format is a re-learn.\n- **Wrong locale grouping**: showing `1,234.56` to a German user (who reads it as 1,234.56 = roughly 1,234 plus 56\u002F100 instead of 1234.56).\n- **Missing `inputmode`**: a numeric field that opens the alphabet keyboard on mobile. Easy fix; commonly missed.\n- **OTP with no auto-advance \u002F paste support**: users tab manually between fields; if they paste, only the first field fills.\n- **Unmasked credit card display**: privacy and security violation. Always mask all but the last 4.\n\n## Heuristics\n\n1. **The \"read it aloud\" test.** Try reading the chunked number aloud. If it requires re-grouping mentally, the chunking is wrong.\n2. **The cross-locale check.** For currency and dates, test in at least 2–3 locales. Format mismatches are common.\n3. **The clipboard \u002F autofill check.** Does pasting the user's clipboard into your input work cleanly? Do password managers fill correctly?\n4. **The mobile keyboard check.** Numeric inputs should produce numeric keyboards on mobile (`inputmode=\"numeric\"`).\n\n## Related sub-skills\n\n- **`chunking`** (parent).\n- **`chunking-form-grouping`** — chunking at the form-section level.\n- **`legibility`** (perception) — tabular numerals for column alignment.\n- **`accessibility-perceivable`** (process) — number formatting affects screen-reader pronunciation.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp",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":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-numeric-and-otp",{"tool":65,"command":66},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-numeric-and-otp",{"tool":68,"command":69},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill chunking-numeric-and-otp","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp\u002FSKILL.md",true,[73],{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fnumeric-format-conventions.md","REFERENCE","参考文档",3272,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fcognition-and-learnability-principles\u002Fskills\u002Fchunking-numeric-and-otp\u002Freferences\u002Fnumeric-format-conventions.md",[80,90,98,106,114,122],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"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":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":89},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":89},"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":89},"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":89},"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":84,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":89},"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",[],[]]