onboarding
Deploy your own Open-Inspect instance. Use when the user wants to set up, deploy, or onboard to Open-Inspect. Guides through repository setup, credential collection, Terraform deployment, and verification with user handoffs.
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
100%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 is a strong skill description that clearly identifies the specific tool (Open-Inspect), lists concrete deployment steps, and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague. The description effectively distinguishes itself from generic deployment or infrastructure skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: repository setup, credential collection, Terraform deployment, and verification with user handoffs. These are clear, actionable steps. | 3 / 3 |
Completeness | Clearly answers both 'what' (guides through repository setup, credential collection, Terraform deployment, and verification) and 'when' (explicit 'Use when the user wants to set up, deploy, or onboard to Open-Inspect'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'set up', 'deploy', 'onboard', 'Open-Inspect', 'Terraform', 'repository setup', 'credentials'. Good coverage of terms a user would naturally use when wanting to deploy this tool. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: deploying Open-Inspect specifically, with distinct triggers like 'Open-Inspect', 'Terraform deployment', and the specific workflow steps. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted deployment guide with excellent actionability—concrete commands, specific URLs, exact permission lists, and clear multi-phase sequencing. The two-phase Terraform deployment and post-deployment configuration steps are well-explained with proper ordering. The main weakness is that the sheer length could benefit from progressive disclosure by splitting service-specific setup details into separate files, and some minor verbosity in credential collection instructions.
Suggestions
Consider splitting service-specific setup guides (GitHub App creation, Slack App setup, Cloudflare credential collection) into separate referenced files to reduce SKILL.md length and improve progressive disclosure.
Trim explanatory text in credential collection phases—e.g., Claude doesn't need to be told what a Cloudflare Account ID is or where dashboard URLs are; just provide the direct links and field names.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long but most content is necessary given the complexity of a multi-service deployment. Some areas could be tightened—e.g., the Phase 1 explanations about what deployment names do, and some hand-holding around where to find credentials—but overall it avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands, specific URLs for service configuration, exact permission scopes, and copy-paste ready Terraform configurations. Each phase has specific, actionable steps rather than vague descriptions. | 3 / 3 |
Workflow Clarity | The 13-phase workflow is clearly sequenced with explicit dependencies (e.g., two-phase Terraform deployment, post-deployment Slack/GitHub setup requiring running workers, build steps before Terraform). Validation is present via health check curls in Phase 12, the Slack URL verification checkpoint, and the error handling section provides feedback loops for common failures. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and phases, but it's a monolithic document (~200+ lines) that could benefit from splitting detailed service configuration (Slack, GitHub App, Terraform vars) into separate reference files. For a skill this complex, inline everything makes the SKILL.md quite long. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- ColeMurray/background-agents
- Commit
e5c55cf
- 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.