[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWJ1FJEKM6HDTK7F58RY1C":3,"skill-same:01M6JWJ1FJEKM6HDTK7F58RY1C":82},{"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":23,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":60,"updatedAt":61,"install":62,"resources":75},"01M6JWJ1FJEKM6HDTK7F58RY1C","factor-of-safety-content-stress",null,"Use this skill when designing UI to survive content extremes — long names, big numbers, multi-line addresses, missing images, internationalized strings, dense data. Trigger when reviewing a design against worst-case content, when bug reports show layouts breaking on real data, or when picking content limits and validation rules. Sub-aspect of `factor-of-safety`; read that first.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Ffactor-of-safety-content-stress\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"content","factor of safety","factor of safety content stress","stress","factor","Safety","long","when","limits","design","ui","addresses","strings","data","missing","read","line","trigger","show","images","reports","bug","use","2026-11-10 10:12:30",false,"---\nname: factor-of-safety-content-stress\ndescription: 'Use this skill when designing UI to survive content extremes — long names, big numbers, multi-line addresses, missing images, internationalized strings, dense data. Trigger when reviewing a design against worst-case content, when bug reports show layouts breaking on real data, or when picking content limits and validation rules. Sub-aspect of `factor-of-safety`; read that first.'\n---\n\n# Designing for content stress\n\nMost designs are tested against ideal sample data: typical-length names, round numbers, well-cropped images, English. Real data is messier. Names span 1 to 100+ characters; numbers span tiny to enormous; images are missing, oversize, or wrong aspect; translations stretch UI strings 30%+. A design that handles only the typical breaks routinely on real users.\n\n## Common content-stress vectors\n\n### Name and identifier length\n\n- **English names**: typically 5–20 characters. Outliers: hyphenated, multi-word, titled — up to 60+.\n- **Other-script names**: Chinese names typically 2–4 characters; Spanish names with multiple surnames can exceed 50; Tamil names can be very long.\n- **Email addresses**: typically 15–35 characters. RFC max: 254.\n- **Account IDs \u002F hashes**: 6–40 characters; users often need to read or copy them.\n\nDesign for the worst plausible case; truncate gracefully with tooltips for very long values.\n\n### Numeric magnitudes\n\n- **Currency**: $0.01 to $999,999,999.99 — 13 visible characters at full extreme.\n- **Counts**: 1 to billions; consider abbreviation (\"12.4M\") for compact display.\n- **Percentages**: -100% to 100% (or beyond for compounded growth).\n- **Time durations**: seconds to years; consider unit-switching display.\n\nA column sized for \"$5,000.00\" breaks for \"$1,234,567.89.\" Size for the worst case or use abbreviated formats.\n\n### Image content\n\n- **Missing**: image fails to load. Show a placeholder, not broken-image icon.\n- **Wrong aspect**: image doesn't match expected ratio. Crop, fit, or letterbox; choose deliberately.\n- **Oversize**: image is 4MB. Lazy-load, downsample, or progressively load.\n- **Mid-load**: brief moment with no image. Show skeleton or low-res preview.\n\n### Internationalization\n\n- **String length**: German strings are typically 30% longer than English; Russian and French similar; Chinese often 30% shorter.\n- **Bidirectional**: Arabic and Hebrew run right-to-left; mixed LTR\u002FRTL content has its own complexities.\n- **Date \u002F number format**: vary widely (covered in `chunking-numeric-and-otp`).\n- **Pluralization**: English has 2 forms (cat, cats); other languages have up to 6 (Polish, Russian, Welsh).\n\nDesign with stretch room; test in worst-case languages (German for length, Arabic for direction).\n\n### Empty states\n\n- **Zero rows in a table**: don't show an empty grid; show an explanation.\n- **Zero items in a list**: show an empty state with guidance.\n- **First-run state**: no data yet; show onboarding.\n\nEmpty states are often forgotten until QA. Design them deliberately.\n\n### Long-tail of edge cases\n\n- **Single character of content**: a one-character name or message.\n- **Whitespace-only content**: validate; reject or strip.\n- **Special characters**: Unicode emojis, combining characters, RTL marks; test rendering.\n- **HTML \u002F SQL injection in user content**: sanitize at render time.\n\n## Worked examples\n\n### Example 1: a card layout that absorbs content variation\n\n```html\n\u003Carticle class=\"user-card\">\n  \u003Cdiv class=\"avatar\">\n    \u003Cimg src={avatarUrl} alt=\"\" onerror=\"this.style.display='none'\" \u002F>\n    \u003Cspan class=\"avatar-fallback\">{initials}\u003C\u002Fspan>\n  \u003C\u002Fdiv>\n  \u003Cdiv class=\"user-info\">\n    \u003Ch3 class=\"name\">{name}\u003C\u002Fh3>\n    \u003Cp class=\"role\">{role}\u003C\u002Fp>\n    \u003Cp class=\"email\">{email}\u003C\u002Fp>\n  \u003C\u002Fdiv>\n\u003C\u002Farticle>\n\n\u003Cstyle>\n  .user-card {\n    display: grid;\n    grid-template-columns: 48px 1fr;\n    gap: 12px;\n    padding: 16px;\n    min-height: 80px;       \u002F* margin for multi-line names *\u002F\n  }\n  .avatar { position: relative; width: 48px; height: 48px; }\n  .avatar img { width: 100%; height: 100%; object-fit: cover; }\n  .avatar-fallback { \u002F* shown when image fails *\u002F }\n  .user-info { min-width: 0; }   \u002F* allows truncation *\u002F\n  .name {\n    overflow-wrap: break-word;\n    hyphens: auto;\n  }\n  .email {\n    overflow: hidden;\n    text-overflow: ellipsis;\n    white-space: nowrap;\n    color: hsl(0 0% 45%);\n  }\n\u003C\u002Fstyle>\n```\n\nThe card handles:\n- Missing avatar (falls back to initials).\n- Long name (wraps to 2–3 lines; card grows).\n- Long email (truncates with ellipsis; full visible on hover).\n- Empty role (just doesn't render).\n\n### Example 2: a numeric column sized for the worst case\n\n```html\n\u003Ctd class=\"amount\">{currency(amount)}\u003C\u002Ftd>\n\n\u003Cstyle>\n  .amount {\n    text-align: right;\n    font-variant-numeric: tabular-nums;\n    width: 12ch;          \u002F* fits \"$9,999,999.99\" *\u002F\n  }\n\u003C\u002Fstyle>\n```\n\nThe column width accommodates the maximum-realistic value. Smaller values right-align within it.\n\n### Example 3: handling translation stretch\n\n```html\n\u003Cbutton class=\"cta\">{t('signup.cta')}\u003C\u002Fbutton>\n\n\u003Cstyle>\n  .cta {\n    min-width: 120px;\n    padding: 12px 24px;\n    white-space: nowrap;     \u002F* don't wrap; let it grow horizontally *\u002F\n  }\n  \u002F* On narrow screens, allow wrap *\u002F\n  @media (max-width: 600px) {\n    .cta { white-space: normal; }\n  }\n\u003C\u002Fstyle>\n```\n\nThe button accommodates German \"Kostenlos anmelden\" (longer than \"Sign up free\") without breaking the layout.\n\n### Example 4: empty state for a list\n\n```html\n{items.length > 0\n  ? \u003CItemList items={items} \u002F>\n  : \u003CEmpty\n      icon={\u003CInboxIcon \u002F>}\n      title=\"Your inbox is empty\"\n      description=\"When messages arrive, they'll appear here.\"\n      action={\u003CButton>Compose new message\u003C\u002FButton>}\n    \u002F>\n}\n```\n\nDesigned deliberately, not just \"the list happens to be empty.\"\n\n## Anti-patterns\n\n- **Sample data only.** Designing with \"John Smith\" and \"$50.00.\" Real users break the layout.\n- **Fixed widths sized for typical.** A 200px name field that truncates 30% of users.\n- **No empty state.** A blank table with no explanation.\n- **No loading state.** A blank screen while data fetches.\n- **No error state.** A blank screen when data fetch fails.\n- **Translation testing only at release.** Translations expanded the UI; many surfaces need rework.\n- **Over-truncation.** Names truncated to 8 characters because \"they look messy otherwise.\" Users can't identify themselves.\n\n## Heuristics\n\n1. **The \"stress test page\" approach.** Build a page that renders every component with maximum-length and minimum-length content. Screenshot regularly; fix what breaks.\n2. **The \"real data\" check.** Pull real samples (anonymized) from production and render them in the design. Most layouts surprise.\n3. **The \"longest plausible content\" estimate.** For each text field, ask: what's the worst case? Design for that.\n4. **The translation audit.** Render in German (long) and Arabic (RTL). What broke?\n\n## Related sub-skills\n\n- **`factor-of-safety`** (parent).\n- **`factor-of-safety-failure-margin`** — capacity and dependency margins.\n- **`chunking-numeric-and-otp`** — numeric formatting decisions.\n- **`accessibility-perceivable`** — content stress is also accessibility (long content for low-vision; missing images for blind users).\n","# Designing for content stress\n\nMost designs are tested against ideal sample data: typical-length names, round numbers, well-cropped images, English. Real data is messier. Names span 1 to 100+ characters; numbers span tiny to enormous; images are missing, oversize, or wrong aspect; translations stretch UI strings 30%+. A design that handles only the typical breaks routinely on real users.\n\n## Common content-stress vectors\n\n### Name and identifier length\n\n- **English names**: typically 5–20 characters. Outliers: hyphenated, multi-word, titled — up to 60+.\n- **Other-script names**: Chinese names typically 2–4 characters; Spanish names with multiple surnames can exceed 50; Tamil names can be very long.\n- **Email addresses**: typically 15–35 characters. RFC max: 254.\n- **Account IDs \u002F hashes**: 6–40 characters; users often need to read or copy them.\n\nDesign for the worst plausible case; truncate gracefully with tooltips for very long values.\n\n### Numeric magnitudes\n\n- **Currency**: $0.01 to $999,999,999.99 — 13 visible characters at full extreme.\n- **Counts**: 1 to billions; consider abbreviation (\"12.4M\") for compact display.\n- **Percentages**: -100% to 100% (or beyond for compounded growth).\n- **Time durations**: seconds to years; consider unit-switching display.\n\nA column sized for \"$5,000.00\" breaks for \"$1,234,567.89.\" Size for the worst case or use abbreviated formats.\n\n### Image content\n\n- **Missing**: image fails to load. Show a placeholder, not broken-image icon.\n- **Wrong aspect**: image doesn't match expected ratio. Crop, fit, or letterbox; choose deliberately.\n- **Oversize**: image is 4MB. Lazy-load, downsample, or progressively load.\n- **Mid-load**: brief moment with no image. Show skeleton or low-res preview.\n\n### Internationalization\n\n- **String length**: German strings are typically 30% longer than English; Russian and French similar; Chinese often 30% shorter.\n- **Bidirectional**: Arabic and Hebrew run right-to-left; mixed LTR\u002FRTL content has its own complexities.\n- **Date \u002F number format**: vary widely (covered in `chunking-numeric-and-otp`).\n- **Pluralization**: English has 2 forms (cat, cats); other languages have up to 6 (Polish, Russian, Welsh).\n\nDesign with stretch room; test in worst-case languages (German for length, Arabic for direction).\n\n### Empty states\n\n- **Zero rows in a table**: don't show an empty grid; show an explanation.\n- **Zero items in a list**: show an empty state with guidance.\n- **First-run state**: no data yet; show onboarding.\n\nEmpty states are often forgotten until QA. Design them deliberately.\n\n### Long-tail of edge cases\n\n- **Single character of content**: a one-character name or message.\n- **Whitespace-only content**: validate; reject or strip.\n- **Special characters**: Unicode emojis, combining characters, RTL marks; test rendering.\n- **HTML \u002F SQL injection in user content**: sanitize at render time.\n\n## Worked examples\n\n### Example 1: a card layout that absorbs content variation\n\n```html\n\u003Carticle class=\"user-card\">\n  \u003Cdiv class=\"avatar\">\n    \u003Cimg src={avatarUrl} alt=\"\" onerror=\"this.style.display='none'\" \u002F>\n    \u003Cspan class=\"avatar-fallback\">{initials}\u003C\u002Fspan>\n  \u003C\u002Fdiv>\n  \u003Cdiv class=\"user-info\">\n    \u003Ch3 class=\"name\">{name}\u003C\u002Fh3>\n    \u003Cp class=\"role\">{role}\u003C\u002Fp>\n    \u003Cp class=\"email\">{email}\u003C\u002Fp>\n  \u003C\u002Fdiv>\n\u003C\u002Farticle>\n\n\u003Cstyle>\n  .user-card {\n    display: grid;\n    grid-template-columns: 48px 1fr;\n    gap: 12px;\n    padding: 16px;\n    min-height: 80px;       \u002F* margin for multi-line names *\u002F\n  }\n  .avatar { position: relative; width: 48px; height: 48px; }\n  .avatar img { width: 100%; height: 100%; object-fit: cover; }\n  .avatar-fallback { \u002F* shown when image fails *\u002F }\n  .user-info { min-width: 0; }   \u002F* allows truncation *\u002F\n  .name {\n    overflow-wrap: break-word;\n    hyphens: auto;\n  }\n  .email {\n    overflow: hidden;\n    text-overflow: ellipsis;\n    white-space: nowrap;\n    color: hsl(0 0% 45%);\n  }\n\u003C\u002Fstyle>\n```\n\nThe card handles:\n- Missing avatar (falls back to initials).\n- Long name (wraps to 2–3 lines; card grows).\n- Long email (truncates with ellipsis; full visible on hover).\n- Empty role (just doesn't render).\n\n### Example 2: a numeric column sized for the worst case\n\n```html\n\u003Ctd class=\"amount\">{currency(amount)}\u003C\u002Ftd>\n\n\u003Cstyle>\n  .amount {\n    text-align: right;\n    font-variant-numeric: tabular-nums;\n    width: 12ch;          \u002F* fits \"$9,999,999.99\" *\u002F\n  }\n\u003C\u002Fstyle>\n```\n\nThe column width accommodates the maximum-realistic value. Smaller values right-align within it.\n\n### Example 3: handling translation stretch\n\n```html\n\u003Cbutton class=\"cta\">{t('signup.cta')}\u003C\u002Fbutton>\n\n\u003Cstyle>\n  .cta {\n    min-width: 120px;\n    padding: 12px 24px;\n    white-space: nowrap;     \u002F* don't wrap; let it grow horizontally *\u002F\n  }\n  \u002F* On narrow screens, allow wrap *\u002F\n  @media (max-width: 600px) {\n    .cta { white-space: normal; }\n  }\n\u003C\u002Fstyle>\n```\n\nThe button accommodates German \"Kostenlos anmelden\" (longer than \"Sign up free\") without breaking the layout.\n\n### Example 4: empty state for a list\n\n```html\n{items.length > 0\n  ? \u003CItemList items={items} \u002F>\n  : \u003CEmpty\n      icon={\u003CInboxIcon \u002F>}\n      title=\"Your inbox is empty\"\n      description=\"When messages arrive, they'll appear here.\"\n      action={\u003CButton>Compose new message\u003C\u002FButton>}\n    \u002F>\n}\n```\n\nDesigned deliberately, not just \"the list happens to be empty.\"\n\n## Anti-patterns\n\n- **Sample data only.** Designing with \"John Smith\" and \"$50.00.\" Real users break the layout.\n- **Fixed widths sized for typical.** A 200px name field that truncates 30% of users.\n- **No empty state.** A blank table with no explanation.\n- **No loading state.** A blank screen while data fetches.\n- **No error state.** A blank screen when data fetch fails.\n- **Translation testing only at release.** Translations expanded the UI; many surfaces need rework.\n- **Over-truncation.** Names truncated to 8 characters because \"they look messy otherwise.\" Users can't identify themselves.\n\n## Heuristics\n\n1. **The \"stress test page\" approach.** Build a page that renders every component with maximum-length and minimum-length content. Screenshot regularly; fix what breaks.\n2. **The \"real data\" check.** Pull real samples (anonymized) from production and render them in the design. Most layouts surprise.\n3. **The \"longest plausible content\" estimate.** For each text field, ask: what's the worst case? Design for that.\n4. **The translation audit.** Render in German (long) and Arabic (RTL). What broke?\n\n## Related sub-skills\n\n- **`factor-of-safety`** (parent).\n- **`factor-of-safety-failure-margin`** — capacity and dependency margins.\n- **`chunking-numeric-and-otp`** — numeric formatting decisions.\n- **`accessibility-perceivable`** — content stress is also accessibility (long content for low-vision; missing images for blind users).\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Ffactor-of-safety-content-stress",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":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill factor-of-safety-content-stress",{"tool":68,"command":69},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill factor-of-safety-content-stress",{"tool":71,"command":72},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill factor-of-safety-content-stress","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Ffactor-of-safety-content-stress\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcontent-stress-test-cases.md","REFERENCE","参考文档",3786,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fprocess-and-robustness-principles\u002Fskills\u002Ffactor-of-safety-content-stress\u002Freferences\u002Fcontent-stress-test-cases.md",[83,93,101,109,117,125],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":92},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":92},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":92},"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":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":92},"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",[],[]]