Name: databowl
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

databowl

Databowl integration. Manage Recordses. Use when the user wants to interact with Databowl data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/databowl/SKILL.md

Quality

Content

75%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 skill body is highly actionable, with concrete, executable Membrane CLI commands and a well-structured connection workflow that includes state-based checkpoints. The main weaknesses are mild verbosity from repeated command examples, a dangling 'Step 2' reference, and missing validation guidance for destructive CRUD operations.

Suggestions

De-duplicate the action-discovery invocation (it appears under both 'Searching for actions' and 'Popular actions') and trim explanatory prose like 'so you can focus on the integration logic rather than auth plumbing' to improve conciseness.

Resolve the dangling 'Step 2' reference by explicitly labeling the next step (e.g., add a '### Step 2: Run actions' header) or remove the cross-reference.

Add a validation/check step for destructive operations (create/update/delete on Records), such as re-reading or listing the Record after a mutation to confirm success, which would also lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and code blocks, but includes padding such as 'so you can focus on the integration logic rather than auth plumbing' and a repeated membrane action list invocation, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because several sections restate the same command and add prose Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, polling, action search/run, and proxy requests, plus a flag table, matching 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection workflow has explicit state-based checkpoints and a poll/retry feedback loop (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), matching 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because of the dangling 'Step 2' reference (no labeled Step 2) and the absence of validation for destructive CRUD action runs, and not 3 because the connect sequence genuinely includes explicit checkpoints and error-recovery guidance.	4 / 5
Progressive Disclosure	The content is a single, well-organized SKILL.md with clear section headers (Overview, Authentication, Connecting, Searching, Popular actions, Best practices) and no broken references, matching 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'.	4 / 5
	Total	16 / 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 covers both what the skill does and when to use it, but is generic in its trigger phrasing and light on concrete capability detail. Tightening the trigger terms and listing more specific actions would lift specificity and trigger quality.

Suggestions

List concrete actions explicitly (e.g., 'create, read, update, delete, and list Records') instead of the single vague phrase 'Manage Recordses', which also reads as a typo.

Replace the generic trigger 'interact with Databowl data' with concrete natural-language triggers users would say (e.g., 'Use when the user wants to create, list, update, or delete Databowl Records or query Databowl lead data').

Add synonyms and entity terms (e.g., 'Databowl Records, leads, forms, data') to broaden trigger-term coverage and reduce overlap ambiguity with other data skills.

Dimension	Reasoning	Score
Specificity	The description names the Databowl domain and one concrete action ('Manage Recordses') but offers no comprehensive action list, matching 'Names domain and 1-2 concrete actions, but not comprehensive'; it is not a 2 because it goes beyond a bare domain mention, and not a 4 because several specific actions are not listed.	3 / 5
Completeness	It states both what it does ('Databowl integration. Manage Recordses.') and when to use it ('Use when the user wants to interact with Databowl data.'), satisfying the 'Has both what and when' anchor; the when is generic rather than tied to concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	It includes 'Databowl' and 'Databowl data' as keywords with a 'Use when' trigger, but lacks natural synonyms, variations, or file extensions, fitting 'Some relevant keywords but missing common variations or synonyms'; a 4 would require broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform 'Databowl' gives it a clear niche with minimal conflict risk, matching 'Mostly distinct; minor overlap risk'; it is not a 5 because the trigger 'interact with Databowl data' is somewhat generic and could overlap with adjacent data skills.	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/databowl/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.