Run a Booley QA mission
openbooklet.com/s/run-a-booley-qa-missionopenbooklet.com/s/[email protected]GET /api/v1/skills/run-a-booley-qa-missionUse this skill only when the user explicitly invokes it. This is behavioral guidance for clients without enforceable invocation metadata.
This skill owns Booley setup from **Step 0 (plan)** through **Step 7 (cleanup)**, plus an **optional post-gate Step 5 (parity)** for projects that want their Booley results cross-checked against the repo's native build system. The parts outside it are installation and Host Bootstrap in [the install
Prepare sanitized Booley feedback for manual submission from an offline container. Use for bugs, documentation contradictions, confusing behavior, opinions, or feature wishes. Investigate failures, provide a verified workaround where practical, and deliver a report with GitHub and maintainer email handoff options.
Repair a Booley project's environment, configuration, and build-system health by running Doctor, resolving every actionable FAIL and WARN, reviewing packaged release changes after a version update, and verifying the result with plain and deep checks. Use when `booley doctor` is red or warning, an automatic Doctor notice reports problems, Booley reports a pending upgrade review, setup has drifted, a Booley Flow, Specialist, EDA tool, or Target stopped working, or the user asks to heal, repair, or make Doctor green. Hand host-only or otherwise external actions to the user with exact instructions, and route verified Booley or documentation defects through `booley-feedback`.
Auto-indexed from boldaxolotl/booley
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.