Name: databasics
Rating: 60 (1 reviews)
Author: membranedev

databasics

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

Quality

70%

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/databasics/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 body is highly actionable with concrete CLI commands and a well-validated connection workflow, but it carries some marketing fluff and leaves minor gaps in cross-references and destructive-operation validation. Trimming the prose and adding a verification note for mutating proxy calls would round it out.

Suggestions

Cut the opening marketing paragraph and phrases like 'so you can focus on the integration logic rather than auth plumbing' to tighten conciseness.

Fix the dangling 'Step 2' reference (there is no labeled Step 2 / section 1a) so the connection workflow sequence is unambiguous.

Add a verification/validation note before destructive proxy requests (PUT/PATCH/DELETE) so workflow clarity can reach the top anchor.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but opens with marketing prose ('centralize, clean, and analyze their data... gain insights and improve decision-making') and includes redundant phrasing like 'rather than auth plumbing', fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready, executable membrane CLI commands for every stage (install, login, connection ensure, action list/run, request) plus a concrete flags table, matching 'fully executable; copy-paste ready; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state-based checkpoints and a poll/handle/re-poll feedback loop (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but a dangling 'Step 2' reference and no validation before destructive proxy methods (PUT/DELETE) are minor gaps below a 5.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested or buried references and no bundle files to misnavigate, though all detail (flags table, clientAction schema) lives inline in a 140-line file rather than being split out, fitting 'good structure; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

66%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 what and when in third person and is anchored to a distinctive brand, but its action verbs are generic and trigger keyword coverage is narrow. Strengthening it with more specific DATABASICS actions and additional natural trigger phrases would raise the middle dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with DATABASICS-specific actions (e.g., 'query expense records, submit timesheets, sync line items') to lift specificity.

Add more natural trigger phrases and synonyms beyond 'interact with DATABASICS data' (e.g., 'expense reports, timesheets, DATABASICS records') to broaden trigger-term coverage.

Expand the 'Use when' clause with multiple concrete triggers so completeness can reach the top anchor.

Dimension	Reasoning	Score
Specificity	Names the DATABASICS domain plus a few actions ('Manage data, records, and automate workflows'), but those verbs are generic and not comprehensive, fitting the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states both what it does and when to use it ('Manage data, records, and automate workflows. Use when the user wants to interact with DATABASICS data'), but the 'when' is a single narrow trigger rather than multiple concrete phrases, so it sits below a 5.	4 / 5
Trigger Term Quality	The trigger relies mostly on the brand name plus 'data' ('Use when the user wants to interact with DATABASICS data'); keyword coverage is thin with no synonyms or common variations, matching 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named DATABASICS platform gives it a clear niche with minimal conflict risk against generic skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	15 / 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/databasics/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.