Skills

Reviews claims in a document for accuracy and verifiability. Extracts discrete factual statements, rates each as supported, unsupported, or needs-verification, flags logical inconsistencies and unsourced numbers, and suggests what evidence would confirm or refute each claim. Designed to reduce hallucinated or outdated facts before publishing.

Inspects messy tabular data and produces a repeatable cleaning plan plus code. Detects and fixes common issues: inconsistent types, duplicate rows, missing values, malformed dates, mixed encodings, whitespace and casing problems, and outliers. Outputs pandas or Polars code, a summary of changes, and a validation checklist.

Turns customer results into a persuasive, credible case study. Structures the story as challenge, solution, and measurable results, weaves in quotes and concrete metrics, keeps claims verifiable, and ends with a clear call to action. Produces a publish-ready draft plus a one-paragraph summary and pull-quote suggestions.

Designs surveys that produce reliable, unbiased data. Turns research goals into clear questions, chooses appropriate scales and response types, avoids leading and double-barreled wording, orders questions to reduce bias, and plans screening and branching logic. Outputs a ready-to-field questionnaire with an analysis plan for each question.

Helps turn a game concept into a structured game design document. Captures the core loop, mechanics, progression, economy, controls, level structure, art and audio direction, and target platform and audience. Keeps scope realistic, flags dependencies and risks, and produces a living GDD that a small team can build from.

Designs and implements rate limiting for APIs and services. Recommends an algorithm (token bucket, leaky bucket, fixed or sliding window) for the use case, defines per-key and per-endpoint limits, plans distributed enforcement with Redis, and specifies response headers and 429 handling with retry-after. Produces a design plus reference implementation.

Generates and refactors dbt models for analytics engineering. Writes staging, intermediate, and mart models following layered conventions, adds schema.yml tests and descriptions, applies incremental and materialization strategies, and structures sources and refs correctly. Produces SQL plus YAML that fits dbt best practices and is ready to run.

Produces structured test plans for features and releases. Defines scope and objectives, derives test cases from requirements and acceptance criteria, covers functional, edge, negative, performance, and accessibility cases, sets entry/exit criteria, and maps risk to test priority. Outputs a clear plan with a traceability matrix linking tests to requirements.

Writes idempotent Ansible playbooks and roles from a described target state. Structures tasks with proper handlers, variables, and templates; favors modules over shell commands; applies role-based layout and inventory grouping; and adds check-mode safety and tags. Produces playbooks that are re-runnable without unintended side effects.

Sets up and maintains Git hooks for a repository. Recommends a manager (Husky, Lefthook, or pre-commit), wires up pre-commit and commit-msg hooks for linting, formatting, type checks, secret scanning, and conventional-commit validation, and keeps hooks fast with staged-file filtering. Produces config plus a short contributor guide.

Builds discovery and usability interview guides that surface real insight. Translates research questions into open, non-leading prompts, sequences warm-up to deep-dive topics, adds follow-up probes, and applies techniques like the "five whys" and past-behavior questions. Outputs a timed guide with a consent intro and a synthesis template for notes.

Turns analysis results into a clear narrative for a specific audience. Selects the key message, orders findings for impact, recommends the right chart for each point, writes plain-language takeaways, and frames actionable recommendations. Helps analysts move from raw numbers to a memo or slide narrative executives can act on.

Builds structured competitive analyses from public information. Maps competitors across positioning, pricing, features, target segments, and go-to-market motion; produces feature-comparison matrices and SWOT summaries; and highlights differentiation gaps and opportunities. Emphasizes citing sources and separating verified facts from inference.

Produces operational runbooks for services and common incidents. Documents prerequisites, step-by-step diagnosis and remediation, exact commands, verification checks, rollback steps, and escalation paths. Structures each runbook so an on-call engineer can follow it under pressure, and keeps destructive steps clearly flagged with safeguards.

Translates requirements and user stories into behavior-driven development scenarios in Gherkin. Writes clear Given/When/Then steps, covers happy paths, edge cases, and negative cases, uses scenario outlines with examples for data-driven tests, and keeps steps declarative and reusable. Optionally scaffolds step definitions for Cucumber or Behave.

Produces production-ready nginx configuration for common scenarios: reverse proxy, load balancing, TLS termination, static file serving, HTTP/2, gzip/brotli, caching, rate limiting, and security headers. Explains each directive, warns about risky defaults, and includes a validation step so the config can be tested before reload.

Decodes and reviews JSON Web Tokens and their surrounding auth flow for correctness and security. Explains header and claims, checks algorithm and key handling, validates expiration and audience/issuer claims, and flags common pitfalls such as the alg:none attack, weak secrets, missing validation, and over-long token lifetimes. Never treats token contents as trusted secrets to echo back.

Generates and validates Software Bills of Materials in CycloneDX or SPDX formats. Covers dependency inventory, transitive resolution, license and vulnerability annotation, VEX statements, container image SBOMs, and CI integration for supply-chain compliance. Helps teams meet regulatory requirements and track what is actually shipped.

Scans code, configuration, and git history for leaked credentials such as API keys, tokens, private keys, and connection strings. Classifies findings by severity and false-positive likelihood, and provides safe remediation steps including rotation, history scrubbing, and pre-commit prevention.

Builds robust webhook producers and consumers. Covers signature verification, idempotency keys, retry with exponential backoff, dead-letter handling, event ordering, and replay endpoints, and generates handler code plus tests so integrations survive duplicates and outages.

Defines data contracts between producers and consumers to prevent breaking changes in pipelines. Covers schema definitions, semantic types, freshness and quality SLAs, ownership, versioning, and backward/forward compatibility rules. Generates contract specs (e.g., ODCS-style) and CI checks that fail builds when a producer violates the contract.