CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

carto

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

Quality

69%

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 body is a solid, mostly executable runbook for driving Carto through the Membrane CLI, with explicit connection-state handling and a sensible proxy fallback. Its weaknesses are padding (marketing intro, hollow "Carto Overview" and "Popular actions" sections) and a broken "Step 2" reference that muddles the otherwise clear workflow sequence.

Suggestions

Cut the marketing intro paragraph and the empty "Carto Overview" bullet list ("Use action names and parameters as needed" adds no instruction) — Claude already knows what CARTO is.

Fix the dangling "skip to **Step 2**" reference by numbering the actual steps consistently (the poll section is only labeled "1b" and no Step 2 exists).

Either populate "Popular actions" with real action examples (e.g. listing datasets, running a SQL query against a connection) or remove the section, since it currently just repeats the action-search command from the previous section.

DimensionReasoningScore

Conciseness

The bulk is efficient executable command documentation, but there is noticeable padding: the marketing-style CARTO intro paragraph ("Businesses across various industries use CARTO to understand spatial patterns"), an empty "Carto Overview" entity list followed only by "Use action names and parameters as needed", and a "Popular actions" section that contains no actions, just a repeat of the search command.

3 / 5

Actionability

Concrete, executable bash commands throughout — CLI install, `membrane connection ensure "https://carto.com" --json`, `action run` with `--input` JSON, and a full proxy flags table. Minor gaps: the Dataset/Column/Connection/OAuth App list carries no actionable guidance and `--tenant` is shown without its value.

4 / 5

Workflow Clarity

A clear sequence (install → login → ensure connection → poll state → resolve CLIENT_ACTION_REQUIRED → search actions → run → proxy fallback) with explicit state checkpoints and error recovery for CONFIGURATION_ERROR/SETUP_FAILED. Not 5 because "skip to **Step 2**" references a step that is never labeled (only a stray "1b" exists) and step numbering is inconsistent.

4 / 5

Progressive Disclosure

A single-file skill (no references/, scripts/, or assets/ exist) with well-organized sections and nothing long enough to demand extraction into a separate file; the proxy flags table is compact and appropriately inline. Minor organization gaps (orphaned step numbering, an empty section) keep it below 5.

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 follows the what-plus-when structure in third person and is pinned to a distinct niche app, so it triggers reliably for Carto requests. Its weakness is generic language: the stated capabilities and trigger phrases could describe almost any SaaS integration, and natural geospatial/mapping synonyms are absent.

Suggestions

Replace the generic capability list with Carto-concrete actions, e.g. "Manage geospatial datasets, columns, and connections; run Carto actions and send requests to the Carto API via Membrane."

Expand trigger coverage with natural synonyms users would say: "Use when the user mentions Carto, maps or mapping data, geospatial datasets, or location intelligence workflows."

Mentioning the key entities the skill actually works with (datasets, columns, connections, OAuth apps) in the description would sharpen both specificity and trigger matching.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Carto domain but the actions are generic verbs with no Carto-concrete capabilities (maps, geospatial datasets, connections, visualization), matching the anchor for minimal/generic actions rather than 1-2 concrete ones.

2 / 5

Completeness

Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' clause ("Use when the user wants to interact with Carto data") are present, but the when is a single generic trigger and the what is vague, so it does not reach the concrete-trigger-phrases level of 5.

4 / 5

Trigger Term Quality

"Carto", "data", "records", and "interact with Carto data" are relevant keywords, but natural synonyms a user would actually say — "maps", "mapping", "geospatial", "location intelligence", "spatial data" — are missing.

3 / 5

Distinctiveness Conflict Risk

"Carto integration" with a Carto-pinned 'Use when' clause gives a clear niche, but the generic "manage data... automate workflows" phrasing creates minor overlap risk with other data/automation skills.

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.

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

membranedev/application-skills

Path

skills/carto/SKILL.md

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill