[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JWDWK5DNXM5452WK538YYW":3,"skill-same:01M6JWDWK5DNXM5452WK538YYW":80},{"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":45,"linkOnly":46,"markdownContent":47,"markdownBody":48,"frontMatter":49,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6JWDWK5DNXM5452WK538YYW","proximity-data-tables",null,"Use this skill when designing or fixing data tables and tabular layouts — row spacing, column spacing, header treatment, group separators, total rows, sticky headers, dense vs. comfortable variants. Trigger when the user is laying out a table, deciding density, debugging \"rows that are hard to follow,\" picking when to add zebra striping, or arguing for\u002Fagainst borders. Sub-aspect of `proximity`; 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\u002Fproximity-data-tables\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44],"data","proximity","proximity data tables","tables","when","debugging","tabular","sticky","variants","for","spacing","headers","you","add","trigger","column","use","user","read","table","first","2026-11-10 10:12:30",false,"---\nname: proximity-data-tables\ndescription: 'Use this skill when designing or fixing data tables and tabular layouts — row spacing, column spacing, header treatment, group separators, total rows, sticky headers, dense vs. comfortable variants. Trigger when the user is laying out a table, deciding density, debugging \"rows that are hard to follow,\" picking when to add zebra striping, or arguing for\u002Fagainst borders. Sub-aspect of `proximity`; read that first if you haven''t already.'\n---\n\n# Proximity in data tables\n\nTables stress proximity in two directions at once: rows should read as discrete records (vertical proximity binding cells of the same row, separating them from cells of neighbor rows), and columns should read as semantic groupings (horizontal proximity within a column header, between header and cells). Most table problems are proximity problems disguised as styling problems.\n\n## The two-axis proximity ladder\n\nIn a table, you're managing two perpendicular spacing systems:\n\n```\nVertical:\n  Inside a row (cell padding)        — ~12-16px\n  Between rows                       — ~0 (or thin border for separation)\n  Header to first row                — slightly more than between rows\n  Footer \u002F total row                 — distinctly more than between rows\n\nHorizontal:\n  Within a cell (text to edge)       — ~12-16px\n  Between columns                    — ~0 (cell border or just padding)\n  Numeric columns: tabular-nums + right alignment for column-internal proximity\n```\n\nThe classic mistake is uniform padding everywhere — every gap the same — so the eye can't tell rows from columns from groups.\n\n## Dense vs. comfortable variants\n\nTables come in two density modes; pick deliberately:\n\n```\nComfortable (default for most apps):\n  Cell padding:  py-3 px-4   (12px \u002F 16px)\n  Row height:    ~48px\n  Best for:      moderate datasets, mixed user proficiency\n\nDense (power-user \u002F spreadsheet-like):\n  Cell padding:  py-1.5 px-3  (6px \u002F 12px)\n  Row height:    ~32px\n  Best for:      high-frequency scanning, expert users, datasets >50 rows visible\n```\n\nDon't mix densities in the same table. Don't try to be \"compact but readable\" with mid-sized padding — it ends up neither dense enough for power users nor comfortable enough for casual ones.\n\n## Header proximity\n\nThe header should bind to its column (vertically tight to the column it labels) but separate clearly from the data rows.\n\n```html\n\u003Cstyle>\n  .table { width: 100%; border-collapse: collapse; }\n  .table th, .table td { padding: 0.75rem 1rem; text-align: left; }\n  .table th {\n    font-size: 0.75rem;\n    font-weight: 600;\n    color: hsl(0 0% 35%);\n    text-transform: uppercase;\n    letter-spacing: 0.04em;\n    border-bottom: 1px solid hsl(0 0% 88%);   \u002F* separates header from data *\u002F\n    padding-bottom: 0.5rem;                    \u002F* tighter to the underline *\u002F\n  }\n  .table td { border-bottom: 1px solid hsl(0 0% 95%); }   \u002F* very subtle row separator *\u002F\n  .table tbody tr:hover { background: hsl(0 0% 98%); }\n\u003C\u002Fstyle>\n\n\u003Ctable class=\"table\">\n  \u003Cthead>\n    \u003Ctr>\n      \u003Cth>Customer\u003C\u002Fth>\n      \u003Cth style=\"text-align: right;\">Amount\u003C\u002Fth>\n      \u003Cth style=\"text-align: right;\">Days late\u003C\u002Fth>\n      \u003Cth>Status\u003C\u002Fth>\n    \u003C\u002Ftr>\n  \u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr>\n      \u003Ctd>Acme Co.\u003C\u002Ftd>\n      \u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$2,480.00\u003C\u002Ftd>\n      \u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">14\u003C\u002Ftd>\n      \u003Ctd>\u003Cspan class=\"badge badge-warning\">Pending\u003C\u002Fspan>\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003C!-- … -->\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n```\n\nThe header sits in its own row, visually distinct (smaller, uppercase, lower contrast, with a stronger underline). Data rows have a subtle hairline separator that suggests row boundaries without dominating.\n\n## Numeric column proximity\n\nNumbers in a column should align *within the column*, so the eye can scan vertically and compare magnitudes:\n\n- **Right-align** numeric columns. Left-aligned numbers don't compare.\n- **Tabular nums** (`font-variant-numeric: tabular-nums`) so digits occupy equal width. Without this, \"1,000\" and \"9,999\" don't align by digit position.\n- **Same number of decimals** in every cell of a column. \"$2.5\", \"$10.00\", \"$1,200\" don't align. Pick a precision and stick to it.\n\n```html\n\u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$2,480.00\u003C\u002Ftd>\n\u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$10.00\u003C\u002Ftd>\n\u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$98,001.50\u003C\u002Ftd>\n```\n\nNow the eye can scan the column and see magnitude differences instantly.\n\n## Group separators\n\nWhen rows belong to logical groups (orders by month, projects by team, transactions by status), encode the grouping with a *visible gap* and an optional sub-header — not by adding a heavy border:\n\n```html\n\u003Ctable class=\"table\">\n  \u003Cthead>…\u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr class=\"group-header\">\n      \u003Ctd colspan=\"4\">May 2026\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n\n    \u003Ctr class=\"group-header\">\n      \u003Ctd colspan=\"4\">April 2026\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Cstyle>\n  .group-header td {\n    font-size: 0.75rem;\n    font-weight: 600;\n    color: hsl(0 0% 35%);\n    background: hsl(0 0% 97%);\n    padding-top: 1rem;        \u002F* extra space above this row separates groups *\u002F\n    padding-bottom: 0.5rem;\n  }\n\u003C\u002Fstyle>\n```\n\nThe extra top padding on group headers creates a perceptual gap; the slight background tint reinforces it. The user reads months as groups, transactions as group members.\n\n## Total \u002F summary rows\n\nTotal rows should bind to the data they summarize (close vertically) and stand out from regular rows (heavier weight, possibly a top border):\n\n```html\n\u003Ctfoot>\n  \u003Ctr style=\"font-weight: 600; border-top: 2px solid hsl(0 0% 88%);\">\n    \u003Ctd>Total\u003C\u002Ftd>\n    \u003Ctd colspan=\"2\" style=\"text-align: right; font-variant-numeric: tabular-nums;\">$24,800.00\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n  \u003C\u002Ftr>\n\u003C\u002Ftfoot>\n```\n\nThe 2px top border separates the summary from data rows. Bold weight signals \"this is summary, not a regular row.\" Same column alignment as the data above.\n\n## Zebra striping (alternating row backgrounds)\n\nUse sparingly. Zebra striping helps the eye track across very wide rows (~7+ columns) but adds visual noise to compact tables.\n\n- **Use it**: wide tables, many columns, where the user must trace a single row across.\n- **Skip it**: 3–5 column tables where row tracking isn't a problem; a hover background is enough.\n- **Make it subtle**: `hsl(0 0% 98%)` against white — visible but not distracting. Anything stronger competes with the data.\n\n## Anti-patterns\n\n- **Heavy borders everywhere.** Every cell bordered, every row separated, every column ruled. The page becomes a grid prison; data drowns in chrome. Strip borders; let alignment and subtle separation do the work.\n- **Equal padding top and bottom on rows.** With no row separator and equal padding, rows blur into a wall of text. Add either a hairline separator or a slight row-zebra.\n- **Numeric and text columns aligned the same way.** Numbers left-aligned mean the eye can't compare magnitudes; text right-aligned means the eye can't follow words.\n- **Inconsistent decimal precision.** One column shows \"$2\", \"$2.5\", \"$2.50\", \"$2.501\" — eye scan fails. Pick a precision per column.\n- **Sticky header with no separator.** Sticky headers that float over scrolling data without a clear border merge into the data; users don't realize what's a header.\n\n## Heuristics\n\n1. **The single-finger trace.** Can you trace any row with one finger from left to right without losing your place? If not, row separation is too weak (or the row is too tall).\n2. **The numeric-column scan.** Look down a numeric column. Can you spot the largest value at a glance? If not, alignment or tabular-nums is missing.\n3. **Strip the chrome.** Mentally remove every border and background. Does the table still parse? If yes, your chrome is doing redundant work; trim it.\n\n## Related sub-skills\n\n- **`proximity`** (parent).\n- **`proximity-form-fields`** — same principle on input layouts.\n- **`hierarchy-typographic`** — header styling lives at the intersection of hierarchy and proximity.\n- **`signal-to-noise-ratio`** — tables are a primary case for SNR discipline.\n- **`legibility`** — tabular numerals and alignment are legibility decisions as much as proximity ones.\n","# Proximity in data tables\n\nTables stress proximity in two directions at once: rows should read as discrete records (vertical proximity binding cells of the same row, separating them from cells of neighbor rows), and columns should read as semantic groupings (horizontal proximity within a column header, between header and cells). Most table problems are proximity problems disguised as styling problems.\n\n## The two-axis proximity ladder\n\nIn a table, you're managing two perpendicular spacing systems:\n\n```\nVertical:\n  Inside a row (cell padding)        — ~12-16px\n  Between rows                       — ~0 (or thin border for separation)\n  Header to first row                — slightly more than between rows\n  Footer \u002F total row                 — distinctly more than between rows\n\nHorizontal:\n  Within a cell (text to edge)       — ~12-16px\n  Between columns                    — ~0 (cell border or just padding)\n  Numeric columns: tabular-nums + right alignment for column-internal proximity\n```\n\nThe classic mistake is uniform padding everywhere — every gap the same — so the eye can't tell rows from columns from groups.\n\n## Dense vs. comfortable variants\n\nTables come in two density modes; pick deliberately:\n\n```\nComfortable (default for most apps):\n  Cell padding:  py-3 px-4   (12px \u002F 16px)\n  Row height:    ~48px\n  Best for:      moderate datasets, mixed user proficiency\n\nDense (power-user \u002F spreadsheet-like):\n  Cell padding:  py-1.5 px-3  (6px \u002F 12px)\n  Row height:    ~32px\n  Best for:      high-frequency scanning, expert users, datasets >50 rows visible\n```\n\nDon't mix densities in the same table. Don't try to be \"compact but readable\" with mid-sized padding — it ends up neither dense enough for power users nor comfortable enough for casual ones.\n\n## Header proximity\n\nThe header should bind to its column (vertically tight to the column it labels) but separate clearly from the data rows.\n\n```html\n\u003Cstyle>\n  .table { width: 100%; border-collapse: collapse; }\n  .table th, .table td { padding: 0.75rem 1rem; text-align: left; }\n  .table th {\n    font-size: 0.75rem;\n    font-weight: 600;\n    color: hsl(0 0% 35%);\n    text-transform: uppercase;\n    letter-spacing: 0.04em;\n    border-bottom: 1px solid hsl(0 0% 88%);   \u002F* separates header from data *\u002F\n    padding-bottom: 0.5rem;                    \u002F* tighter to the underline *\u002F\n  }\n  .table td { border-bottom: 1px solid hsl(0 0% 95%); }   \u002F* very subtle row separator *\u002F\n  .table tbody tr:hover { background: hsl(0 0% 98%); }\n\u003C\u002Fstyle>\n\n\u003Ctable class=\"table\">\n  \u003Cthead>\n    \u003Ctr>\n      \u003Cth>Customer\u003C\u002Fth>\n      \u003Cth style=\"text-align: right;\">Amount\u003C\u002Fth>\n      \u003Cth style=\"text-align: right;\">Days late\u003C\u002Fth>\n      \u003Cth>Status\u003C\u002Fth>\n    \u003C\u002Ftr>\n  \u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr>\n      \u003Ctd>Acme Co.\u003C\u002Ftd>\n      \u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$2,480.00\u003C\u002Ftd>\n      \u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">14\u003C\u002Ftd>\n      \u003Ctd>\u003Cspan class=\"badge badge-warning\">Pending\u003C\u002Fspan>\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003C!-- … -->\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n```\n\nThe header sits in its own row, visually distinct (smaller, uppercase, lower contrast, with a stronger underline). Data rows have a subtle hairline separator that suggests row boundaries without dominating.\n\n## Numeric column proximity\n\nNumbers in a column should align *within the column*, so the eye can scan vertically and compare magnitudes:\n\n- **Right-align** numeric columns. Left-aligned numbers don't compare.\n- **Tabular nums** (`font-variant-numeric: tabular-nums`) so digits occupy equal width. Without this, \"1,000\" and \"9,999\" don't align by digit position.\n- **Same number of decimals** in every cell of a column. \"$2.5\", \"$10.00\", \"$1,200\" don't align. Pick a precision and stick to it.\n\n```html\n\u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$2,480.00\u003C\u002Ftd>\n\u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$10.00\u003C\u002Ftd>\n\u003Ctd style=\"text-align: right; font-variant-numeric: tabular-nums;\">$98,001.50\u003C\u002Ftd>\n```\n\nNow the eye can scan the column and see magnitude differences instantly.\n\n## Group separators\n\nWhen rows belong to logical groups (orders by month, projects by team, transactions by status), encode the grouping with a *visible gap* and an optional sub-header — not by adding a heavy border:\n\n```html\n\u003Ctable class=\"table\">\n  \u003Cthead>…\u003C\u002Fthead>\n  \u003Ctbody>\n    \u003Ctr class=\"group-header\">\n      \u003Ctd colspan=\"4\">May 2026\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n\n    \u003Ctr class=\"group-header\">\n      \u003Ctd colspan=\"4\">April 2026\u003C\u002Ftd>\n    \u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n    \u003Ctr>\u003Ctd>…\u003C\u002Ftd>…\u003C\u002Ftr>\n  \u003C\u002Ftbody>\n\u003C\u002Ftable>\n\n\u003Cstyle>\n  .group-header td {\n    font-size: 0.75rem;\n    font-weight: 600;\n    color: hsl(0 0% 35%);\n    background: hsl(0 0% 97%);\n    padding-top: 1rem;        \u002F* extra space above this row separates groups *\u002F\n    padding-bottom: 0.5rem;\n  }\n\u003C\u002Fstyle>\n```\n\nThe extra top padding on group headers creates a perceptual gap; the slight background tint reinforces it. The user reads months as groups, transactions as group members.\n\n## Total \u002F summary rows\n\nTotal rows should bind to the data they summarize (close vertically) and stand out from regular rows (heavier weight, possibly a top border):\n\n```html\n\u003Ctfoot>\n  \u003Ctr style=\"font-weight: 600; border-top: 2px solid hsl(0 0% 88%);\">\n    \u003Ctd>Total\u003C\u002Ftd>\n    \u003Ctd colspan=\"2\" style=\"text-align: right; font-variant-numeric: tabular-nums;\">$24,800.00\u003C\u002Ftd>\n    \u003Ctd>\u003C\u002Ftd>\n  \u003C\u002Ftr>\n\u003C\u002Ftfoot>\n```\n\nThe 2px top border separates the summary from data rows. Bold weight signals \"this is summary, not a regular row.\" Same column alignment as the data above.\n\n## Zebra striping (alternating row backgrounds)\n\nUse sparingly. Zebra striping helps the eye track across very wide rows (~7+ columns) but adds visual noise to compact tables.\n\n- **Use it**: wide tables, many columns, where the user must trace a single row across.\n- **Skip it**: 3–5 column tables where row tracking isn't a problem; a hover background is enough.\n- **Make it subtle**: `hsl(0 0% 98%)` against white — visible but not distracting. Anything stronger competes with the data.\n\n## Anti-patterns\n\n- **Heavy borders everywhere.** Every cell bordered, every row separated, every column ruled. The page becomes a grid prison; data drowns in chrome. Strip borders; let alignment and subtle separation do the work.\n- **Equal padding top and bottom on rows.** With no row separator and equal padding, rows blur into a wall of text. Add either a hairline separator or a slight row-zebra.\n- **Numeric and text columns aligned the same way.** Numbers left-aligned mean the eye can't compare magnitudes; text right-aligned means the eye can't follow words.\n- **Inconsistent decimal precision.** One column shows \"$2\", \"$2.5\", \"$2.50\", \"$2.501\" — eye scan fails. Pick a precision per column.\n- **Sticky header with no separator.** Sticky headers that float over scrolling data without a clear border merge into the data; users don't realize what's a header.\n\n## Heuristics\n\n1. **The single-finger trace.** Can you trace any row with one finger from left to right without losing your place? If not, row separation is too weak (or the row is too tall).\n2. **The numeric-column scan.** Look down a numeric column. Can you spot the largest value at a glance? If not, alignment or tabular-nums is missing.\n3. **Strip the chrome.** Mentally remove every border and background. Does the table still parse? If yes, your chrome is doing redundant work; trim it.\n\n## Related sub-skills\n\n- **`proximity`** (parent).\n- **`proximity-form-fields`** — same principle on input layouts.\n- **`hierarchy-typographic`** — header styling lives at the intersection of hierarchy and proximity.\n- **`signal-to-noise-ratio`** — tables are a primary case for SNR discipline.\n- **`legibility`** — tabular numerals and alignment are legibility decisions as much as proximity ones.\n",{"name":5,"description":7},"main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fproximity-data-tables",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill proximity-data-tables",{"tool":66,"command":67},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill proximity-data-tables",{"tool":69,"command":70},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill proximity-data-tables","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fproximity-data-tables\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ftable-design-patterns.md","REFERENCE","参考文档",6192,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FHDeibler\u002Funiversal-design-principles\u002Fplugins\u002Fperception-and-hierarchy-principles\u002Fskills\u002Fproximity-data-tables\u002Freferences\u002Ftable-design-patterns.md",[81,91,99,107,115,123],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":90},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":90},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":90},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":119,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":90},"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":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":127,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":90},"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",[],[]]