CtrlK
BlogDocsLog inGet started
Tessl Logo

carto

Carto integration. Manage data, records, and automate workflows. Use when the user wants to interact with Carto data.

55

Quality

62%

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 ./skills/carto/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 content is a well-structured, actionable guide to driving Carto via the Membrane CLI, with concrete commands and a clear state-aware connection workflow, weakened mainly by a padded intro and a vague overview section.

Suggestions

Trim or remove the opening paragraph explaining what CARTO is, since Claude can infer this from the domain.

Replace the literal 'QUERY' intent placeholder with a concrete example such as '--intent "list datasets"'.

Add a brief note on validating action results (e.g. checking the response 'output' or error fields) after running actions.

DimensionReasoningScore

Conciseness

The body is mostly efficient commands, but the opening paragraph explaining what CARTO is, the vague 'Carto Overview' with 'Use action names and parameters as needed', and the repeated action-list command add unnecessary padding.

3 / 5

Actionability

It provides copy-paste-ready CLI commands covering install, auth, connection, action discovery/execution, and proxying, with minor gaps such as the literal 'QUERY' intent placeholder and no concrete proxy endpoint example.

4 / 5

Workflow Clarity

The install→authenticate→connect→wait→search→run→proxy sequence is clear with explicit state checkpoints (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, with minor validation gaps.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is organized into clear labeled sections with no nested references, which is good structure though some content like the proxy flag table could conceivably be split out.

4 / 5

Total

15

/

20

Passed

Description

57%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 correctly includes an explicit 'Use when' trigger and names a distinct product niche, but its capability list is generic rather than Carto-specific and it lacks synonym trigger terms.

Suggestions

Replace generic verbs with concrete Carto actions, e.g. 'query datasets, manage connections, and run spatial analyses'.

Add natural trigger synonyms such as 'geospatial data', 'maps', or 'location intelligence' alongside 'Carto'.

Tighten the 'when' clause to name concrete user intents (e.g. 'Use when the user wants to query or visualize Carto datasets').

DimensionReasoningScore

Specificity

It names the Carto domain but the listed actions ('Manage data, records, and automate workflows') are generic verbs on vague nouns rather than concrete Carto-specific operations like querying datasets or creating maps.

2 / 5

Completeness

Both 'what' (Carto integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with Carto data') are present, though the when clause is somewhat generic.

4 / 5

Trigger Term Quality

'Carto' and 'Carto data' are relevant natural keywords a user would say, but synonyms like geospatial, maps, or location data are missing, so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Carto platform gives it a clear niche with minimal conflict risk, though the generic wording keeps it just short of fully distinct triggers.

4 / 5

Total

13

/

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
membranedev/application-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.