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

56

Quality

71%

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

63%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 concrete, API-complete reference with working curl examples, good setup guidance, and useful error handling, but it is held back by malformed visualize example payloads, substantial duplication between Usage and Examples sections, and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Fix the three truncated 'Visualize Your Own Data' code blocks so the -d JSON payload is complete and copy-paste executable (currently the CSV data leaks outside the JSON string).

Deduplicate the 'Examples' section against 'Usage' and state the shared curl wrapper (base URL, auth header) once instead of repeating it in every example.

Move the full Parameters and Response field reference into a references/ file (e.g., API.md), keeping SKILL.md as a lean overview with well-signaled one-level-deep pointers.

DimensionReasoningScore

Conciseness

All twelve curl examples repeat identical URL/header boilerplate, and the 'Examples' section largely re-duplicates commands already shown in 'Usage'. Mostly efficient (no concept explanations Claude already knows) but noticeably could be tightened, matching anchor 3 rather than 4.

3 / 5

Actionability

Most curl commands are complete and copy-paste ready with realistic payloads, and the credentials setup is fully executable. However, the three 'Visualize Your Own Data' blocks (lines 76-84, 89-96, 214-221) have truncated -d JSON payloads with CSV rows leaking outside the string, and the chart_insights example posts a body where the Parameters section documents a GET. Falls between anchors 3 and 4: mostly executable with gaps beyond minor.

4 / 5

Workflow Clarity

A clear implicit sequence (auth setup -> knowledge search -> use card_id for insights/embed) with an Error Handling section covering 400/401/404 and a recovery hint for empty results ('try rephrasing or using source_indexes'). No destructive or batch operations, so no cap applies; not 5 because there is no explicit validate-fix-retry loop.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent); the full parameter reference, response-field reference, and example set are all inlined in a ~230-line SKILL.md. Section headers are good and navigation is possible, but bulk reference content that belongs in separate files is inline, matching anchor 3.

3 / 5

Total

14

/

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.

A clear, domain-specific description with concrete deliverables (charts, insights, embeddable knowledge cards) and good natural keywords. Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness and limits its usefulness for skill routing.

Suggestions

Add an explicit 'Use when...' clause (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').

Add common synonyms users would naturally say, such as 'graph', 'visualization', 'statistics', or 'stock prices', to strengthen trigger coverage.

Tighten 'Search and visualize the world's data' to concrete actions (e.g., 'Search public and private datasets') to reduce vagueness.

DimensionReasoningScore

Specificity

Names several concrete actions ('get charts, insights, and embeddable knowledge cards') plus concrete domains (finance, economics, demographics, sports), though 'Search and visualize the world's data' is slightly generic. Not 5 because coverage of actions is less comprehensive than the top anchor; not 3 because it lists more than 1-2 concrete actions.

4 / 5

Completeness

Has a clear 'what' (search and visualize data, get charts/insights/knowledge cards) but entirely lacks a 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is absent rather than merely implicit-but-present.

3 / 5

Trigger Term Quality

Good natural keywords users would say ('charts', 'data', 'finance', 'economics', 'demographics', 'sports'), but common synonyms like 'graph', 'visualization', 'statistics', or 'stocks' are missing. Not 5 because synonym coverage is incomplete; not 3 because the natural term coverage goes beyond 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The 'knowledge cards' framing and domain list carve out a fairly distinct data-search/visualization niche with minor overlap risk against generic charting skills. Not 5 because 'charts' and 'data' are broad terms shared with other visualization skills; not 3 because the domain enumeration narrows it meaningfully.

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.

Validation — 15 / 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.