CtrlK
BlogDocsLog inGet started
Tessl Logo

automox

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

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/automox/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a well-structured, executable guide to driving Automox through the Membrane CLI, with strong command coverage and a genuine state-polling feedback loop. The main weaknesses are minor redundancy and a couple of soft filler passages that could be trimmed.

Suggestions

Remove or condense the introductory 'Automox is a cloud-native platform...' paragraph and the bare entity bullet list, which add little Claude does not already infer.

Label the 'Step 2' target explicitly so the 'skip to Step 2' references resolve unambiguously.

Fold the redundant 'Popular actions' action-list command back into 'Searching for actions' to avoid repeating the same command.

DimensionReasoningScore

Conciseness

The body is mostly lean command-focused documentation, with only minor over-explanation such as the introductory paragraph describing what Automox is and the bare entity bullet list capped by 'Use action names and parameters as needed'.

4 / 5

Actionability

It provides concrete, copy-paste-ready commands throughout (login, connection ensure, action list/run, request proxy) plus a flag table, with only minor placeholder gaps like CONNECTION_ID and --intent "QUERY".

4 / 5

Workflow Clarity

The install → authenticate → connect → poll-for-ready → search → run sequence is clear, and the connection-state branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) forms a feedback loop, but the 'skip to Step 2' reference points to an unlabeled step, a minor gap.

4 / 5

Progressive Disclosure

No bundle files exist, so all content lives in one well-sectioned SKILL.md with clear headers; structure is good, though the 'Popular actions' section redundantly repeats the action-list command from 'Searching for actions'.

4 / 5

Total

16

/

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 clearly targets a distinct product niche and includes an explicit 'Use when' trigger, but its capability list is generic. Tightening 'Manage data, records, and automate workflows' into concrete Automox actions would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Automox actions (e.g., 'List and patch endpoints, manage policies and groups, pull vulnerability reports').

Add natural trigger synonyms such as 'patch management', 'endpoint management', or 'Automox policies' to broaden keyword coverage.

Make the 'what' clause as specific as the 'when' clause so completeness can reach a 5.

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Automox domain and a few action targets, but the verbs are generic rather than concrete operations, matching the 'names domain and 1-2 actions but not comprehensive' anchor.

3 / 5

Completeness

Both halves are present — a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Automox data"), but the 'what' is generic rather than concrete, so it stops short of a 5.

4 / 5

Trigger Term Quality

The trigger "Use when the user wants to interact with Automox data" surfaces the natural keyword "Automox", but offers few variations or synonyms, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

"Automox integration" tied to a specific named product creates a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.