CtrlK
BlogDocsLog inGet started
Tessl Logo

control-d

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

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/control-d/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, with copy-paste-ready Membrane CLI commands and a well-structured connection workflow that includes state-based validation and feedback loops. It is token-efficient with only minor over-explanation, and its single-file organization is clean though it makes no use of external references.

DimensionReasoningScore

Conciseness

The body is mostly efficient concrete commands with only minor over-explanation (the opening 'Control D is a customizable DNS service...' paragraph and the awkward Agent Types line), fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure/get with --json, action list/run, request with a concrete flags table), covering the common cases with specific examples.

5 / 5

Workflow Clarity

The connection setup has a clear sequence with explicit state-based validation checkpoints and feedback loops (poll --wait, CLIENT_ACTION_REQUIRED -> user acts -> poll again, CONFIGURATION_ERROR -> check error field); the dangling 'skip to Step 2' reference and unlabeled step numbering are minor gaps keeping it just below 5.

4 / 5

Progressive Disclosure

No bundle files exist and all content lives in one file, but it is well-organized into clearly headed sections (overview, install, auth, connecting, searching, running, proxy, best practices) with no deep nesting or buried references; structure is good with only minor organization gaps, consistent with the well-organized-sections allowance for self-contained skills.

4 / 5

Total

17

/

20

Passed

Description

61%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 establishes a clearly distinct niche via the Control D brand and includes an explicit 'Use when' trigger, but its action list is generic and it omits the natural task vocabulary (DNS, ad/malware blocking) that users would actually say. Tightening the 'what' and adding concrete trigger phrases would lift the weaker dimensions.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Control D capabilities (e.g., 'configure DNS profiles, manage device and network settings, block ads, trackers, and malware').

Expand the 'Use when' clause with natural user phrasings such as 'Use when the user wants to block ads or trackers, configure DNS filtering, or manage Control D devices and profiles.'

DimensionReasoningScore

Specificity

It names the domain ("Control D integration") but the actions "Manage data, records, and automate workflows" are generic rather than concrete, matching the 'names domain but actions minimal/generic' anchor and falling short of listing specific capabilities.

2 / 5

Completeness

Both 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Control D data") are present; the 'Use when' clause avoids the cap at 3, but the trigger is generic and could be more specific, fitting the both-present-but-when-could-be-sharper anchor.

4 / 5

Trigger Term Quality

It includes the distinctive keyword "Control D" and the phrase "interact with Control D data", but misses the natural task terms a user would actually say (DNS, block ads/trackers/malware, DNS filtering), so keyword coverage has relevant terms with common synonyms missing.

3 / 5

Distinctiveness Conflict Risk

The "Control D" brand name creates a clear niche with distinct triggers and minimal conflict risk with other skills, matching the 'clear niche with distinct triggers' anchor.

5 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.