Name: toucan-toco
Rating: 61.6 (1 reviews)
Author: membranedev

toucan-toco

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

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/toucan-toco/SKILL.md

Quality

Content

82%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 highly actionable with executable Membrane CLI commands, a clear multi-step connection workflow with state-based validation checkpoints, and clean section organization. The only slack is a mildly over-explanatory intro and the absence of action-result verification guidance.

Suggestions

Trim or remove the opening descriptive paragraph about what Toucan Toco is, since Claude can infer app context from the docs link.

Add a brief verification step after `membrane action run` (e.g. check the `output`/`error` field) to close the workflow's validation gap and push workflow clarity toward anchor 5.

Consider splitting the proxy flag table and action-reference detail into a references file to formalize progressive disclosure, though inline placement is currently reasonable.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable commands and minimal padding, but the opening paragraph ("Toucan Toco is a data storytelling platform that helps businesses visualize and communicate data insights...") explains app context Claude could infer; matches anchor 4 (efficient, minor over-explanation to trim) and below anchor 5.	4 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy requests plus a flag table; matches anchor 5 (fully executable, covers common cases) and exceeds anchor 4's "minor gaps".	5 / 5
Workflow Clarity	Sequences install → login → connection ensure → poll state → search → run with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop; matches anchor 4 (clear sequence, most checkpoints, minor validation gaps) but action-result verification is not spelled out, so it is below anchor 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent), so all content is inline but well-organized under clear section headers (Install, Authentication, Connecting, Searching, Popular actions, Best practices); matches anchor 4 (good structure, content appropriately placed) and is below anchor 5 only because no one-level-deep references are used.	4 / 5
	Total	17 / 20 Passed

Description

62%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 answers both what and when in third person and names a distinct app, but its actions and trigger terms are generic and could be tightened with more concrete capability verbs and natural synonyms. Voice and structure are sound; the main weakness is specificity of capabilities.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "Create and edit dashboards, manage data sources and filters, automate data workflows" to lift specificity toward anchor 4-5.

Add natural trigger phrases and synonyms such as "Toucan Toco dashboards, data stories, filters, or visualizations" to broaden keyword coverage.

Tighten the "Use when" clause with concrete trigger conditions (e.g. building or editing Toucan Toco dashboards) to move completeness toward anchor 5.

Dimension	Reasoning	Score
Specificity	Quotes "Manage data, records, and automate workflows" name the domain plus 2-3 actions, but each action is broad and generic rather than concrete like "extract text, fill forms"; matches anchor 3 (1-2 concrete actions, not comprehensive) and falls short of anchor 4's specific-action coverage.	3 / 5
Completeness	Provides both a "what" ("Toucan Toco integration. Manage data, records, and automate workflows.") and a "when" ("Use when the user wants to interact with Toucan Toco data."), but the when is generic rather than tied to concrete trigger phrases; matches anchor 4 and is below anchor 5's explicit concrete triggers.	4 / 5
Trigger Term Quality	Includes "Toucan Toco", "data", "records", and "workflows" with an explicit trigger clause, but lacks common variations, synonyms, or file extensions; matches anchor 3 (some relevant keywords, missing common variations) and does not reach anchor 4's fuller keyword coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "Toucan Toco" gives a clear niche with minimal conflict risk, but the generic action verbs (manage data, automate workflows) create minor overlap risk with other data-integration skills; matches anchor 4 (mostly distinct, minor overlap) rather than anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/toucan-toco/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.