CtrlK
BlogDocsLog inGet started
Tessl Logo

data-charts-tako

Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/design/capabilities/data-charts-tako/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, mostly actionable API reference for a read-only service, but it is hurt by repeated curl boilerplate, a duplicated Examples section, and malformed JSON in the visualize-your-own-data examples. Fixing the broken payloads and de-duplicating examples would raise conciseness and actionability.

Suggestions

Fix the malformed `-d` JSON in the Visualize examples (Usage x2 and Examples x1) so the CSV payload is inside the quoted request body and the curl is executable.

Remove the duplicated Examples section or fold it into Usage to cut repeated curl boilerplate and reduce token cost.

Define a reusable auth/header snippet once and reference it, instead of repeating the full `-H "Authorization: Bearer ..."` and `-H "Content-Type: ..."` lines in every example.

DimensionReasoningScore

Conciseness

It avoids explaining concepts Claude already knows, but repeats full curl boilerplate (auth/content-type headers) across 10+ examples and duplicates much of the Usage section in a separate Examples section, so it could be tightened.

3 / 5

Actionability

Most curl commands are copy-paste ready with concrete payloads, but the "Visualize your own data" examples have malformed `-d` JSON (the quote closes before the CSV payload) in three places, leaving a core feature non-executable as written.

4 / 5

Workflow Clarity

It is a read-only API with no destructive or batch ops, and the implied search -> card_id -> chart_insights flow plus ordering tips ("start here", "call List Default Schemas before Create Card") give a clear sequence with only minor explicitness gaps.

4 / 5

Progressive Disclosure

No bundle files exist; the 245-line body is a single well-sectioned reference (Setup, When to Use, Usage, Parameters, Response, Tips, Error Handling) with good organization, though it is a monolithic inline reference rather than a lean overview pointing one level deep.

4 / 5

Total

15

/

20

Passed

Description

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

The description conveys concrete capabilities and natural domain keywords well, but omits any explicit "Use when..." trigger guidance, which caps completeness and slightly weakens distinctiveness. Adding a trigger clause would lift the two constrained dimensions.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when the user asks a data question, wants to compare metrics, or needs a chart for finance, economics, demographics, or sports data."

Include a few natural synonyms (graphs, plots, visualizations) alongside "charts" to broaden trigger coverage.

Tighten "the world's data" toward the specific named domains to reduce breadth and overlap risk with generic charting skills.

DimensionReasoningScore

Specificity

"Search and visualize the world's data - get charts, insights, and embeddable knowledge cards" lists multiple concrete actions (search, visualize, get charts/insights/knowledge cards), though the domain framing "the world's data" stays somewhat broad.

4 / 5

Completeness

It clearly answers "what" (search/visualize data, get charts/insights/cards) but has no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Natural keywords users would say ("charts", "insights", "finance", "economics", "demographics", "sports") are present with good coverage, but common synonyms like "graphs", "plots", or "visualizations" are missing.

4 / 5

Distinctiveness Conflict Risk

The data-search-and-knowledge-card niche is mostly distinct with minor overlap risk against general charting/visualization skills; lack of explicit triggers slightly raises conflict risk versus a 5.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.