CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-infra-discover

This skill should be used when the user says "discover tools", "infra discover", "arn infra discover", "arn-infra-discover", "audit tools", "check installed tools", "what tools do I have", "scan for MCPs", "check provider tools", "tool discovery", "discover infrastructure tools", "check my setup", "infra tooling", or wants to audit their installed infrastructure tools (MCPs, CLIs, Claude Code plugins), check authentication state, search for new official tools online, and produce a tooling manifest for the infrastructure workflow.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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, highly actionable four-phase workflow with concrete commands, validation checkpoints, and clean progressive disclosure to real bundle files. The only weakness is minor redundancy in the intro and template phrasing that keeps conciseness at level 2.

Suggestions

Trim the opening paragraph (lines 17-19) which restates the description; the frontmatter already covers the skill's purpose, so the body can jump straight to Prerequisites.

Tighten Phase C's recommendation templates by collapsing the near-identical MCP/CLI/plugin phrasing into one parameterized pattern instead of three separate boilerplate blocks.

Consider shortening the duplicated priority-tag explanations in Phase C and Error Handling, since the Required/Recommended/Optional semantics are already clear from a single statement.

DimensionReasoningScore

Conciseness

Largely lean and actionable with no concept-teaching fluff, but the opening paragraph restates the description and Phase C carries some template padding that could be tightened; it sits at 'mostly efficient but could be tightened' rather than fully lean.

2 / 3

Actionability

Provides fully executable commands (aws --version, aws sts get-caller-identity, etc.), exact file paths, a copy-paste-ready MCP JSON config block, and concrete table schemas — matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Clear four-phase sequence (A-D) with explicit checkpoints (auth-status recording, Phase A/B duplicate cross-reference, confidence ratings, AskUserQuestion gate before mutating .mcp.json) and a comprehensive error-handling section with recovery guidance.

3 / 3

Progressive Disclosure

Body is an overview that signals one-level-deep references via blockquote markers to mcp-registry.md, cli-registry.md, plugin-registry.md, and tooling-manifest-schema.md, all of which exist in ./references/; detailed registry/schema content is appropriately kept out of the body.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 excellent: third-person voice, concrete multi-action capability list, abundant natural trigger terms, and explicit 'use when' guidance all present. It clearly answers what the skill does and when to invoke it with low conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — audit installed tools (MCPs, CLIs, plugins), check authentication state, search online for official tools, and produce a tooling manifest — tied to specific tool categories, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (audit tools, check auth, search online, produce manifest) and 'when' (the literal 'This skill should be used when the user says...' trigger clause), satisfying the explicit-triggers anchor for level 3.

3 / 3

Trigger Term Quality

Includes many natural phrases a user would say ('discover tools', 'audit tools', 'check installed tools', 'what tools do I have', 'check my setup'), giving good coverage of colloquial variations rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear, brand-anchored niche (Arness/arn infra tooling audit, producing a tooling manifest for the infrastructure workflow) with distinctive triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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
AppsVortex/arness
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.