CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

data-forms

Pick the right way to represent a dataset so a reader gets the finding in three seconds — a catalog of 20+ chart and diagram forms with when-to-use and failure modes, plus the encoding decisions that make any of them readable (takeaway headline, direct labels, kill the axis, highlight-and-mute, show the caveat). Style-agnostic — use with whatever palette or design system the destination already has. Use when charting survey results, benchmark data, usage metrics, or research findings for a post, brief, deck, or report, and whenever the default bar chart feels like it's burying the point.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/data-forms/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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.

The body is a thin redirect stub that delegates all substance to an external SKILL.md and rules file not present in the bundle. It is concise but neither actionable nor self-contained, and its references point to files that may not resolve.

Suggestions

Inline at least a minimal quick-start — the core chart-selection shortcut or a few representative forms with their when-to-use — so the body is useful without the external playbook.

Add one concrete, executable example (e.g., applying 'takeaway headline + direct labels + kill the axis' to a small dataset) so the guidance is actionable on its own.

If delegation is intended, bundle the referenced playbook and rules under ./references/ so the one-level-deep references are real, navigable files instead of external paths that may not resolve.

DimensionReasoningScore

Conciseness

The ~50-word body is lean and avoids over-explaining concepts Claude already knows, but the 'Antigravity substitution' aside is marginal operational detail that does not earn every token.

4 / 5

Actionability

It names specific file paths to read, but all actual chart-selection guidance is deferred to an external, non-bundled SKILL.md; there is no code or concrete step for the skill's stated purpose.

2 / 5

Workflow Clarity

A rough sequence is present ('Read… and execute it… Then follow cog.md'), but the real workflow lives in the external playbook and no checkpoints or structure are visible in the body itself.

3 / 5

Progressive Disclosure

There is no bundle and the references point to non-bundled external paths (another SKILL.md and rules file); the content is entirely deferred rather than appropriately split into navigable one-level-deep references.

2 / 5

Total

11

/

20

Passed

Description

96%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.

A strong, specific description that clearly states both what the skill does and when to use it, with rich natural trigger language. Its only soft spot is some overlap risk with sibling charting/visualization skills on shared triggers.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions — 'a catalog of 20+ chart and diagram forms with when-to-use and failure modes' plus specific encoding decisions ('takeaway headline, direct labels, kill the axis, highlight-and-mute, show the caveat'), giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (catalog of forms + encoding decisions) and when ('Use when charting survey results, benchmark data, usage metrics, or research findings…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural terms users would say — 'charting survey results, benchmark data, usage metrics, or research findings', 'default bar chart feels like it's burying the point', and 'post, brief, deck, or report' cover synonyms and output mediums.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (pick the right representation for a three-second finding) and a distinguishing 'style-agnostic' framing, but charting triggers like 'benchmark data' and 'default bar chart' overlap with closely related visualization skills.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

huytieu/COG-second-brain

Path

.agents/skills/data-forms/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.