Name: dnsimple
Rating: 62.4 (1 reviews)
Author: membranedev

dnsimple

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/dnsimple/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 Membrane CLI commands and a solid connect-and-poll workflow including error-recovery guidance. Its main weaknesses are mild marketing/audience fluff that could be trimmed and a dangling 'Step 2' reference that breaks navigation.

Suggestions

Remove audience/marketing padding such as who uses DNSimple and 'so you can focus on the integration logic rather than auth plumbing' to improve token efficiency.

Define or fix the 'Step 2' reference — either add a numbered 'Step 2' heading for searching/running actions or replace the bare 'Step 2' mentions with concrete section links.

Consider moving the proxy flag table and clientAction field reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and structure, but includes unnecessary padding such as 'It's used by developers, businesses, and anyone who needs reliable and automated domain infrastructure' and 'so you can focus on the integration logic rather than auth plumbing', matching the anchor for mostly-efficient content with some over-explanation to trim.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands across the common cases (install, login, connection ensure/get with --wait, action list/run, request proxy) plus a flag table, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	Clear sequence (install → authenticate → connect → poll for READY → search → run) with an explicit feedback loop for state handling (CLIENT_ACTION_REQUIRED → poll again), but the repeated 'skip to Step 2' reference points to no defined Step 2, leaving a minor navigation gap below the explicit-checkpoint anchor.	4 / 5
Progressive Disclosure	Single-file skill with no bundle files and well-organized section headers; content is appropriately placed with no nested references, though some inline material (proxy flag table, clientAction detail) and the dangling 'Step 2' reference leave minor organization gaps short of a clean 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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 third-person, names a distinct platform, and includes an explicit 'Use when' trigger, giving it solid completeness and low conflict risk. It is held back from the top by generic action verbs and missing common synonyms like 'domains' and 'DNS'.

Suggestions

Replace generic verbs with concrete DNSimple actions, e.g. 'Manage domains, DNS records, certificates, and webhooks' instead of 'Manage data, records, and automate workflows'.

Broaden trigger terms to include natural synonyms users would say, such as 'domains', 'DNS records', or 'DNS hosting'.

Make the 'when' clause more specific, e.g. 'Use when the user wants to manage domains, DNS records, or certificates in DNSimple.'

Dimension	Reasoning	Score
Specificity	Names the DNSimple domain and a couple of actions ('Manage data, records, and automate workflows'), but 'manage data' and 'automate workflows' are generic while only 'records' is concrete, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Answers both 'what' ('DNSimple integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with DNSimple data.'), but the 'when' clause is somewhat generic rather than listing concrete trigger phrases, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	Good keyword coverage with 'DNSimple', 'data', 'records', and an explicit trigger ('Use when the user wants to interact with DNSimple data'), though common synonyms like 'domains' or 'DNS' are missing, so it falls short of comprehensive (5).	4 / 5
Distinctiveness Conflict Risk	DNSimple is a named, specific platform giving the skill a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/dnsimple/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.