vani-keyed-lists
Build scalable lists with keyed rows and per-item updates
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Build scalable lists with keyed rows and per-item updates
Automatically create GitHub issues when DataQL errors occur, with duplicate validation. Use when DataQL commands fail or produce unexpected errors.
This skill should be used when the user asks to "write SQL", "optimize a query", "explain this SQL", or needs help with database queries and SQL best practices.
WHAT: Transform API responses into domain models with transformers, helpers, and utilities. WHEN: converting API data shapes, implementing data pipelines, organizing transformation logic. KEYWORDS: transformer,...
Complete knowledge of the PostgreSQL schema, Prisma ORM patterns, indexes, and migration workflows.
When writing complex features or significant refactors or user ask explicitly, use an ExecPlan from design to implementation.
Analyze McDougall-style fuel business data (SQLite via Laravel) to answer business questions, build KPIs, propose dashboards, and deliver actionable insights for operations leadership.
Neon PostgreSQL serverless database - connection pooling, branching, serverless driver, and optimization. Use when deploying to Neon or building serverless applications.
Generates detailed chapter outlines for books, including key scenes, plot progression, character arcs, and themes. Use this when planning book structure or expanding story ideas.
This skill should be used when the user asks to "track metrics", "calculate ARR", "what metrics should I track", "benchmark my metrics", "understand churn", "calculate LTV", "what is burn multiple", "GMV calcul...
State file management techniques for explicit workflow state tracking with multi-item backlog support
Problem-solving decision tree for when you're blocked. Matches stuck-type to solution strategy.
Select and execute a single legacy reskin checklist item by priority (repositories before services) and by fewest dependencies; use when choosing the next item from docs\progress\checklist.md or when progressin...
Perform a thorough code review with Staff Software Engineer rigor, grounded in ticket context and relevant documentation.
Execute the legacy reskin workflow for a single, already-selected checklist item (service or repository); use after selection to perform extraction, adapter wiring, tests, and checklist updates.
Best practices for creating GitHub pull requests including conventional commits, PR formatting, and multi-language support (en/ja). Use when creating PRs, writing PR descriptions, or formatting commit messages.
MANDATORY before creative work - exploring user intent, requirements and design before implementation. Use for feature design, component planning, or any creative development work.
Analyze git repository changes, branch differences, and commit history. Use when analyzing branches, comparing changes, examining commit history, or preparing for PR/commit operations.
Generate a checklist for the legacy reskin given a specific criteria
Create diagrams with Mermaid.js v11 syntax. Use for flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, state diagrams, architecture diagrams, timelines, user journeys.
Techniques for analyzing existing codebases to reverse-engineer requirements and understand business logic. Use when conducting brownfield analysis or understanding existing system capabilities.
Scan and aggregate task checkboxes from Speckit (.specify/) and context-planning (specs/) formats into a unified backlog.yaml, with automatic project context analysis and auto-update capabilities.
Decomposes a plan file into beads with epics, dependencies, and self-documenting context. Use when you have a comprehensive feature specification or implementation plan that needs to be broken into actionable,...
Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also tri...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.