grtninja/shockwave-operator-handoff
skill-candidates/shockwave-operator-handoff/SKILL.md
Preserve Shockwave operator handoff across startup, control-rail contract display, chat/status surfaces, and voice/manual recovery behavior. Use when dashboard changes affect how the operator sees mode, authority, services, playback, or degraded-state transitions.
$ install --global
skillsauthnpx skillsauth add grtninja/skill-arbiter shockwave-operator-handoffInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 8:26 PM67.0s3 files scanned
SKILL.md
- name:
- shockwave-operator-handoff
- description:
- Preserve Shockwave operator handoff across startup, control-rail contract display, chat/status surfaces, and voice/manual recovery behavior. Use when dashboard changes affect how the operator sees mode, authority, services, playback, or degraded-state transitions.
Shockwave Operator Handoff
Use this skill when Project Shockwave changes affect the operator-facing handoff between startup, live dashboard state, and the typed local control surface.
Workflow
- Read the target repo
AGENTS.md, README, and startup contract first. - Confirm the repo-owned visible dashboard path still matches the startup wrapper and shim-first authority model:
:9000public plane:2337hosted large-model lane:1234non-authoritative operator surface only
- Inspect the operator handoff surfaces together:
- startup verification script and test
- control rail contract block
- chat/status strip
- app-level event/status handling
- Preserve operator-visible handoff state:
- current mode and profile
- control-plane and display-host authority labels
- active service and phase visibility
- transcript/tool-card continuity
- hot-mic and voice-path state
- interrupted playback resume behavior
- Keep typed bridge/API payloads aligned with what the dashboard labels and summaries claim.
- Re-run startup verification and nearby UI/runtime checks before closing.
Required Evidence
- startup-contract verification output
- operator-facing status snapshot or UI proof
- exact handoff surfaces touched
- note of any remaining degraded-state or authority drift
Guardrails
- Do not let direct LM Studio assumptions override shim-first authority.
- Do not hide offline, degraded, or disconnected service state behind generic labels.
- Keep the lane read-only with respect to vehicle control and autonomy boundaries.
- If startup proof and dashboard status disagree, report the handoff as unresolved.
Best-Fit Companion Skills
$shockwave-dashboard-ops$desktop-startup-acceptance$local-compute-usage$docs-alignment-lock
Scope Boundary
Use this skill only for Shockwave operator handoff and dashboard-state continuity.
Do not use it for:
- generic router or provider changes with no operator-surface effect
- vehicle or hardware integration outside the dashboard handoff
- full cross-app meta-harness alignment
References
references/operator-handoff-checklist.md
Loopback
If this lane is unresolved, blocked, or ambiguous:
- capture the failing startup proof or operator-state drift
- route back through
$skill-hubfor chain recalculation - resume only after the updated chain returns a deterministic handoff repair path
Related Skills
grtninja/white-hat
tools
VerifiedTrustedCommunity
Run a defender-first security sweep on code, configs, prompts, model/tooling surfaces, or third-party contribution lanes. Use when a request involves safe bug, leak, zero-day-class, exploit, or hack hunting for protection, when contributing to outside repositories and you want a focused security pass, or when touching auth, secrets, permissions, network exposure, prompt/tool boundaries, data flow, or update/build surfaces. This skill is defensive only and must never be used for weaponization or unauthorized access.
2SKILL.mdUpdated Apr 22, 2026
grtninja/vrm-sandbox-startup-acceptance
development
VerifiedTrustedCommunity
Validate and repair VRM Sandbox startup acceptance with shim-first local model authority, frontend/backend bring-up, and avatar-runtime launch proof. Use when launch behavior, chat handoff, voice fallback, or runtime bridge acceptance must be verified end to end.
2SKILL.mdUpdated Apr 22, 2026
grtninja/voice-catalog-runtime-alignment
documentation
VerifiedTrustedCommunity
Align documented voice-command catalogs, endpoint action allowances, and live runtime handlers so operator-visible voice surfaces match what the stack can actually execute. Use when voice command docs, parser matrices, endpoint permissions, or runtime action routing drift apart.
2SKILL.mdUpdated Apr 22, 2026
grtninja/skillhub-trend-radar
development
VerifiedTrustedCommunity
Track SkillHub trend and topic drift, maintain a bounded rewrite watchlist, and surface emerging gaps worth turning into repo-owned skills. Use when the marketplace query set shows new families or when the current shortlist has gone stale.
2SKILL.mdUpdated Apr 22, 2026