Name: inedo-otter
Rating: 62.4 (1 reviews)
Author: membranedev

inedo-otter

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

Quality

74%

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/inedo-otter/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 a well-structured, mostly executable integration guide with a clear connection-setup workflow and validation via state polling, weakened mainly by a generic entity list and the absence of a concrete worked action example.

Suggestions

Add a concrete worked example showing `membrane action run` with a real actionId and sample JSON output so Claude can pattern-match real usage.

Resolve the 'Step 2' / '1b' numbering into a single consistent labeled sequence (Step 1, Step 2, Step 3) so navigation is unambiguous.

Move the 18-item entity 'Overview' list into a references file (e.g. ENTITIES.md) and keep SKILL.md as a concise overview that links to it.

Dimension	Reasoning	Score
Conciseness	The body is dominated by concrete, executable CLI commands, with only minor over-explanation (the opening 'Inedo Otter is an infrastructure automation tool...' sentence and 'so you can focus on the integration logic rather than auth plumbing') that could be trimmed, fitting anchor 4.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and request with a full flags table, but lacks any concrete worked example with a real actionId and sample output, leaving minor gaps that cap it at 4 rather than 5.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→search→run sequence with state-based polling checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the unlabeled 'Step 2' reference and '1b' numbering introduce a minor navigation gap.	4 / 5
Progressive Disclosure	The single-file body is organized into well-labeled sections with no nested references; the 18-item entity 'Overview' list is the only content that arguably belongs in a separate reference file, a minor organization gap consistent with anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

73%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 is third-person, includes an explicit 'Use when' trigger, and names a distinctive product niche, but its action verbs are generic and its trigger-term coverage lacks synonyms or natural variations.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Otter-specific actions such as 'manage servers, roles, plans, deployments, and configurations'.

Broaden trigger-term coverage with natural phrases users say: 'infrastructure automation', 'Otter deployments', 'server configuration', 'Otter plans'.

Tighten the 'when' clause to name concrete scenarios (e.g. 'Use when the user wants to manage Inedo Otter servers, roles, deployments, or plans').

Dimension	Reasoning	Score
Specificity	Names the domain (Inedo Otter) and a few action areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete like 'extract' or 'fill forms', placing it at the anchor-3 level rather than 4.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Inedo Otter data') are present; the trigger is explicit so it clears the 3-cap, though the 'when' could be more specific, fitting anchor 4.	4 / 5
Trigger Term Quality	The distinctive keyword 'Inedo Otter' is present, but coverage is limited — no synonyms or natural variations like 'infrastructure automation', 'deployments', 'server configuration', or 'Otter', matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The named product 'Inedo Otter' is a highly distinctive niche trigger with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers' anchor.	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/inedo-otter/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.