CtrlK
BlogDocsLog inGet started
Tessl Logo

ns1

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

56

Quality

63%

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/ns1/SKILL.md
SKILL.md
Quality
Evals
Security

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 is actionable and well-structured, with concrete Membrane CLI commands and a sensible connection workflow. It loses points for marketing-style padding, a broken "Step 2" cross-reference, and the absence of validation before destructive proxy requests.

Suggestions

Remove the marketing intro and "so you can focus on the integration logic rather than auth plumbing" filler to tighten token efficiency.

Fix the broken "skip to Step 2" reference by numbering the steps consistently (1a/1b/2) or removing the forward reference.

Add an explicit validation/confirmation checkpoint before destructive proxy requests (e.g. confirm before `-X DELETE`) to satisfy the workflow_clarity feedback-loop requirement.

DimensionReasoningScore

Conciseness

Mostly concrete with executable commands, but it carries unnecessary padding such as the marketing intro "It helps businesses optimize their website and application performance by intelligently routing traffic based on various factors" and "so you can focus on the integration logic rather than auth plumbing", fitting the 3 anchor over 4.

3 / 5

Actionability

It provides concrete, executable commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", the proxy flag table), with only minor gaps from placeholders like <agentType> and QUERY, matching the 4 anchor rather than fully copy-paste-ready 5.

4 / 5

Workflow Clarity

The connection flow has a sequence and a polling feedback loop ("poll again... to check if the state moved to READY"), but it references a non-existent "Step 2" and lacks validation/confirmation before destructive proxy calls (the proxy supports DELETE), so the destructive-operations cap pins it at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the single file is well organized with clear section headers (Overview, Authentication, Connecting, Searching, Proxy, Best practices); minor redundancy between "Searching for actions" and "Popular actions" keeps it at 4 rather than 5.

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 cleanly states what the skill does and when to use it, and the NS1-specific framing keeps conflict risk low. Its main weakness is generic action verbs and missing the DNS/zones vocabulary users actually say.

Suggestions

Replace generic verbs with concrete NS1 actions, e.g. "Manage DNS zones, records, monitors, and data sources" instead of "Manage data, records, and automate workflows".

Add the natural trigger terms users say — "DNS", "DNS records", "zones", "traffic management" — to the "Use when..." clause.

Tighten the trigger to enumerate concrete cases, e.g. "Use when the user wants to manage NS1 DNS zones, records, or monitors".

DimensionReasoningScore

Specificity

It names the 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, so coverage is not comprehensive — fitting the 3 anchor rather than 4.

3 / 5

Completeness

Both halves are present: a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with NS1 data"), but the trigger could be more specific, matching the 4 anchor rather than 5.

4 / 5

Trigger Term Quality

Relevant keywords ("NS1", "data", "records") appear, but the core natural terms users say for this product — "DNS", "DNS records", "zones", "traffic" — are absent, leaving common variations missing as the 3 anchor describes.

3 / 5

Distinctiveness Conflict Risk

"NS1 integration" targets a named, specific product with a distinct trigger ("interact with NS1 data"), giving a clear niche with minimal conflict risk, matching the 5 anchor.

5 / 5

Total

15

/

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.