kentoshimizu/sw-agent-skills/db-index-strategy

Claude Code and agent skill by kentoshimizu/sw-agent-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Index strategy workflow for balancing read latency, write amplification, and plan stability on critical query paths. Use when query performance depends on index design trade-offs; do not use for high-level conceptual modeling.

Install

npx vskill@latest install kentoshimizu/sw-agent-skills/db-index-strategy

SKILL.md

DB Index Strategy

Overview

Use this skill to choose indexes that improve real workloads while controlling write and storage costs.

Scope Boundaries

  • Query latency hotspots are driven by access-path inefficiency.
  • New query patterns or sort requirements are introduced.
  • Existing indexes show redundancy, bloat, or unstable plans.

Core Judgments

  • Query-path priority by business impact and frequency.
  • Composite key order by filter selectivity and sort usage.
  • Covering/partial/functional index suitability by engine capability.
  • Write amplification and maintenance cost tolerance.

Practitioner Heuristics

  • Indexes should be justified by concrete query families, not single ad hoc queries.
  • Composite index order follows filter-first then sort semantics.
  • Prefer fewer high-value indexes over broad index proliferation.
  • Consider plan stability across parameter distribution, not one explain sample.

Workflow

  1. Rank critical queries by frequency, latency impact, and SLA relevance.
  2. Inspect current plans and identify scans, misestimation, and sort spills.
  3. Propose candidate indexes with expected plan effects.
  4. Evaluate write/maintenance/storage impact for each candidate.
  5. Decide new, modified, and removable indexes as one portfolio.
  6. Record assumptions that require re-evaluation as data distribution changes.

Common Failure Modes

  • Indexes tuned for one tenant or parameter pattern only.
  • Redundant indexes remain after query evolution.
  • Index design ignores heavy write paths and causes throughput collapse.

Failure Conditions

  • Stop when index choices are not tied to prioritized workload.
  • Stop when write amplification risk is unbounded.
  • Escalate when plan stability remains poor after viable candidates.

Security

  • Security scanPassed, 95 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
5
7-day trend score
9

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 5 May 2026, 6 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/kentoshimizu/sw-agent-skills/db-index-strategy/badge)](https://verified-skill.com/skills/kentoshimizu/sw-agent-skills/db-index-strategy)

Something wrong with this skill or its page? Tell us.