scoobydont-666
- 22 skills
- 0 followers
- 5 hours ago last updated
- ▌ Grill Me · scoobydont-666Structured interrogation methodology for stress-testing plans, designs, and decisions. Resolves decision tree branches through systematic questioning across 8 categories (requirements, constraints, edge cases, failure modes, scalability, security, tradeoffs, integration, maintenance). Invoked by write-a-prd and prd-to-plan during design validation.
- ▌ Hydra Swarm · scoobydont-666Distributed Claude Code coordination v2 — autonomous multi-instance orchestration via NFS + git. Agent registry with heartbeat, priority work queue with capability matching, event bus for cross-agent context, auto git sync, GPU slot management, session lifecycle protocol. Replaces OpenClaw for self-hosted agent coordination.
- ▌ Token Miser · scoobydont-666 bundleMinimize Claude token and cost waste across ALL surfaces — Claude Code subagents, API calls in code, and artifacts. Routes subagent model selection via the Agent tool's model parameter. Recommends /model switches when the current model is overkill or underpowered. Applies to any code importing anthropic or calling /v1/messages. Trigger on: "API call", "artifact", "pipeline", "multi-agent", "LangGraph", "which model", "save tokens", "reduce cost", "claude API", "token usage", "context window", any code importing anthropic or calling /v1/messages, subagent launches, or any discussion about optimizing Claude usage or costs.
- ▌ Code Quality · scoobydont-666 bundleDeep code quality analysis: performance (Big-O, hot paths, resource management), security (injection, secrets, auth, input validation), testability (coverage gaps, untestable design, DI), architecture (SOLID, coupling, abstraction leaks, layering). Language-agnostic with language-specific patterns from references. Trigger on: "code quality", "performance audit", "security review", "OWASP", "SOLID", "coupling", "testability", "technical debt", "code smell", "architecture review", "Big-O", "complexity analysis", "hot path", "memory leak", "injection", "vulnerability", "dependency injection", "clean architecture", "is this code good", or "can this be better". Also triggers on escalation from code-consistency quality triage.
- ▌ Inbound Sync · scoobydont-666Generate a structured sync bundle that captures decisions, architecture changes, conventions, bug fixes, and roadmap updates from the current Claude.ai conversation for ingestion into local Project Swarm projects via Claude Code. Trigger when the user says "sync", "sync project details", "generate sync bundle", "save this for Claude Code", "update local projects", "export decisions", or any variation of requesting that conversation outcomes be persisted to the local codebase. Also trigger at the end of long conversations where significant decisions were made, if the user asks to wrap up or summarize. Do NOT trigger for general summaries unrelated to project sync.
- ▌ Openclaw Ops · scoobydont-666OpenClaw and NemoClaw operations — sandbox management, inference provider config, policy configuration, Tailscale integration, security hardening, skill vetting. Trigger on: "OpenClaw", "NemoClaw", "OpenShell", "sandbox", "openclaw tui", "agent assistant", "ClawHub", "gateway token", or any task involving personal AI assistant deployment and operations.
- ▌ Fleet Manager · scoobydont-666 bundleMulti-machine fleet operations — SSH key management, cross-host syncing, Ansible playbook execution, fleet health checks, and inventory management. Trigger on: "fleet", "SSH to", "sync to", "cross-host", "deploy to", "rsync", "fleet health", "all machines", "inventory", or any task involving coordination between multiple hosts or infrastructure nodes.
- ▌ Session Miser · scoobydont-666 bundleIntelligent model routing for Claude Code sessions. Recommends optimal model (Opus/Sonnet/Haiku) and effort level based on task complexity. Delegates mechanical work to cheaper subagents. Maximizes quality-per-dollar across the entire session. Trigger on: any new session, "save tokens", "cheaper model", "delegate this", "use sonnet", "effort level", "cost", or automatically when task complexity is clearly below the current model's tier.
- ▌ Skill Updater · scoobydont-666Self-assessment and auto-update for Claude Code's installed skills, CLAUDE.md files, and reference data. Audits for staleness, gaps, overlaps, and freshness. Triggers on: "update your skills", "skill audit", "skill assessment", "refresh skills", "are your skills up to date", "check your skills", "review your context", "tune yourself up", "make yourself better".
- ▌ Budi Analytics · scoobydont-666budi token/cost analytics for Claude Code — dashboard access, CLI queries, cost analysis patterns, session tracking. Trigger on: "budi", "token cost", "how much did that cost", "session cost", "spending", "token analytics", "cost dashboard", "usage stats", or any question about Claude Code token consumption or spending patterns.
- ▌ Config Auditor · scoobydont-666Cross-reference all CLAUDE.md files, memory files, skill descriptions, and project registries for contradictions, stale data, and inconsistencies. Trigger on "check for contradictions", "audit configs", "config consistency", "are my configs consistent", or any request to verify configuration coherence across Project Swarm.
- ▌ Cost Optimizer · scoobydont-666Unified cost awareness across Swarm operations. Claude API model routing, infrastructure electricity/TOU costs, mining profitability, cloud hosting budgets.
- ▌ Database Design · scoobydont-666Schema design, migration strategy, index planning, and data lifecycle for SQL databases (PostgreSQL, SQLite). Covers table design, normalization, foreign keys, migration tooling (Alembic, raw SQL), index optimization, retention policies, and schema review. Trigger on: "design schema", "database migration", "add table", "schema review", "index strategy", "data model", "retention policy", "normalize".
- ▌ Ms Office Suite · scoobydont-666Generate professional Excel workbooks, Word documents, PowerPoint decks, and PDFs, including CPA-grade financial reports, cost analyses, ROI projections, executive summaries, budgets, and break-even reports. Uses python-docx, openpyxl, python-pptx, reportlab, weasyprint, and Markdown. Use when asked to generate a report, spreadsheet, PDF, pitch deck, presentation, financial projection, cloud-cost analysis, or other Microsoft Office-style deliverable.
- ▌ Claude To Cursor · scoobydont-666Convert Claude Code skills to Cursor-compatible rules (.mdc/.md files) for sharing or use in Cursor workspaces. Does NOT modify local Claude Code setup — outputs go to a separate repo. Trigger on: "convert to cursor", "cursor rules", "port to cursor", ".mdc", "cursor format", or any request to export skills for Cursor users.
- ▌ Code Consistency · scoobydont-666 bundleEnforce, review, and generate consistent code across registered languages: Python, Golang, Bash/Shell, Rust, PowerShell, Terraform, Ansible. Auto-expands when new languages are encountered. Includes inline quality triage (performance, security, testability, architecture smells). Trigger on: "consistency", "style", "conventions", "review my code", "refactor", "clean up", "idiomatic", "linting", "best practices", "code review", "code smell", or when code is present and a consistency/quality task is implied. Also trigger when generating code alongside existing snippets. Do not wait to be asked explicitly — if code is present, use this skill.
- ▌ Model Evaluation · scoobydont-666LLM evaluation methodology — side-by-side comparison, domain-specific benchmarking, regression detection for fine-tuned models. Trigger on: "evaluate model", "benchmark", "model comparison", "A/B test models", "model quality", "accuracy test", "regression test model", or any discussion about measuring LLM output quality.
- ▌ Ansible Hardening · scoobydont-666Codify security hardening into reusable Ansible roles — CrowdSec IDS, fail2ban, auditd, Tailscale VPN, Semaphore UI, scoped sudoers, systemd sandboxing, and UFW firewall management. Trigger on: "harden with Ansible", "Ansible security", "CrowdSec role", "fail2ban role", "auditd role", "Tailscale Ansible", "Semaphore role", "sudoers role", "security playbook", "fleet hardening", or any request to automate security configurations that were done manually.
- ▌ Container Sandbox · scoobydont-666Run risky or destructive operations inside ephemeral Docker containers for isolation. Use when executing untrusted scripts, destructive Ansible playbooks, or operations that could damage the host.
- ▌ Infosec Architect · scoobydont-666 bundleSecurity architect persona with CISSP/GSE/OSEE-depth expertise. Hardening infrastructure, reviewing code for vulnerabilities, auditing Docker Swarm GPU clusters, securing OpenClaw/NemoClaw agent deployments, and red-teaming your own systems. Trigger on ANY security topic: firewall rules, SSH hardening, TLS configuration, container isolation, Docker daemon security, secrets management, network segmentation, CVE triage, vulnerability assessment, pen testing, exploit analysis, threat modeling, OWASP, prompt injection, agent security, sandbox escape, OpenShell policies, NemoClaw hardening, ClawHub skill vetting, WebSocket security, RBAC, IAM, zero trust, SIEM, incident response, forensics, malware analysis, supply chain security, credential rotation, API key management, secure coding review, NIST frameworks, CIS benchmarks, or any mention of 'is this secure', 'harden this', 'security audit', 'attack surface', 'lock this down'. Even casual security questions trigger this skill.
- ▌ Project Management · scoobydont-666Autonomous work execution across all Swarm projects. Reads last session summary, picks highest-priority work, executes it, then loops to the next item. Only stops when blocked on the operator or nothing remains. Trigger on: "what's the status", "project status", "what needs work", "prioritize", "what's next", "plan work", "coordinate", "which projects", "phase status", "roadmap", "backlog", "session start", "session end", "wrap up", "what should I work on", "keep going", "crank it out", or any request to understand or organize work across multiple Swarm heads.
- ▌ Verification Before Completion · scoobydont-666Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always