Name: retool
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

retool

Retool integration. Manage Users. Use when the user wants to interact with Retool data.

Quality

59%

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/retool/SKILL.md

Quality

Content

56%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 actionable CLI guidance is concrete and well-sequenced with validation checkpoints, but the body is dominated by a massive inlined enumeration of query types that wastes context and should be split out or dropped. Structure exists via headers yet progressive disclosure is undermined by that monolithic list.

Suggestions

Remove or externalize the ~980-line enumerated query list into a reference file (e.g. references/query-types.md) and link to it, which would recover most of the conciseness and progressive-disclosure loss.

Fix the dangling "Step 2" reference by labeling the workflow steps consistently (1a/1b/2) or rewriting the cross-references to section names.

Resolve placeholder usage (e.g., CONNECTION_ID) with a short note on where the value comes from, and deduplicate the "Popular actions" section so it adds information beyond the search command.

Dimension	Reasoning	Score
Conciseness	Roughly 980 of ~1100 lines are an inlined enumerated list of every Retool query type, a heavily padded data dump that does not earn its context; the instruction sections themselves are reasonably tight, placing this noticeably below efficient.	2 / 5
Actionability	Concrete, executable CLI commands are given throughout (install, login, connection ensure/get, action list/run, request) with a flags table, with only minor gaps such as unresolved CONNECTION_ID placeholders and the redundant "Popular actions" repeat.	4 / 5
Workflow Clarity	There is a clear sequence (install -> authenticate -> connect -> search -> run -> proxy) with explicit state checkpoints and a poll-until-ready feedback loop, but the referenced "Step 2" has no matching labeled section, leaving minor gaps.	4 / 5
Progressive Disclosure	Section headers provide navigable structure, but the 980-line query enumeration is content that clearly belongs in a separate reference file (or should be removed), so organization is only partial.	3 / 5
	Total	13 / 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 is third-person, concise, and answers both what and when with an explicit trigger clause, but its capability statement is thin (only "Manage Users") and trigger coverage lacks synonyms. It is distinct because Retool is a specific product, yet the wording is generic.

Suggestions

Replace the narrow "Manage Users" with several concrete capabilities the skill actually supports (e.g., run Retool queries, manage apps, proxy Retool API requests) to lift specificity and completeness.

Add natural trigger variations and file/URL hints (e.g., "Retool apps, Retool queries, retool.com") so users phrase requests in more ways that match.

Tighten the "when" clause to concrete situations (e.g., "Use when the user wants to run or automate Retool queries and app actions") to reach the explicit-trigger-phrases anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ("Retool integration") and one concrete action ("Manage Users"), matching the anchor for domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both "what" (Retool integration, Manage Users) and "when" ("Use when the user wants to interact with Retool data") are present and explicit, though the "what" is narrow rather than comprehensive.	4 / 5
Trigger Term Quality	"Retool" and "Retool data" are relevant natural terms, but coverage lacks synonyms or file extensions, falling at the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	Retool is a distinct product niche with low overlap risk, but the phrasing ("Retool integration", "Retool data") is generic rather than sharply distinctive, so it sits just below the clear-niche anchor.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1135 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/retool/SKILL.md
Commit: f484c82

Reviewed: 5 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.