Name: dyn
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

dyn

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

Quality

68%

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/dyn/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, giving executable commands and a well-sequenced connection workflow with real validation feedback loops. The main weaknesses are an unnecessary company-description preamble and content dense enough to benefit from splitting into reference files.

Suggestions

Cut the opening "Dyn is a cloud-based internet performance management company..." paragraph or condense it to one line, since Claude already knows what Dyn is.

Move the detailed clientAction state machine and the proxy flags table into a one-level-deep reference file (e.g. references/connections.md) referenced from the body.

Add a short verify step after running actions (e.g. inspect the output/error fields) so the action-execution workflow matches the validation rigor of the connection phase.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening company blurb ("Dyn is a cloud-based internet performance management company...") explains background Claude largely already knows and could be trimmed, matching the mostly-efficient-but-could-be-tighter anchor.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run, proxy) plus a concrete flags table, fitting the fully-executable anchor covering common cases.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with validation checkpoints (poll --wait, inspect state, handle CLIENT_ACTION_REQUIRED, re-poll, check error field), but the "skip to Step 2" reference has no labeled Step 2 and action execution lacks a verify step, leaving minor gaps below the top anchor.	4 / 5
Progressive Disclosure	The body is well-organized into clear headers with no nested references and no bundle files to navigate; it loses the top score only because the 140-line file inlines material (the clientAction state machine, proxy flag table) that could live in one-level-deep reference files.	4 / 5
	Total	16 / 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 cleanly answers what the skill does and when to use it with a third-person voice and an explicit trigger tied to a specific product. It is held back from the top band by generic action verbs and thin keyword/synonym coverage.

Suggestions

Replace generic verbs with concrete Dyn actions, e.g. "Manage DNS records, traffic, and performance monitoring; automate workflows."

Add natural trigger synonyms such as "DNS", "Dyn DNS", or "internet performance" to broaden keyword coverage.

Tighten the "what" clause to list 3-4 specific capabilities so completeness reaches the top anchor.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Dyn domain and a couple of action areas, but the verbs ("manage") are generic rather than concrete, matching the anchor for naming a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It states both a "what" ("Dyn integration. Manage data, records, and automate workflows.") and an explicit "Use when..." trigger, but the "what" is somewhat generic rather than fully concrete, so it sits just below the top anchor.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Dyn data" surfaces the natural term "Dyn data" but offers no synonyms or variations, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	Scoping everything to the named product "Dyn" gives it a distinct niche with minimal conflict risk, though the generic "manage data, records" verbs leave minor overlap with general data-management skills.	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/dyn/SKILL.md
Commit: f484c82

Reviewed: 4 days 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.