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.
71
88%
Does it follow best practices?
Impact
—
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 other deployment or infrastructure skills by naming the specific product and toolchain.
| 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-structured, highly actionable deployment guide with clear multi-phase sequencing, concrete commands, and good error handling. Its main weakness is that all content lives in a single long file with no progressive disclosure to supporting documents, which is a missed opportunity given the complexity and length. The content is mostly concise for its scope but could be tightened in places.
Suggestions
Split detailed per-service credential collection (Phases 3-5) and post-deployment setup (Phases 9-10) into separate referenced files to reduce the main SKILL.md to an overview with clear navigation links.
Tighten verbose sections—e.g., combine the Slack scope list into a single line, reduce 'Tell the user' phrasing to direct instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient and avoids explaining basic concepts, but it's quite long (~250 lines) with some verbosity that could be tightened—e.g., the Slack scopes list, some hand-holding instructions like 'Tell the user to...' could be more compact. However, given the genuine complexity of a 13-phase deployment, most content earns its place. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands throughout (wrangler, terraform, openssl, curl, gh CLI), specific URLs for credential creation, exact permission lists, and copy-paste ready code blocks. Key details like the PKCS#8 conversion and two-phase Terraform deployment are fully specified. | 3 / 3 |
Workflow Clarity | The 13-phase workflow is clearly sequenced with explicit dependencies (e.g., build before Terraform, Phase 1 before Phase 2 of Terraform, deploy before Slack event subscription setup). Validation checkpoints are present (health check curls in Phase 12, 'Wait for Verified checkmark' in Slack setup, wrangler whoami). Error handling section provides a feedback loop for common failures. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents, despite being ~250 lines covering 13 phases. Phases like GitHub App setup, Slack App setup, and Terraform configuration could benefit from being split into separate referenced files. The numbered phase structure provides some organization but the file is quite long for inline consumption. | 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
bd70437
- 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.