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.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/onboarding/SKILL.md

Quality

Content

71%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.

A highly actionable, well-sequenced deployment guide with concrete commands throughout, though it is verbose and monolithic — splitting the per-service setup walkthroughs into reference files would improve navigability and token efficiency.

Suggestions

Move the GitHub App, Google OAuth, and Slack App setup walkthroughs into separate reference files (e.g. references/github-app.md, references/slack-app.md) and link to them from the phase sections to reduce SKILL.md length and improve progressive disclosure.

Tighten or relocate explanatory asides (App Home feature descriptions, per-scope rationale) into the relevant reference files so the main body stays lean.

Add an explicit validate->fix->retry checkpoint inside Phase 8 (e.g. 'If terraform apply errors, review output, fix tfvars, and re-run') rather than relying on the separate Error Handling section.

Dimension	Reasoning	Score
Conciseness	The guide is mostly efficient instructional prose with concrete commands, but at ~370 lines it includes explanatory asides (e.g. App Home feature descriptions, scope rationale) that could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides fully executable, copy-paste-ready bash commands (openssl, gh, wrangler, terraform, vercel, curl) plus specific URLs and exact field values covering the common deployment cases, matching the top anchor.	5 / 5
Workflow Clarity	Thirteen phases are clearly sequenced with a two-phase Terraform gate ('after Phase 1 succeeds') and a final verification phase, but the validate->fix->retry feedback loop is only loosely implied via the error-handling section rather than embedded as explicit checkpoints.	4 / 5
Progressive Disclosure	The file is well-sectioned by phase but is a monolithic 370-line guide with no bundle files; substantial chunks (GitHub App, Slack, Google OAuth setup) that clearly belong in separate reference files are inlined, matching the 'some structure but could be better organized' anchor.	3 / 5
	Total	15 / 20 Passed

Description

87%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.

A strong, third-person description that clearly states both purpose and trigger conditions with concrete named actions tied to a specific product. Minor gains would come from adding a few more synonyms for the trigger terms.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete actions — 'repository setup, credential collection, Terraform deployment, and verification' — matching the 'lists several specific actions; minor gaps' anchor; it falls short of the comprehensive multi-action coverage of a 5.	4 / 5
Completeness	It explicitly answers both what ('Deploy your own Open-Inspect instance... Guides through repository setup, credential collection, Terraform deployment, and verification') and when ('Use when the user wants to set up, deploy, or onboard to Open-Inspect') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	'set up, deploy, or onboard to Open-Inspect' provides good natural terms a user would actually say, but it lacks synonyms and there are no file-extension triggers, so it sits just below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	'Open-Inspect' is a specific named product with dedicated setup/onboard triggers, giving it a clear niche and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: ColeMurray/background-agents
Path: .claude/skills/onboarding/SKILL.md
Commit: 52af550

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.