Name: defastra
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

defastra

Defastra integration. Manage Organizations, Leads, Projects, Users, Goals, Filters. Use when the user wants to interact with Defastra data.

Quality

63%

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

Quality

Content

61%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 delivers strong executable CLI commands and a reasonably sequenced connection workflow, but is undermined by a leftover placeholder line, an inconsistent overview section, and a broken "Step 2" reference that hurt clarity and conciseness.

Suggestions

Remove the placeholder ("I don't have enough information to describe Defastra...") and the vague "Use action names and parameters as needed" line.

Reconcile the "Defastra Overview" entity list (Project/Issue/User/Worklog/Comment) with the description's resources (Organizations/Leads/Projects/Users/Goals/Filters) so they are consistent.

Fix the dangling "skip to Step 2" by labeling the search/run steps explicitly (e.g., "## Step 2: Search for actions") to close the workflow sequence gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and command-focused, but it contains an irrelevant placeholder line ("I don't have enough information to describe Defastra...") and vague filler ("Use action names and parameters as needed"), so it is mostly efficient with some unnecessary padding.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run") with real flags and a popular-actions table, with only minor gaps from the placeholder and vague directives.	4 / 5
Workflow Clarity	A clear sequence exists (install → auth → connect → search → run) with explicit state checkpoints for the connection flow (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with polling), but the dangling "skip to Step 2" with no labeled Step 2, the inconsistent overview entities, and the placeholder text leave noticeable sequence gaps.	3 / 5
Progressive Disclosure	As a single-file CLI integration guide with no bundle files present, it is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with content appropriately placed inline; only minor organization gaps remain.	4 / 5
	Total	14 / 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 explicitly answers both what and when and is highly distinct thanks to the Defastra proper noun, but the action verb "Manage" is generic and the trigger term coverage is limited to the brand name.

Suggestions

Replace the single generic verb "Manage" with several concrete actions per resource (e.g., "Create and assign Leads, track Project Issues, manage User roles") to lift specificity.

Broaden the trigger phrase beyond the brand name to include natural variations users might say (e.g., "phone/email risk checks", "lead enrichment", "Defastra data").

Dimension	Reasoning	Score
Specificity	It names the domain and six concrete resources ("Organizations, Leads, Projects, Users, Goals, Filters") but uses a single generic action verb ("Manage"), so the actions are minimal rather than comprehensive — matching the anchor that names the domain with 1-2 concrete actions.	3 / 5
Completeness	Both "what" ("Manage Organizations, Leads, Projects, Users, Goals, Filters") and "when" ("Use when the user wants to interact with Defastra data") are explicitly present, but the "when" is somewhat broad rather than highly specific — matching the anchor where both exist but the when could be more explicit.	4 / 5
Trigger Term Quality	The natural keyword is the proper noun "Defastra" plus "interact with Defastra data", which are relevant but limited; common variations or synonyms are missing, fitting the anchor for some relevant keywords without broader coverage.	3 / 5
Distinctiveness Conflict Risk	"Defastra" is a unique proper noun tied to a specific app, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	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/defastra/SKILL.md
Commit: f484c82

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