Name: code-dx
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

code-dx

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

Quality

61%

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/code-dx/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 content is actionable and well-structured with concrete CLI commands and a clear connection-state workflow, but it carries some marketing padding and lacks validation guidance around destructive proxy and action-run operations.

Suggestions

Add a validation/verification checkpoint before destructive proxy or action-run operations, e.g. dry-run GET to confirm the target before POST/PUT/DELETE.

Trim promotional language ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') to lean, factual guidance.

Provide at least one worked example with realistic values (a concrete actionId and its output) so the run/proxy commands are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and options, but it includes unnecessary marketing-flavored explanation ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') and a promotional intro that could be tightened, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a flags table, with only minor gaps such as omitted sample output and unresolved placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection flow has a clear state-checking sequence with checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED and re-polling), but destructive-capable operations exposed via the proxy (POST/PUT/DELETE) and action run have no validation or verification steps, which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no nested references, and all content is appropriately placed for its scope, with only minor organization gaps such as the detailed proxy flags table and best practices that could stand alone.	4 / 5
	Total	14 / 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 well-formed with an explicit 'Use when' clause and a distinctive product-named trigger, but its action list is generic and it omits substantive synonyms like vulnerabilities and findings.

Suggestions

Replace generic verbs with concrete Code Dx capabilities, e.g. 'Query findings, manage projects and analyses, post comments, and triage vulnerabilities.'

Broaden trigger terms to include natural synonyms such as 'vulnerabilities', 'findings', 'security analysis', or 'code analysis'.

Sharpen the 'Use when' clause with specific triggers, e.g. 'Use when the user wants to query or triage Code Dx findings, analyses, or project data.'

Dimension	Reasoning	Score
Specificity	Names the domain ('Code Dx integration') and 2-3 actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive, fitting the anchor that names the domain with 1-2 concrete actions.	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'Use when' trigger ('Use when the user wants to interact with Code Dx data'), but the 'when' could be more specific, matching the anchor for both present with room for improvement.	4 / 5
Trigger Term Quality	The trigger 'Code Dx data' is a relevant natural keyword, but it misses common variations and synonyms users would say (vulnerabilities, findings, security analysis, code analysis).	3 / 5
Distinctiveness Conflict Risk	The 'Code Dx' proper noun creates a clear niche with distinct triggers and minimal conflict risk, though the generic action verbs ('Manage data, records') introduce minor overlap risk, placing it just below the top anchor.	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/code-dx/SKILL.md
Commit: f484c82

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