Name: octopus-deploy
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

octopus-deploy

Octopus Deploy integration. Manage Projects, Accounts, Certificates, Feeds, Infrastructures, Users and more. Use when the user wants to interact with Octopus Deploy data.

Quality

66%

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/octopus-deploy/SKILL.md

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 an actionable, well-structured guide built around concrete Membrane CLI commands and a clear connection-state workflow. It would benefit from tighter prose and explicit validation checkpoints for destructive deployment operations.

Suggestions

Add an explicit verification step after destructive/batch actions (e.g. poll the deployment task or confirm release state) so the workflow includes a validate→fix→retry feedback loop.

Trim editorial filler ("so you can focus on the integration logic", "This is the fastest way") to improve token efficiency.

Clarify the ambiguous "Step 2" reference in the Connecting section, which points to a step that is not explicitly numbered.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste commands and brief context, but includes padded prose like "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed.	3 / 5
Actionability	Provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with a flags table; minor gaps remain around the CONNECTION_ID placeholder resolution and runbook-specific examples.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with a polling/feedback loop for connection states, but Octopus Deploy involves potentially destructive/batch operations (deployments) with no explicit validation step, capping clarity at 3.	3 / 5
Progressive Disclosure	Well-organized into clearly signaled sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no broken or nested references; the proxy-options table and best-practices prose are slightly bulky inline but appropriately placed for a self-contained skill.	4 / 5
	Total	14 / 20 Passed

Description

71%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.

A solid description that names the integration, enumerates concrete managed objects, and includes an explicit Use-when clause. It is clearly distinct but could improve trigger-term coverage and make the "when" more specific.

Suggestions

Expand the "Use when" clause with concrete natural-language triggers users would say, e.g. "deploying releases", "managing environments or runbooks", "triggering deployments".

Replace the generic "and more" with one or two additional concrete capabilities to close the specificity gap toward a 5.

Add common synonyms or shorthand (e.g. "Octopus", "OD") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete managed entity types ("Projects, Accounts, Certificates, Feeds, Infrastructures, Users") which is comprehensive coverage, though the trailing "and more" leaves minor gaps keeping it just below a 5.	4 / 5
Completeness	Explicitly answers both "what" (manage Projects, Accounts, etc.) and "when" ("Use when the user wants to interact with Octopus Deploy data"), but the "when" could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural product keyword "Octopus Deploy" and entity names, but the trigger clause ("when the user wants to interact with Octopus Deploy data") is fairly generic and lacks common synonyms or variations a user might say.	3 / 5
Distinctiveness Conflict Risk	The "Octopus Deploy" product name carves out a clear, distinct niche with minimal conflict risk against other skills; the named entities further sharpen the trigger.	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/octopus-deploy/SKILL.md
Commit: f484c82

Reviewed: 5 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.