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

Blog Docs Log in Get started

deployhq

DeployHQ integration. Manage Projects, Users, Teams. Use when the user wants to interact with DeployHQ 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/deployhq/SKILL.md

Quality

Content

71%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 skill body is highly actionable with executable commands and a well-checkpointed connection workflow, but it carries marketing fluff and inlines API-reference tables that would be better split into a separate file. No bundle files are present to offload that detail.

Suggestions

Trim the marketing intro and 'auth plumbing' commentary to assume Claude's competence and save tokens.

Move the popular-actions table and proxy-flags reference into a dedicated reference file (e.g. references/actions.md) and link to it from the body.

Resolve the undefined 'Step 2' reference and add a verification/confirm step before destructive actions like delete-project, delete-server, and rollback-deployment.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but the intro marketing prose ('streamline deployments, reduce errors, and improve release velocity') and 'so you can focus on the integration logic rather than auth plumbing' explain concepts/value Claude already assumes, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list, action run, and request, plus a concrete table of action keys, covering the common cases.	5 / 5
Workflow Clarity	The connection flow has explicit state checkpoints and feedback loops (poll BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll after action), but 'Step 2' is referenced without being defined and destructive actions (delete, rollback) have no verification guidance, leaving minor validation gaps short of a 5.	4 / 5
Progressive Disclosure	No bundle files exist, and the 19-row popular-actions table and proxy-flags table are inlined API-reference content that belongs in a separate reference file; with the body over 150 lines this is 'content that should be separate is inline' rather than the simple-skill exception.	3 / 5
	Total	15 / 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 covers both what the skill does and when to use it, anchored on a distinct branded product. Its main weakness is generic action language ('Manage') and trigger phrasing that could be more concrete and natural.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'List, create, update, and delete DeployHQ projects, servers, and deployments; queue and roll back deployments'.

Broaden trigger terms to natural user phrasings such as 'list DeployHQ projects', 'deploy a project', or 'rollback a deployment' rather than only 'interact with DeployHQ data'.

Dimension	Reasoning	Score
Specificity	It names the DeployHQ domain and the entity groups 'Projects, Users, Teams', but the only verb is the generic 'Manage', which is closer to score 2; listing multiple concrete objects lifts it above the minimal/generic anchor rather than reaching the 'several specific actions' of 4.	3 / 5
Completeness	Both 'what' ('DeployHQ integration. Manage Projects, Users, Teams.') and an explicit 'when' ('Use when the user wants to interact with DeployHQ data.') are present; it avoids the 3 cap because of the 'Use when' clause, but the 'what' is generic and the trigger could be more concrete, so it falls short of the fully concrete score-5 anchor.	4 / 5
Trigger Term Quality	'DeployHQ' plus 'Projects, Users, Teams' are relevant keywords with a 'Use when the user wants to interact with DeployHQ data' trigger, but it lacks common variations, synonyms, or natural phrasings a user would actually say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'DeployHQ' is a unique branded product with a clear niche, and the trigger 'interact with DeployHQ data' is distinct, giving minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/deployhq/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.