[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWCQ8BN2DS8GCKMQS0E1C5":3,"skill-same:01M6JWCQ8BN2DS8GCKMQS0E1C5":78},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M6JWCQ8BN2DS8GCKMQS0E1C5","hierarchy-typographic",null,"Use this skill when the question is specifically about how to construct visual hierarchy through typography — picking a type scale, ladders of weight, line-height steps, and the relationships between display, heading, body, and caption type. Trigger when designing type systems, choosing fonts, picking heading sizes, defining a design system's typographic tokens, fixing a \"no clear focal point in the headline area\" issue, or reviewing why a long-form page feels like a wall of text. Sub-aspect of the broader `hierarchy` principle; 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\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-typographic\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],"hierarchy","hierarchy typographic","line","when","point","body","long-form","display","fonts","you","form","how to","design","trigger","issue","typography","read","question","page","text","system","why","how","design system","2026-11-10 10:12:30",false,"---\nname: hierarchy-typographic\ndescription: 'Use this skill when the question is specifically about how to construct visual hierarchy through typography — picking a type scale, ladders of weight, line-height steps, and the relationships between display, heading, body, and caption type. Trigger when designing type systems, choosing fonts, picking heading sizes, defining a design system''s typographic tokens, fixing a \"no clear focal point in the headline area\" issue, or reviewing why a long-form page feels like a wall of text. Sub-aspect of the broader `hierarchy` principle; read that first if you haven''t already.'\n---\n\n# Hierarchy through typography\n\nTypography alone can carry a complete hierarchy without color, color alone, or layout tricks. A well-constructed type system gives you 4–6 distinct ranks of importance using nothing but size, weight, and (sometimes) tracking and tone. This skill covers how to build that system.\n\n## When this is the decisive sub-aspect\n\n- You're picking the type tokens for a new design system (display, h1, h2, h3, h4, body-lg, body, body-sm, caption, micro).\n- You're working in a constrained color palette (monochrome, a single brand color) and need hierarchy without leaning on hue.\n- The page is text-heavy (docs, articles, settings descriptions, emails) and feels like a wall.\n- You're reviewing a layout where headings, sub-heads, and body text don't read as distinct ranks.\n\n## Core ideas\n\n### Pick a type scale, not arbitrary sizes\n\nA *type scale* is a multiplicative ratio applied to a base size to generate a series of harmonious sizes. Common scales:\n\n- **1.125** (Major Second) — very subtle. Good for dense application UI where step changes between sizes shouldn't shout.\n- **1.2** (Minor Third) — gentle, common in software UI.\n- **1.25** (Major Third) — a solid default for general web; what Tailwind's default scale approximates.\n- **1.333** (Perfect Fourth) — feels editorial; good for content sites.\n- **1.414** (Augmented Fourth, √2) — common in print.\n- **1.5** (Perfect Fifth) — bold, feels like a magazine layout.\n- **1.618** (Golden Ratio) — dramatic, marketing\u002Fhero scale.\n\nPick *one* ratio per project. Mixing ratios across sizes destroys the rhythm.\n\nA worked scale at base 16px and ratio 1.25:\n\n```\ncaption  10.24 px   (16 \u002F 1.25 \u002F 1.25)\nbody-sm  12.80 px   (16 \u002F 1.25)\nbody     16.00 px   (base)\nbody-lg  20.00 px   (16 * 1.25)\nh4       25.00 px   (16 * 1.25^2)\nh3       31.25 px   (16 * 1.25^3)\nh2       39.06 px   (16 * 1.25^4)\nh1       48.83 px   (16 * 1.25^5)\ndisplay  61.04 px   (16 * 1.25^6)\n```\n\nRounded to friendly numbers (10, 13, 16, 20, 25, 31, 39, 49, 61), this gives you a 9-step ladder with consistent visual jumps between any two adjacent steps.\n\n### Use weight as a second axis\n\nSize alone is enough for hierarchy in body-vs.-heading contexts but is a blunt tool when you need fine distinctions. Weight gives you a second axis. A useful weight ladder:\n\n```\nhairline \u002F thin    100   — display only, never body\nlight              300   — large display sizes; never small\nregular            400   — body\nmedium             500   — UI labels, buttons\nsemibold           600   — headings, emphasis\nbold               700   — strong emphasis, heavy display\nblack              900   — display only\n```\n\nMost software UIs need only three weights: regular (400), medium (500), and semibold (600). Reach for bolder weights only at display sizes; bold at body size is hard to read.\n\n### Combine size and weight, don't trade them\n\nA common mistake is treating size *or* weight as the hierarchy signal. They compound:\n\n- A 24px-semibold heading reads as much higher in the hierarchy than a 24px-regular heading, even though the size is identical.\n- A 16px-regular body paragraph and a 16px-medium label are perceived as different ranks despite identical size.\n\nWhen constructing a step in your hierarchy, *both* dial up: bigger headings should also be bolder. The exception is display type (very large), which often *decreases* in weight at the largest sizes (light or regular at 60px+ reads as elegant; black at 60px+ reads as shouting).\n\n### Line height (leading) is part of the system\n\nTighter leading (1.1–1.25) suits display and headings. Looser leading (1.5–1.75) suits body. Mismatch a heading with body leading (1.5) and the heading feels droopy; mismatch a body with display leading (1.2) and reading becomes hard.\n\nA workable mapping:\n\n```\ndisplay, h1, h2:   line-height 1.1–1.25\nh3, h4:            line-height 1.25–1.4\nbody, body-lg:     line-height 1.5–1.75\nbody-sm, caption:  line-height 1.4–1.6\n```\n\n### Line length (measure)\n\nFor sustained reading, constrain body text to roughly 45–75 characters per line (≈ 65ch is a common default). Longer lines fatigue eye-tracking; shorter lines fragment thought. Headings can be wider; captions and labels can be tighter.\n\n```css\n.body-text { max-width: 65ch; }\n```\n\n### Tracking (letter-spacing)\n\nGenerally leave tracking alone. Two cases where it earns adjustment:\n\n- **All-caps labels and small caps:** add ~0.04–0.08em of tracking; they read tightly otherwise.\n- **Very large display type:** subtract a small amount (-0.01 to -0.02em); large type looks loose without it.\n\n## Worked example: a complete typographic hierarchy in CSS\n\n```css\n:root {\n  \u002F* Type scale at ratio 1.25, base 16px *\u002F\n  --text-caption: 0.64rem;   \u002F* 10.24 *\u002F\n  --text-sm:      0.80rem;   \u002F* 12.80 *\u002F\n  --text-base:    1.00rem;   \u002F* 16.00 *\u002F\n  --text-lg:      1.25rem;   \u002F* 20.00 *\u002F\n  --text-xl:      1.563rem;  \u002F* 25.00 *\u002F\n  --text-2xl:     1.953rem;  \u002F* 31.25 *\u002F\n  --text-3xl:     2.441rem;  \u002F* 39.06 *\u002F\n  --text-4xl:     3.052rem;  \u002F* 48.83 *\u002F\n  --text-display: 3.815rem;  \u002F* 61.04 *\u002F\n\n  \u002F* Weight ladder *\u002F\n  --weight-body:     400;\n  --weight-label:    500;\n  --weight-emphasis: 600;\n  --weight-display:  700;\n\n  \u002F* Leading *\u002F\n  --leading-display: 1.1;\n  --leading-heading: 1.25;\n  --leading-body:    1.6;\n  --leading-tight:   1.4;\n}\n\n.display {\n  font-size: var(--text-display);\n  font-weight: 400;          \u002F* display gets lighter weight, paradoxically *\u002F\n  line-height: var(--leading-display);\n  letter-spacing: -0.02em;\n}\nh1 {\n  font-size: var(--text-3xl);\n  font-weight: var(--weight-emphasis);\n  line-height: var(--leading-heading);\n  letter-spacing: -0.01em;\n}\nh2 {\n  font-size: var(--text-2xl);\n  font-weight: var(--weight-emphasis);\n  line-height: var(--leading-heading);\n}\nh3 {\n  font-size: var(--text-xl);\n  font-weight: var(--weight-emphasis);\n  line-height: var(--leading-heading);\n}\nh4 {\n  font-size: var(--text-lg);\n  font-weight: var(--weight-label);\n  line-height: var(--leading-heading);\n}\nbody, p {\n  font-size: var(--text-base);\n  font-weight: var(--weight-body);\n  line-height: var(--leading-body);\n  max-width: 65ch;\n}\n.label, button, .ui-control {\n  font-size: var(--text-sm);\n  font-weight: var(--weight-label);\n  line-height: var(--leading-tight);\n}\n.caption, small, .micro {\n  font-size: var(--text-caption);\n  font-weight: var(--weight-body);\n  line-height: var(--leading-tight);\n  color: rgb(0 0 0 \u002F 0.55);   \u002F* tone reduction adds tertiary recession *\u002F\n}\n```\n\nEight clear ranks, all derived from one ratio, three weights, three leading values, and one tone reduction at the very bottom. This is enough hierarchy to handle any UI or content surface.\n\n## Anti-patterns\n\n- **Random sizing.** \"Make this 18px\" \u002F \"this 19px\" \u002F \"this 22px\" — close-but-not-equal sizes look like accidents. If two things should be the same rank, give them the same size; if different ranks, make the difference clear.\n- **Bold everything.** When every label, every heading, and every value is bold, none of them read as emphasized. Reserve bold for one or two roles.\n- **Gigantic body type.** Body text larger than ~18–20px starts to feel like a slide deck. Reserve large type for headings; keep body in the 14–18px range.\n- **Tiny captions.** Below 11px, anti-aliasing destroys legibility. If you find yourself reaching for 9px or 10px, you have too much content for the space — cut content rather than shrink type.\n- **Inconsistent weight per role.** \"Card titles are semibold here, medium there.\" Decide once per role.\n\n## Heuristics\n\n1. **Print-test.** Print the page in grayscale on regular paper. Hierarchy that survives this test is robust. Hierarchy that requires color or screen brightness is fragile.\n2. **Three-rank squint.** Squint until detail blurs. You should still see a primary tier, a secondary tier, and a recessive tier. If everything is one tone of grey, hierarchy is too flat.\n3. **The body-only test.** Hide all headings; the body should still feel like prose, not a wall. If it feels like a wall, your `max-width` or leading is wrong.\n\n## Related principles\n\n- **`hierarchy`** — the parent skill. Read it for the full framing.\n- **`hierarchy-spatial`** — when type alone isn't enough, spatial hierarchy carries the rest.\n- **`hierarchy-color-and-tone`** — color and tone as a third axis on top of size+weight.\n- **`legibility`** and **`readability`** — the typeface- and layout-side of typography that hierarchy depends on.\n- **`signal-to-noise-ratio`** — too many active ranks reduces SNR; restraint multiplies the effect of each rank.\n","# Hierarchy through typography\n\nTypography alone can carry a complete hierarchy without color, color alone, or layout tricks. A well-constructed type system gives you 4–6 distinct ranks of importance using nothing but size, weight, and (sometimes) tracking and tone. This skill covers how to build that system.\n\n## When this is the decisive sub-aspect\n\n- You're picking the type tokens for a new design system (display, h1, h2, h3, h4, body-lg, body, body-sm, caption, micro).\n- You're working in a constrained color palette (monochrome, a single brand color) and need hierarchy without leaning on hue.\n- The page is text-heavy (docs, articles, settings descriptions, emails) and feels like a wall.\n- You're reviewing a layout where headings, sub-heads, and body text don't read as distinct ranks.\n\n## Core ideas\n\n### Pick a type scale, not arbitrary sizes\n\nA *type scale* is a multiplicative ratio applied to a base size to generate a series of harmonious sizes. Common scales:\n\n- **1.125** (Major Second) — very subtle. Good for dense application UI where step changes between sizes shouldn't shout.\n- **1.2** (Minor Third) — gentle, common in software UI.\n- **1.25** (Major Third) — a solid default for general web; what Tailwind's default scale approximates.\n- **1.333** (Perfect Fourth) — feels editorial; good for content sites.\n- **1.414** (Augmented Fourth, √2) — common in print.\n- **1.5** (Perfect Fifth) — bold, feels like a magazine layout.\n- **1.618** (Golden Ratio) — dramatic, marketing\u002Fhero scale.\n\nPick *one* ratio per project. Mixing ratios across sizes destroys the rhythm.\n\nA worked scale at base 16px and ratio 1.25:\n\n```\ncaption  10.24 px   (16 \u002F 1.25 \u002F 1.25)\nbody-sm  12.80 px   (16 \u002F 1.25)\nbody     16.00 px   (base)\nbody-lg  20.00 px   (16 * 1.25)\nh4       25.00 px   (16 * 1.25^2)\nh3       31.25 px   (16 * 1.25^3)\nh2       39.06 px   (16 * 1.25^4)\nh1       48.83 px   (16 * 1.25^5)\ndisplay  61.04 px   (16 * 1.25^6)\n```\n\nRounded to friendly numbers (10, 13, 16, 20, 25, 31, 39, 49, 61), this gives you a 9-step ladder with consistent visual jumps between any two adjacent steps.\n\n### Use weight as a second axis\n\nSize alone is enough for hierarchy in body-vs.-heading contexts but is a blunt tool when you need fine distinctions. Weight gives you a second axis. A useful weight ladder:\n\n```\nhairline \u002F thin    100   — display only, never body\nlight              300   — large display sizes; never small\nregular            400   — body\nmedium             500   — UI labels, buttons\nsemibold           600   — headings, emphasis\nbold               700   — strong emphasis, heavy display\nblack              900   — display only\n```\n\nMost software UIs need only three weights: regular (400), medium (500), and semibold (600). Reach for bolder weights only at display sizes; bold at body size is hard to read.\n\n### Combine size and weight, don't trade them\n\nA common mistake is treating size *or* weight as the hierarchy signal. They compound:\n\n- A 24px-semibold heading reads as much higher in the hierarchy than a 24px-regular heading, even though the size is identical.\n- A 16px-regular body paragraph and a 16px-medium label are perceived as different ranks despite identical size.\n\nWhen constructing a step in your hierarchy, *both* dial up: bigger headings should also be bolder. The exception is display type (very large), which often *decreases* in weight at the largest sizes (light or regular at 60px+ reads as elegant; black at 60px+ reads as shouting).\n\n### Line height (leading) is part of the system\n\nTighter leading (1.1–1.25) suits display and headings. Looser leading (1.5–1.75) suits body. Mismatch a heading with body leading (1.5) and the heading feels droopy; mismatch a body with display leading (1.2) and reading becomes hard.\n\nA workable mapping:\n\n```\ndisplay, h1, h2:   line-height 1.1–1.25\nh3, h4:            line-height 1.25–1.4\nbody, body-lg:     line-height 1.5–1.75\nbody-sm, caption:  line-height 1.4–1.6\n```\n\n### Line length (measure)\n\nFor sustained reading, constrain body text to roughly 45–75 characters per line (≈ 65ch is a common default). Longer lines fatigue eye-tracking; shorter lines fragment thought. Headings can be wider; captions and labels can be tighter.\n\n```css\n.body-text { max-width: 65ch; }\n```\n\n### Tracking (letter-spacing)\n\nGenerally leave tracking alone. Two cases where it earns adjustment:\n\n- **All-caps labels and small caps:** add ~0.04–0.08em of tracking; they read tightly otherwise.\n- **Very large display type:** subtract a small amount (-0.01 to -0.02em); large type looks loose without it.\n\n## Worked example: a complete typographic hierarchy in CSS\n\n```css\n:root {\n  \u002F* Type scale at ratio 1.25, base 16px *\u002F\n  --text-caption: 0.64rem;   \u002F* 10.24 *\u002F\n  --text-sm:      0.80rem;   \u002F* 12.80 *\u002F\n  --text-base:    1.00rem;   \u002F* 16.00 *\u002F\n  --text-lg:      1.25rem;   \u002F* 20.00 *\u002F\n  --text-xl:      1.563rem;  \u002F* 25.00 *\u002F\n  --text-2xl:     1.953rem;  \u002F* 31.25 *\u002F\n  --text-3xl:     2.441rem;  \u002F* 39.06 *\u002F\n  --text-4xl:     3.052rem;  \u002F* 48.83 *\u002F\n  --text-display: 3.815rem;  \u002F* 61.04 *\u002F\n\n  \u002F* Weight ladder *\u002F\n  --weight-body:     400;\n  --weight-label:    500;\n  --weight-emphasis: 600;\n  --weight-display:  700;\n\n  \u002F* Leading *\u002F\n  --leading-display: 1.1;\n  --leading-heading: 1.25;\n  --leading-body:    1.6;\n  --leading-tight:   1.4;\n}\n\n.display {\n  font-size: var(--text-display);\n  font-weight: 400;          \u002F* display gets lighter weight, paradoxically *\u002F\n  line-height: var(--leading-display);\n  letter-spacing: -0.02em;\n}\nh1 {\n  font-size: var(--text-3xl);\n  font-weight: var(--weight-emphasis);\n  line-height: var(--leading-heading);\n  letter-spacing: -0.01em;\n}\nh2 {\n  font-size: var(--text-2xl);\n  font-weight: var(--weight-emphasis);\n  line-height: var(--leading-heading);\n}\nh3 {\n  font-size: var(--text-xl);\n  font-weight: var(--weight-emphasis);\n  line-height: var(--leading-heading);\n}\nh4 {\n  font-size: var(--text-lg);\n  font-weight: var(--weight-label);\n  line-height: var(--leading-heading);\n}\nbody, p {\n  font-size: var(--text-base);\n  font-weight: var(--weight-body);\n  line-height: var(--leading-body);\n  max-width: 65ch;\n}\n.label, button, .ui-control {\n  font-size: var(--text-sm);\n  font-weight: var(--weight-label);\n  line-height: var(--leading-tight);\n}\n.caption, small, .micro {\n  font-size: var(--text-caption);\n  font-weight: var(--weight-body);\n  line-height: var(--leading-tight);\n  color: rgb(0 0 0 \u002F 0.55);   \u002F* tone reduction adds tertiary recession *\u002F\n}\n```\n\nEight clear ranks, all derived from one ratio, three weights, three leading values, and one tone reduction at the very bottom. This is enough hierarchy to handle any UI or content surface.\n\n## Anti-patterns\n\n- **Random sizing.** \"Make this 18px\" \u002F \"this 19px\" \u002F \"this 22px\" — close-but-not-equal sizes look like accidents. If two things should be the same rank, give them the same size; if different ranks, make the difference clear.\n- **Bold everything.** When every label, every heading, and every value is bold, none of them read as emphasized. Reserve bold for one or two roles.\n- **Gigantic body type.** Body text larger than ~18–20px starts to feel like a slide deck. Reserve large type for headings; keep body in the 14–18px range.\n- **Tiny captions.** Below 11px, anti-aliasing destroys legibility. If you find yourself reaching for 9px or 10px, you have too much content for the space — cut content rather than shrink type.\n- **Inconsistent weight per role.** \"Card titles are semibold here, medium there.\" Decide once per role.\n\n## Heuristics\n\n1. **Print-test.** Print the page in grayscale on regular paper. Hierarchy that survives this test is robust. Hierarchy that requires color or screen brightness is fragile.\n2. **Three-rank squint.** Squint until detail blurs. You should still see a primary tier, a secondary tier, and a recessive tier. If everything is one tone of grey, hierarchy is too flat.\n3. **The body-only test.** Hide all headings; the body should still feel like prose, not a wall. If it feels like a wall, your `max-width` or leading is wrong.\n\n## Related principles\n\n- **`hierarchy`** — the parent skill. Read it for the full framing.\n- **`hierarchy-spatial`** — when type alone isn't enough, spatial hierarchy carries the rest.\n- **`hierarchy-color-and-tone`** — color and tone as a third axis on top of size+weight.\n- **`legibility`** and **`readability`** — the typeface- and layout-side of typography that hierarchy depends on.\n- **`signal-to-noise-ratio`** — too many active ranks reduces SNR; restraint multiplies the effect of each rank.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-typographic",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hierarchy-typographic",{"tool":64,"command":65},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hierarchy-typographic",{"tool":67,"command":68},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill hierarchy-typographic","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-typographic\u002FSKILL.md",true,[72],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Ftype-scale-and-history.md","REFERENCE","参考文档",6403,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fhierarchy-typographic\u002Freferences\u002Ftype-scale-and-history.md",[79,89,97,105,113,121],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":88},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":88},"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":88},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":88},"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":88},"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":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":88},"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",[],[]]