[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWD6GSTTS11J35K4KXGS9R":3,"skill-same:01M6JWD6GSTTS11J35K4KXGS9R":76},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JWD6GSTTS11J35K4KXGS9R","legibility-contrast-and-spacing",null,"Apply contrast and spacing for legibility — calibrating color contrast between text and background, character tracking, and line leading so a chosen typeface and size actually render legibly. Use when picking text colors, choosing background colors that will carry text, evaluating accessibility against WCAG, fine-tuning typography for production rendering, or auditing why text \"looks designed\" but is hard to read. Even a perfect typeface at the right size will fail if contrast is too low, tracking too tight, or leading too cramped.","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\u002Flegibility-contrast-and-spacing\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"legibility","legibility contrast and spacing","contrast","spacing","color","when","for","at","size","render","rendering","Fine-Tuning","line","but","character","typography","use","read","text","why","WCAG","tuning","2026-11-10 10:12:30",false,"---\nname: legibility-contrast-and-spacing\ndescription: 'Apply contrast and spacing for legibility — calibrating color contrast between text and background, character tracking, and line leading so a chosen typeface and size actually render legibly. Use when picking text colors, choosing background colors that will carry text, evaluating accessibility against WCAG, fine-tuning typography for production rendering, or auditing why text \"looks designed\" but is hard to read. Even a perfect typeface at the right size will fail if contrast is too low, tracking too tight, or leading too cramped.'\n---\n\n# Legibility — contrast and spacing\n\nA typeface and size are necessary but not sufficient for legibility. The conditions under which type is rendered — contrast against background, spacing between characters, spacing between lines — determine whether the chosen typography actually communicates. Most legibility failures in production are spacing or contrast failures, not typeface failures.\n\n## Color contrast\n\nColor contrast is the difference in luminance between text and its background. WCAG codifies minimum thresholds:\n\n- **4.5:1** for normal text (under 18pt regular or 14pt bold).\n- **3:1** for large text (18pt+ regular or 14pt+ bold).\n- **3:1** for graphical objects and UI components (icons, button outlines).\n- **7:1** for AAA conformance — recommended for users with low vision or in poor viewing conditions.\n\nThese are floors, not targets. Best practice is to substantially exceed them where possible.\n\nCommon contrast failures:\n\n**Light gray text on white.** Common because designers like the \"soft\" feel. #999 on white is roughly 2.8:1, well below WCAG AA. #767676 is roughly 4.5:1. Below this, you're failing the standard.\n\n**Brand color on white that doesn't pass.** A brand color in the medium-blue range (e.g., #5BA0E6) on white is often around 3:1 — fine for large display text, fails for body text. Pick text colors with adequate contrast even if the brand color is borderline.\n\n**Text on photos or gradients without protection.** Text overlaid on busy photos or gradients can fail in some places and pass in others. Solutions: a dark scrim over the photo, a solid text background, or moving the text out of the photo area.\n\n**Low-contrast helper or muted text.** Helper text intentionally de-emphasized often drifts into illegibility. Don't go below 4.5:1 (or 3:1 if it's larger text and clearly secondary).\n\n**Color-only state indicators.** A red error message that loses meaning when rendered to a colorblind user, or a green success message that's invisible to others. Always pair color with shape, label, or icon.\n\nTools for verifying contrast:\n\n- WebAIM contrast checker.\n- Browser dev tools' built-in contrast picker.\n- axe, Lighthouse, WAVE for automated audits.\n- Stark or similar Figma\u002FSketch plugins for design-time checking.\n\n## Tracking (letter spacing)\n\nTracking is the space between characters. The right tracking depends on the typeface, the size, and the use.\n\n**Body text:** typefaces are usually designed for body sizes with built-in correct tracking. Don't adjust tracking for body unless you have a specific reason.\n\n**Display sizes (large):** large text often benefits from tighter tracking (-1% to -2%) to prevent characters from feeling too far apart. Many display typefaces are designed expecting some negative tracking at large sizes.\n\n**Small sizes (especially below 12px):** small text may need slightly looser tracking (+0.5% to +1%) to prevent characters from merging into ambiguous shapes.\n\n**All caps:** uppercase text needs significantly looser tracking (+5% to +10%) because capital letters have less visual differentiation in their outlines.\n\n**Bold text:** can sometimes need slightly looser tracking to prevent visual crowding.\n\nCommon tracking failures:\n\n**Default tracking on display sizes.** Many typefaces look loose at large sizes; tighten to -1% to -3%.\n\n**Tight tracking on small text.** A common cause of \"blurry-looking\" small text. Loosen slightly.\n\n**Untracked all-caps.** Uppercase without extra tracking looks crowded and reads slowly.\n\n## Leading (line height)\n\nLeading is the space between lines. The right leading depends on the typeface, the line length, and the use.\n\n**Body text:** 1.4× to 1.6× the font size. So for 16px text, line height of 22–26px. This range is comfortable for sustained reading.\n\n**Display \u002F headline text:** 1.0× to 1.2× the font size. Tighter leading at display sizes prevents headlines from feeling fragmented.\n\n**UI labels and dense text:** 1.2× to 1.4× the font size. Tighter than body but loose enough to keep characters from overlapping.\n\n**Long-form prose:** 1.5× to 1.7× the font size. Slightly more generous than UI body text for sustained reading comfort.\n\nCommon leading failures:\n\n**Default browser leading on body text.** Browsers default to about 1.2× line height, which is too tight for body text. Set explicit line-height: 1.5 or higher for prose.\n\n**Leading too tight for the font's x-height.** Fonts with tall x-heights (Verdana, Inter) need slightly more leading than fonts with shorter x-heights (Times, Garamond) at the same size.\n\n**Inconsistent leading across the type system.** Body, headings, captions all should have leading that's calibrated to their use; one-size-fits-all is rarely right.\n\n**Tight leading on multi-line UI elements.** Buttons, table cells, form labels with multiple lines often have insufficient line height, causing the lines to crowd.\n\n## Word spacing and paragraph spacing\n\nLess critical than tracking and leading for most UI but worth checking:\n\n**Word spacing.** Default word spacing in most typefaces is appropriate. Adjust only for specific cases (justified text, very large display).\n\n**Paragraph spacing.** Space between paragraphs should be larger than line spacing. A common ratio: paragraph spacing = 0.75× to 1× the font size, in addition to leading.\n\n**First-line indent vs. block paragraphs.** Most digital UI uses block paragraphs with space between. First-line indents are reserved for editorial \u002F book contexts.\n\n## Worked examples\n\n### A button that fails contrast\n\nA button with white text (#FFFFFF) on a light blue background (#7AB8FF). Contrast ratio: 2.1:1. Below WCAG AA for both normal and large text.\n\nThe fix: darken the blue (#1E78D6 gives 4.5:1) or change the text to a darker color. White on the original blue is too low contrast for accessibility.\n\n### Body text with too-tight leading\n\nDefault browser styling: 16px body text with default line-height (about 1.2 = 19px). The text feels cramped; users skim faster than they should and miss content.\n\nThe fix: set line-height to 1.5 or higher for body text. 24px line height for 16px text is a comfortable baseline for sustained reading.\n\n### A headline with too-loose tracking\n\nA 48px display headline using a typeface with default (positive) tracking. The letters feel separated; the headline doesn't read as a unit.\n\nThe fix: tighten tracking to -1% or -2% at this size. The headline now reads as a cohesive title rather than as separate letters.\n\n### All-caps navigation that's hard to read\n\nA navigation bar uses ALL CAPS labels at 13px with default tracking. The text feels crowded and reads slowly because all-caps lacks the ascender\u002Fdescender silhouette that aids word recognition.\n\nThe fix: add positive tracking (+5% to +8%) to give the capitals room to breathe; consider whether all-caps is necessary at all (sentence-case or title-case is usually more readable).\n\n### Helper text that drifts into illegibility\n\nHelper text under form fields is set in #BBBBBB on white. Contrast ratio: 1.6:1. Many users can't read it at all; even those who can, struggle.\n\nThe fix: darken to #767676 or similar (gives 4.5:1). The helper text remains clearly secondary but is now legible.\n\n### Code that's hard to scan\n\nCode blocks in a documentation site use a serif typeface at 14px with default tracking and line-height. The text is technically legible but feels dense and hard to scan.\n\nThe fix: switch to a monospace typeface (JetBrains Mono or similar), set line-height to 1.6 (a bit more generous than body for visual scanning), and add some background tinting to set code apart from prose.\n\n## Anti-patterns\n\n**Designing on high-contrast displays then shipping to low-contrast contexts.** Mobile devices in sunlight, lower-DPI external monitors, projectors all reduce effective contrast. Test in the worst conditions you'll actually encounter.\n\n**Using opacity for text instead of explicit colors.** A semi-transparent black text on a colored background can produce unpredictable contrast depending on the underlying color. Use explicit colors, computed against the actual background.\n\n**Ignoring user-chosen color schemes.** Dark mode, high-contrast mode, and user-overridden colors all change the effective contrast. Test your typography in all the modes your users will use.\n\n**Tracking adjustments without testing.** Tracking is sensitive to typeface and size. A -2% adjustment that improves a 48px headline may break a 14px body. Calibrate each adjustment to its specific use.\n\n**Set-and-forget design tokens for typography.** Typography tokens that haven't been audited in years often drift away from current best practices. Review your typography system periodically.\n\n**Relying on automated contrast checkers without visual review.** Automated tools catch the most obvious failures but miss situations like text over photos, gradient backgrounds, or color combinations that pass technically but feel low-contrast.\n\n## Heuristic checklist\n\nBefore shipping any typography decision, ask: **Does the contrast meet WCAG AA at minimum (4.5:1 normal, 3:1 large)?** Check with a contrast tool. **Does the contrast hold up in dark mode?** Test both modes. **Is the leading appropriate for the use case?** 1.5× for body, 1.2× for display. **Is the tracking appropriate for size and case?** Tighter for display, looser for small or all-caps. **Have you tested in production conditions?** Actual devices, actual browsers, actual viewing conditions.\n\n## Related sub-skills\n\n- `legibility` — parent principle on visual character clarity.\n- `legibility-typeface-and-size` — sibling skill on typeface and size choices.\n- `color` — color choices that affect contrast.\n- `accessibility` — contrast is one critical accessibility dimension.\n- `signal-to-noise` — well-spaced, high-contrast type is signal; the opposite is noise.\n\n## See also\n\n- `references\u002Fcontrast-spacing-recipes.md` — specific recipes for common situations (light mode, dark mode, hero text, code, captions).\n","# Legibility — contrast and spacing\n\nA typeface and size are necessary but not sufficient for legibility. The conditions under which type is rendered — contrast against background, spacing between characters, spacing between lines — determine whether the chosen typography actually communicates. Most legibility failures in production are spacing or contrast failures, not typeface failures.\n\n## Color contrast\n\nColor contrast is the difference in luminance between text and its background. WCAG codifies minimum thresholds:\n\n- **4.5:1** for normal text (under 18pt regular or 14pt bold).\n- **3:1** for large text (18pt+ regular or 14pt+ bold).\n- **3:1** for graphical objects and UI components (icons, button outlines).\n- **7:1** for AAA conformance — recommended for users with low vision or in poor viewing conditions.\n\nThese are floors, not targets. Best practice is to substantially exceed them where possible.\n\nCommon contrast failures:\n\n**Light gray text on white.** Common because designers like the \"soft\" feel. #999 on white is roughly 2.8:1, well below WCAG AA. #767676 is roughly 4.5:1. Below this, you're failing the standard.\n\n**Brand color on white that doesn't pass.** A brand color in the medium-blue range (e.g., #5BA0E6) on white is often around 3:1 — fine for large display text, fails for body text. Pick text colors with adequate contrast even if the brand color is borderline.\n\n**Text on photos or gradients without protection.** Text overlaid on busy photos or gradients can fail in some places and pass in others. Solutions: a dark scrim over the photo, a solid text background, or moving the text out of the photo area.\n\n**Low-contrast helper or muted text.** Helper text intentionally de-emphasized often drifts into illegibility. Don't go below 4.5:1 (or 3:1 if it's larger text and clearly secondary).\n\n**Color-only state indicators.** A red error message that loses meaning when rendered to a colorblind user, or a green success message that's invisible to others. Always pair color with shape, label, or icon.\n\nTools for verifying contrast:\n\n- WebAIM contrast checker.\n- Browser dev tools' built-in contrast picker.\n- axe, Lighthouse, WAVE for automated audits.\n- Stark or similar Figma\u002FSketch plugins for design-time checking.\n\n## Tracking (letter spacing)\n\nTracking is the space between characters. The right tracking depends on the typeface, the size, and the use.\n\n**Body text:** typefaces are usually designed for body sizes with built-in correct tracking. Don't adjust tracking for body unless you have a specific reason.\n\n**Display sizes (large):** large text often benefits from tighter tracking (-1% to -2%) to prevent characters from feeling too far apart. Many display typefaces are designed expecting some negative tracking at large sizes.\n\n**Small sizes (especially below 12px):** small text may need slightly looser tracking (+0.5% to +1%) to prevent characters from merging into ambiguous shapes.\n\n**All caps:** uppercase text needs significantly looser tracking (+5% to +10%) because capital letters have less visual differentiation in their outlines.\n\n**Bold text:** can sometimes need slightly looser tracking to prevent visual crowding.\n\nCommon tracking failures:\n\n**Default tracking on display sizes.** Many typefaces look loose at large sizes; tighten to -1% to -3%.\n\n**Tight tracking on small text.** A common cause of \"blurry-looking\" small text. Loosen slightly.\n\n**Untracked all-caps.** Uppercase without extra tracking looks crowded and reads slowly.\n\n## Leading (line height)\n\nLeading is the space between lines. The right leading depends on the typeface, the line length, and the use.\n\n**Body text:** 1.4× to 1.6× the font size. So for 16px text, line height of 22–26px. This range is comfortable for sustained reading.\n\n**Display \u002F headline text:** 1.0× to 1.2× the font size. Tighter leading at display sizes prevents headlines from feeling fragmented.\n\n**UI labels and dense text:** 1.2× to 1.4× the font size. Tighter than body but loose enough to keep characters from overlapping.\n\n**Long-form prose:** 1.5× to 1.7× the font size. Slightly more generous than UI body text for sustained reading comfort.\n\nCommon leading failures:\n\n**Default browser leading on body text.** Browsers default to about 1.2× line height, which is too tight for body text. Set explicit line-height: 1.5 or higher for prose.\n\n**Leading too tight for the font's x-height.** Fonts with tall x-heights (Verdana, Inter) need slightly more leading than fonts with shorter x-heights (Times, Garamond) at the same size.\n\n**Inconsistent leading across the type system.** Body, headings, captions all should have leading that's calibrated to their use; one-size-fits-all is rarely right.\n\n**Tight leading on multi-line UI elements.** Buttons, table cells, form labels with multiple lines often have insufficient line height, causing the lines to crowd.\n\n## Word spacing and paragraph spacing\n\nLess critical than tracking and leading for most UI but worth checking:\n\n**Word spacing.** Default word spacing in most typefaces is appropriate. Adjust only for specific cases (justified text, very large display).\n\n**Paragraph spacing.** Space between paragraphs should be larger than line spacing. A common ratio: paragraph spacing = 0.75× to 1× the font size, in addition to leading.\n\n**First-line indent vs. block paragraphs.** Most digital UI uses block paragraphs with space between. First-line indents are reserved for editorial \u002F book contexts.\n\n## Worked examples\n\n### A button that fails contrast\n\nA button with white text (#FFFFFF) on a light blue background (#7AB8FF). Contrast ratio: 2.1:1. Below WCAG AA for both normal and large text.\n\nThe fix: darken the blue (#1E78D6 gives 4.5:1) or change the text to a darker color. White on the original blue is too low contrast for accessibility.\n\n### Body text with too-tight leading\n\nDefault browser styling: 16px body text with default line-height (about 1.2 = 19px). The text feels cramped; users skim faster than they should and miss content.\n\nThe fix: set line-height to 1.5 or higher for body text. 24px line height for 16px text is a comfortable baseline for sustained reading.\n\n### A headline with too-loose tracking\n\nA 48px display headline using a typeface with default (positive) tracking. The letters feel separated; the headline doesn't read as a unit.\n\nThe fix: tighten tracking to -1% or -2% at this size. The headline now reads as a cohesive title rather than as separate letters.\n\n### All-caps navigation that's hard to read\n\nA navigation bar uses ALL CAPS labels at 13px with default tracking. The text feels crowded and reads slowly because all-caps lacks the ascender\u002Fdescender silhouette that aids word recognition.\n\nThe fix: add positive tracking (+5% to +8%) to give the capitals room to breathe; consider whether all-caps is necessary at all (sentence-case or title-case is usually more readable).\n\n### Helper text that drifts into illegibility\n\nHelper text under form fields is set in #BBBBBB on white. Contrast ratio: 1.6:1. Many users can't read it at all; even those who can, struggle.\n\nThe fix: darken to #767676 or similar (gives 4.5:1). The helper text remains clearly secondary but is now legible.\n\n### Code that's hard to scan\n\nCode blocks in a documentation site use a serif typeface at 14px with default tracking and line-height. The text is technically legible but feels dense and hard to scan.\n\nThe fix: switch to a monospace typeface (JetBrains Mono or similar), set line-height to 1.6 (a bit more generous than body for visual scanning), and add some background tinting to set code apart from prose.\n\n## Anti-patterns\n\n**Designing on high-contrast displays then shipping to low-contrast contexts.** Mobile devices in sunlight, lower-DPI external monitors, projectors all reduce effective contrast. Test in the worst conditions you'll actually encounter.\n\n**Using opacity for text instead of explicit colors.** A semi-transparent black text on a colored background can produce unpredictable contrast depending on the underlying color. Use explicit colors, computed against the actual background.\n\n**Ignoring user-chosen color schemes.** Dark mode, high-contrast mode, and user-overridden colors all change the effective contrast. Test your typography in all the modes your users will use.\n\n**Tracking adjustments without testing.** Tracking is sensitive to typeface and size. A -2% adjustment that improves a 48px headline may break a 14px body. Calibrate each adjustment to its specific use.\n\n**Set-and-forget design tokens for typography.** Typography tokens that haven't been audited in years often drift away from current best practices. Review your typography system periodically.\n\n**Relying on automated contrast checkers without visual review.** Automated tools catch the most obvious failures but miss situations like text over photos, gradient backgrounds, or color combinations that pass technically but feel low-contrast.\n\n## Heuristic checklist\n\nBefore shipping any typography decision, ask: **Does the contrast meet WCAG AA at minimum (4.5:1 normal, 3:1 large)?** Check with a contrast tool. **Does the contrast hold up in dark mode?** Test both modes. **Is the leading appropriate for the use case?** 1.5× for body, 1.2× for display. **Is the tracking appropriate for size and case?** Tighter for display, looser for small or all-caps. **Have you tested in production conditions?** Actual devices, actual browsers, actual viewing conditions.\n\n## Related sub-skills\n\n- `legibility` — parent principle on visual character clarity.\n- `legibility-typeface-and-size` — sibling skill on typeface and size choices.\n- `color` — color choices that affect contrast.\n- `accessibility` — contrast is one critical accessibility dimension.\n- `signal-to-noise` — well-spaced, high-contrast type is signal; the opposite is noise.\n\n## See also\n\n- `references\u002Fcontrast-spacing-recipes.md` — specific recipes for common situations (light mode, dark mode, hero text, code, captions).\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Flegibility-contrast-and-spacing",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill legibility-contrast-and-spacing",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill legibility-contrast-and-spacing",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill legibility-contrast-and-spacing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Flegibility-contrast-and-spacing\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fcontrast-spacing-recipes.md","REFERENCE","参考文档",7047,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Flegibility-contrast-and-spacing\u002Freferences\u002Fcontrast-spacing-recipes.md",[77,87,95,103,111,119],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":86},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":86},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":86},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":86},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":86},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":86},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]