.agents/skills/clawdstrike-desktop-dogfood-loop/SKILL.md
Use when the Huntronomer desktop app needs live dogfooding, reproduction, or smoke validation across the shell, launch overlay, Hunt Deck, Playwright browser flow, Tauri bridge, or OpenClaw and receipt states.
npx skillsauth add backbay-labs/clawdstrike clawdstrike-desktop-dogfood-loopInstall 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 this skill when the job is to prove what the Huntronomer desktop surface actually does, not what the React tree or Tauri code seems like it should do.
Drive toward:
scripts/huntronomer-playwright-smoke.sh for fast shell and launch-overlay checks.cd apps/desktop && bun run tauri:dev.output/playwright/ and keep the failure mode concrete.Run:
scripts/huntronomer-playwright-smoke.sh
This smoke path:
summary.jsonRead apps/desktop/docs/huntronomer-dogfooding.md for environment knobs and current limitations.
Use the relevant subset of:
scripts/huntronomer-playwright-smoke.shcd apps/desktop && bun run typecheckcd apps/desktop && bun run test -- --runcd apps/desktop && bun run buildcargo check --manifest-path apps/desktop/src-tauri/Cargo.tomltesting
A simple skill demonstrating clawdstrike security
tools
# Hello Skill A simple greeting skill that demonstrates secure agent operation. ## Description This skill allows the agent to greet users and perform basic file operations within the allowed workspace. ## Capabilities - Generate personalized greetings - Read files from the workspace - Write greeting logs to the output directory ## Usage Ask the agent: - "Say hello to Alice" - "Read the welcome message from data/welcome.txt" - "Log a greeting for Bob" ## Examples ### Basic Greeting **Us
testing
# bb-edr: Triage Skill Use this skill to turn clawdstrike audit logs into an incident report and a minimal response plan. ## Inputs - `.hush/audit.jsonl` (JSONL) — clawdstrike audit events (allowed/denied, guard, reason). - `policy.yaml` — the active security policy. ## Task 1. Read and summarize the last ~50 audit events. 2. Focus on **denied** events first: - Group by `guard` (e.g., `forbidden_path`, `egress`, `patch_integrity`) - Identify likely intent (misconfiguration vs. suspici
tools
Threat hunting and security event investigation