agentleFS
npownpow/claude-skills/table/SKILL.md

table

Skill4 starsChanged 6 months agoApache-2.0View on GitHub

Renders interactive sortable, filterable tables in the browser using pure vanilla HTML/CSS/JS — no external dependencies. Use when the user wants to compare alternatives, show a feature matrix, display structured data, create a comparison table, render a sortable table, show options side-by-side, or visualize rows and columns of data. Always renders live in browser — never as static text.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before delivering, verify ALL:

    line 28
  2. Very specific:

    Always define colors as CSS variables on :root: Never write a hex color value directly into an element style.

    line 45
  3. Very specific:

    Always call wait_for before take_screenshot: Wait on the first column header text string.

    line 49

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Table

Renders interactive sortable, filterable tables in the browser by writing a zero-dependency HTML file and opening it via Chrome DevTools.

Workflow

  1. Extract columns and rows — identify column names, value types (text, number, badge, rating, boolean, tag), and all row data from user context. See TEMPLATE.md for column type definitions.
  2. Map column types — assign a type to each column: text, number, badge, rating, boolean, or tag. See TEMPLATE.md for rendering rules per type.
  3. Choose a unique filename — use /tmp/table.html by default. If a file with that name already exists (check with Bash ls /tmp/table.html), use a descriptive slug instead (e.g. /tmp/genai-taxonomy.html, /tmp/db-comparison.html). Never silently overwrite an existing file with unrelated content.
  4. Write the HTML file — write a complete self-contained file to the chosen path using the vanilla JS template. See TEMPLATE.md for the full template with sort and filter implementation.
  5. Render in browser — follow _shared/chrome-devtools-render.md to open the HTML file, wait for render, screenshot, and fix-and-reload if needed. wait_for the text of the first column header. See TROUBLESHOOTING.md for table-specific fixes.

Self-review checklist

Before delivering, verify ALL:

  • Screenshot shows all columns with readable headers and all rows with populated cells
  • Sort works: clicking a column header changes row order and shows a ▲ or ▼ indicator
  • Filter works: search input above the table is present with placeholder="Filter..."
  • Dark background (#1e1e2e) is applied — not white or gray
  • No horizontal scroll is visible when the table fits the viewport
  • Sticky header (position: sticky; top: 0) is present in the CSS
  • All CSS color values use var(--token) references — no hardcoded hex in element styles
  • wait_for was called before take_screenshot
  • Rating cells render as star characters (e.g. ⭐⭐⭐), not raw numbers
  • Boolean cells render as ✓ or ✗, not true/false

Golden rules

Hard rules. Never violate these.

  1. Always define colors as CSS variables on :root. Never write a hex color value directly into an element style. Every color used must reference a var(--token).
  2. Always include both sort AND filter. A table missing either feature is incomplete. Both must be present in every output, even for small datasets.
  3. Never use an external library. Implement sort and filter in plain JS. The complete implementation is under 50 lines. See TEMPLATE.md.
  4. Always use position: sticky; top: 0 on thead. Apply this to every table regardless of row count.
  5. Always call wait_for before take_screenshot. Wait on the first column header text string. Never screenshot immediately after new_page.
  6. Always use overflow-x: auto on the table container. Without it, wide tables break the page layout.
  7. Always .toLowerCase() both sides in the filter comparison. Case-sensitive filtering breaks on mixed-case data.

Reference files

FileContents
TEMPLATE.mdComplete vanilla JS HTML template with full sort and filter implementation, CSS design tokens, column type rendering rules
TROUBLESHOOTING.mdFailure diagnosis table: symptoms, likely causes, and fixes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.