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.
80
76%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/arn-infra/skills/arn-infra-discover/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage and completeness, providing an extensive list of natural phrases users might say and clearly stating both what the skill does and when to use it. Its main weakness is that the capabilities are somewhat buried in a run-on sentence structure rather than being clearly enumerated as distinct concrete actions. The description could also benefit from slightly more structured formatting to improve readability.
Suggestions
Break the capabilities into a clearer list of concrete actions (e.g., 'Audits installed MCPs, CLIs, and Claude Code plugins. Checks authentication state. Searches for new official tools online. Produces a tooling manifest.') rather than embedding them in a long clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (infrastructure tools/MCPs) and lists some actions like 'audit installed infrastructure tools', 'check authentication state', 'search for new official tools online', and 'produce a tooling manifest', but these are somewhat buried in a long sentence and could be more clearly enumerated. | 2 / 3 |
Completeness | The description explicitly answers both 'what' (audit installed infrastructure tools, check authentication state, search for new official tools online, produce a tooling manifest) and 'when' (extensive list of trigger phrases plus 'when the user wants to audit their installed infrastructure tools'). The 'Use when' guidance is effectively present through the opening 'This skill should be used when...' clause. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including many variations users would actually say: 'discover tools', 'audit tools', 'check installed tools', 'what tools do I have', 'scan for MCPs', 'check my setup', 'infra tooling', plus command-style variants like 'arn infra discover' and 'arn-infra-discover'. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a very specific niche around infrastructure tool discovery, MCP scanning, and tooling manifests. The trigger terms are highly specific to this domain and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill excels at actionability and workflow clarity with concrete commands, clear phased sequencing, comprehensive error handling, and explicit validation steps. However, it is significantly over-verbose — inlining detailed command lists, output templates, and recommendation patterns that should live in the referenced registry/schema files. The content would benefit greatly from being trimmed to an overview that delegates specifics to its supporting references.
Suggestions
Move the inline CLI detection commands (A.2), auth check commands (A.3), and recommendation templates (Phase C) into the referenced registry files, keeping only the pattern/algorithm in SKILL.md.
Collapse the output table formats (D.2, D.3) into a reference to the tooling-manifest-schema.md rather than spelling out full table structures inline.
Remove explanatory phrases like 'This skill is proactive: it does not just check what is installed, but actively recommends...' — Claude doesn't need motivation or design rationale, just instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~200+ lines with significant redundancy. It explains concepts Claude already knows (what MCPs are, what CLIs do, what authentication means), repeats patterns across providers, and includes extensive inline detail that could be in reference files. The recommendation templates and table formats are spelled out in full when a brief schema reference would suffice. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance: specific CLI commands for detection (e.g., `aws --version`, `aws sts get-caller-identity`), exact JSON snippets for MCP configuration, specific file paths, and clear install command patterns. Every step has actionable instructions rather than vague descriptions. | 3 / 3 |
Workflow Clarity | The four-phase workflow (Detect → Online Check → Recommendations → Manifest) is clearly sequenced with explicit sub-steps, validation checkpoints (auth checks, confidence ratings), error handling for each failure mode, and feedback loops (auto-configure offers with user approval). The error handling section covers edge cases comprehensively with specific recovery actions. | 3 / 3 |
Progressive Disclosure | The skill references external files appropriately (mcp-registry.md, cli-registry.md, plugin-registry.md, tooling-manifest-schema.md, experience-derivation.md) but then inlines extensive detail that belongs in those reference files — particularly the full CLI detection command lists, auth check commands, recommendation templates, and output table formats. The main SKILL.md should be a concise overview delegating details to the referenced files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- AppsVortex/arness
- Commit
1fe948f
- 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.