Name: dock-certs
Rating: 55.2 (1 reviews)
Author: membranedev

dock-certs

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

Quality

62%

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/dock-certs/SKILL.md

Quality

Content

67%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 a well-structured, actionable CLI integration guide with executable commands and a solid connection-state feedback loop. Main weaknesses are mild prose padding and a broken 'Step 2' cross-reference that slightly muddies the workflow.

Suggestions

Trim marketing-style prose (e.g. 'so you can focus on the integration logic rather than auth plumbing') and the SaaS overview paragraph to assume Claude's competence.

Fix the 'skip to Step 2' references by adding an explicitly labeled 'Step 2: Search for actions' header so the cross-references resolve.

Provide one fully worked end-to-end example with concrete IDs filled in to close the actionability gap from placeholder values.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with code blocks and tables, but includes unnecessary prose such as the SaaS overview, 'so you can focus on the integration logic rather than auth plumbing', and informal best-practice padding that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-pasteable commands for install, login, connection, action search/run, and proxy requests, with minor gaps such as unfilled placeholders like <actionId> and CONNECTION_ID rather than a fully worked end-to-end example.	4 / 5
Workflow Clarity	The install → authenticate → connect → poll → search → run sequence is clear with a real feedback loop (poll --wait and handle READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR states), but the repeated 'skip to Step 2' references an unlabeled step, a minor clarity gap.	4 / 5
Progressive Disclosure	The single-file skill is well organized into clear sections (Overview, Install, Authentication, Connecting, Actions, Proxy, Best practices) with no nested references; the 20-row actions table is borderline content that could live in a reference file, keeping it just below a 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 correctly includes an explicit 'Use when...' trigger and names a distinct niche, but its action list is generic rather than concrete cert-management operations. Tightening the 'what' with specific Dock Certs capabilities would raise specificity and completeness.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Dock Certs operations such as 'issue certifications, manage recipients and templates, and track maritime worker compliance'.

Add natural trigger terms a user would actually say (e.g. 'certificates', 'credentials', 'maritime certifications') alongside 'Dock Certs data'.

Make the 'when' clause more specific about the scenarios that warrant this skill over generic data tools.

Dimension	Reasoning	Score
Specificity	The description names the domain (Dock Certs) but the stated actions — 'Manage data, records, and automate workflows' — are generic rather than concrete cert-management operations, matching the 'names domain but actions are minimal/generic' anchor.	2 / 5
Completeness	Both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Dock Certs data') are present; the trigger is explicit but generic, matching the 'has both what and when, when could be more specific' anchor.	4 / 5
Trigger Term Quality	'Dock Certs' is the key natural keyword and it appears in an explicit trigger clause, but common variations, synonyms, or file/record terms a user might say are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Dock Certs' is a clearly named niche with a distinct trigger giving low conflict risk, though the generic 'manage data/records/workflows' phrasing leaves minor overlap with general data-management skills.	4 / 5
	Total	13 / 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/dock-certs/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.