dave-tools

Query and transform CSV and Parquet files using DuckDB SQL. Use when: (1) Querying CSV or Parquet files with SQL, (2) Transforming data between CSV/Parquet formats, (3) Aggregating, filtering, or joining data files, (4) Exporting query results to files, (5) Working with large datasets that need columnar analysis. Triggers on requests involving data analysis, file querying, format conversion, or SQL operations on CSV/Parquet files.

Review the changes on the current git branch compared to its base branch on remote. Produces: (1) a summary of what the changes do, (2) issues and recommendations ranked by priority using 🔴 Critical / 🟠 High / 🟡 Medium / 🟢 Low severity, and (3) an overall quality rating. Use when the user says "review branch", "review my changes", "review this PR", "review the current branch", or wants a quality assessment before opening a pull request.

End-of-session skill that reflects on what happened, identifies skill gaps and friction points, and proposes concrete improvements to the skills that were used. Edits skill files directly — tracing global skills back to their source repo via embedded provenance comments. Use when the user says "wrap up", "improve our skills", "self-improve", or at the end of any session that involved repeated manual patterns, corrections, or skill underperformance.

Use when the user asks questions about infrastructure dependencies across repositories in an AWS organization. Covers: blast-radius analysis ("if I change X, what breaks?"), resource ownership ("which repo owns this IAM role / VPC / S3 bucket?"), dependency tracing ("what does repo A depend on?"), and cross-repo change planning ("which repos need coordinated changes for this feature?"). Requires INFRA-MAP.md and infra-graph.json to be present (generated by the infra-compose tool). Trigger phrases: "blast radius", "which repo owns", "what depends on", "infra map", "dependency map", "cross-repo", "if I change", "which repos are affected", "infrastructure graph".

GitLab CI/CD pipeline expert for creating and configuring `.gitlab-ci.yml` files. Use when working with GitLab pipelines for: (1) Creating or editing `.gitlab-ci.yml` pipeline configurations, (2) Configuring jobs, stages, rules, `needs`, and includes, (3) Setting up CI/CD variables (masked, protected, external secrets), (4) Configuring caching and artifacts, (5) Setting up pipeline triggers, schedules, child/multi-project pipelines, (6) Runner configuration and image handling, (7) Security scanning integration (SAST, secret detection, dependency scanning), (8) Pipeline speed optimization and best practices, (9) Troubleshooting pipeline failures.

Systematic debugging methodology that finds root causes before attempting fixes. Use for ANY technical issue: test failures, bugs, unexpected behavior, performance problems, build failures, integration issues. Use ESPECIALLY when under time pressure, when a "quick fix" seems obvious, or when multiple prior fixes have failed. Enforces a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Interactive brainstorming and idea evaluation framework for generating and assessing novel ideas across any domain. Use when users want to: (1) Generate new ideas for projects, features, products, or strategies, (2) Brainstorm solutions to problems, (3) Evaluate and prioritize existing ideas, (4) Explore opportunities in software design, AI/ML, architecture, startups, or business planning, (5) Run structured ideation sessions, or (6) Analyze and compare multiple concepts. Triggers on requests for brainstorming, ideation, creative thinking, idea generation, concept evaluation, or opportunity exploration.

Manage QEMU/KVM virtual machines on Proxmox VE using the qm command-line tool. Use when working with Proxmox VE for: (1) VM lifecycle operations (create, start, stop, destroy), (2) Cloning VMs and creating templates, (3) Snapshot management and rollback, (4) VM migration between nodes, (5) Disk operations (import, resize, move), (6) Guest agent interactions, (7) Cloud-init configuration, (8) Any task involving the 'qm' command or Proxmox VM management.

Configure and use Taskfile (task automation tool) for project build workflows. Use when users want to: (1) Create or configure a Taskfile.yml, (2) Add/modify tasks for building, testing, deploying, or other automation, (3) Set up task dependencies and variables, (4) Configure watch mode, parallel execution, or advanced features, (5) Troubleshoot Taskfile issues, (6) Organize tasks across multiple files with includes.