onboard

Initialize a claudity-assurance QA environment via guided interview and scaffold files.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/look-itsaxiom/claudity-assurance --skill onboard-look-itsaxiom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/look-itsaxiom/claudity-assurance/tree/main/skills/onboard
Command: npx skills add https://github.com/look-itsaxiom/claudity-assurance --skill onboard-look-itsaxiom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a guided, repeatable process to create an isolated claudity-assurance QA environment so solo developers can verify system behavior without exposing source code or implementation details.

Core Features & Use Cases

  • Interview-driven onboarding: Conduct a one-question-at-a-time interview to capture system type, access method, auth, environment needs, and a high-level system map.
  • Scaffold and document: Create CLAUDE.md, bdds/, docs/, tests/, results/, and changelog.md and add lightweight knowledge graph entries based on interview answers.
  • Configure and validate interaction layer: Recommend tools via web search, set up MCP or helper scripts as needed, and run a connectivity/smoke check; optionally seed initial BDDs to validate the verification workflow.
  • Use case: A solo developer wants to start black-box QA in an empty directory; the skill interviews the user, configures the interaction surface, and scaffolds the QA workspace.

Quick Start

Say 'onboard this project' inside an empty QA directory to start the interview and scaffold the claudity-assurance QA environment.

Frequently Asked Questions about onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a black-box QA environment without exposing source code?

To set up a black-box QA environment without exposing source code, use a guided onboarding interview to scaffold an isolated workspace with CLAUDE.md, knowledge graph files, and BDD scenarios, verifying system behavior through an interaction layer.

How do I scaffold BDD scenarios and a knowledge graph for a new QA project?

You can scaffold BDD scenarios and a knowledge graph by running an interactive onboarding interview in an empty directory, which automatically generates bdds/, docs/, tests/, and lightweight knowledge graph entries based on your system map answers.

Can I use a guided interview to configure QA tooling for web, API, and game systems?

Yes, the onboarding interview captures your system type and access method to recommend tooling via web search, configuring the interaction layer and seeding initial BDDs for web, API, desktop, mobile, or game systems.

What is an isolated claudity-assurance QA environment used for?

An isolated claudity-assurance QA environment is used to provide a repeatable process for solo developers to verify system behavior externally, ensuring source code and implementation details remain completely unexposed during testing.

Do I need an empty directory to start a black-box testing onboarding session?

Yes, you need an empty or near-empty directory to start the black-box testing onboarding session, because the process performs pre-flight checks for source code presence before scaffolding the QA workspace and interaction layer.