CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

table-grid-commands

Check that every table insert, remove, merge and split command, and Enter, Backspace, Delete, paste and delete inside and across cells, leaves a table whose cells cover every slot exactly once and puts each cell's content where the Table section of docs/editor-behavior/markdown-editing-spec.md says, on every span layout of up to three rows and three columns. Use before and after changing packages/platejs/src/features/table or another file in its coverage record, when the table-grid step of pnpm check fails, or when fixing a table structure or cell-editing bug a test or a tester found.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly operational skill body with executable commands, explicit validation and recovery loops, and a well-defined triage procedure for failures. Its main costs are runtime statistics and historical fix detail that pad the token budget, and material that could be offloaded to reference files.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows and nearly every sentence carries operational information, but time-sensitive runtime statistics ("used 231 CPU-seconds and took 93 s at a load average of 110") and dated fix history ("ten fixes in the two months before 2026-10-24, such as a9919f48f9") could be trimmed without loss.

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact commands (`pnpm check:table-grid`, `--case='<identity or part of one>'`, `--jobs=<n>`, `--lower`, `--init`), exit-code semantics, a worked failure-output example with interpretation, and a concrete git-log procedure for the sync commit.

5 / 5

Workflow Clarity

Workflows are clearly sequenced with explicit validation loops: run the gate, read a finding, classify it as real bug / modeling error / intended change, fix accordingly, then run `--lower`; the gate re-fails until the baseline is lowered, and moving the sync commit forward is gated on a recheck plus a passing run.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers and one-level references to repo files (spec, baseline, script, coverage-table files), but at ~93 lines, dense material such as the Findings analysis and the planted-mutant discussion is inlined rather than split into a reference file.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An unusually precise description that states the verified property, the full command surface, the layout bound, and three concrete trigger conditions. Its only weakness is trigger phrasing that favors internal jargon over the natural synonyms a user might say.

DimensionReasoningScore

Specificity

The description enumerates the exact command surface ("every table insert, remove, merge and split command, and Enter, Backspace, Delete, paste and delete inside and across cells"), the precise invariant ("cells cover every slot exactly once"), the layout bound ("up to three rows and three columns"), and the governing spec path, giving comprehensive concrete coverage rather than minor gaps.

5 / 5

Completeness

It explicitly answers both what ("Check that every table... command... leaves a table whose cells cover every slot exactly once...") and when with concrete triggers ("Use before and after changing packages/platejs/src/features/table... when the table-grid step of pnpm check fails, or when fixing a table structure or cell-editing bug").

5 / 5

Trigger Term Quality

Natural phrases like "merge", "split", "paste", "table structure", "cell-editing bug", and "the table-grid step of pnpm check fails" match what a maintainer would say, but plainer variations such as "insert row", "remove column", and "merge cells" are absent and the phrasing leans technical ("span layout", "coverage record").

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche — table-grid verification for the Plate/Plite table plugin — anchored to specific repo paths, a spec file, and a named check step, so the risk of triggering for an unrelated skill is minimal.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

udecode/plate

Path

.agents/skills/table-grid-commands/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.