projects/skills/start-expert/SKILL.md
# Start Expert Session Use when the user needs or you are suggesting specialized expert help. Compose a structured brief from the current conversation context and trigger an expert session. ## Skill Steps 1. **Identify the need**: What specific expertise is required? What should the expert accomplish? 2. **Choose the role**: Select from the expert roster in your CLAUDE.md. Use the exact `name` value. 3. **Compose the brief** — structured handoff with: - **Goal**: What the expert needs to
npx skillsauth add zazig-team/zazigv2 projects/skills/start-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use when the user needs or you are suggesting specialized expert help. Compose a structured brief from the current conversation context and trigger an expert session.
Identify the need: What specific expertise is required? What should the expert accomplish?
Choose the role: Select from the expert roster in your CLAUDE.md. Use the exact name value.
Compose the brief — structured handoff with:
Get machine_id: Read from .claude/workspace-config.json (field: machineId) or from the ZAZIG_MACHINE_ID environment variable.
Call the MCP tool:
start_expert_session({
role_name: "<exact role name>",
brief: "<structured brief>",
machine_id: "<machineId>",
project_id: "<project_id if repo access needed>"
})
Confirm to user: "Expert session started. Your terminal will switch to the expert window. The expert's summary will appear here when done."
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.