smithery/baskarajati

Firestore Index Sync

Detect and fix drift between documented and actual Firestore indexes

Installation

$ npx skills add smithery/baskarajati --skill firestore-index-sync

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/baskarajati.

npx skills add smithery/baskarajati

Browse all from smithery/baskarajati

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,398 B
  • docs SUMMARY.md 96 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Firestore Index Sync Skill

Purpose

Keep FIRESTORE_INDEXES.md and firestore.indexes.json aligned to prevent query errors.

When to Use

  • Indexes added or removed
  • Query errors indicate missing indexes
  • Documentation updates

Inputs

  • FIRESTORE_INDEXES.md
  • firestore.indexes.json

Outputs

  • Drift report under .agent/artifacts/{conversation-id}/firestoreindexsync.md
  • Minimal patch to align docs and JSON

Prerequisites

  • Awareness of active query patterns

Tools & Availability

  • Local editor + rg for diffing
  • Optional JSON formatter (manual if unavailable)

Methodology

  1. Compare index definitions between MD and JSON.
  2. Identify mismatches (collection, fields, order, query scope).
  3. Update the minimal source of truth (prefer JSON for actual indexes).
  4. Sync documentation to match exact definitions.

Verification

  • Every index in JSON is documented in FIRESTORE_INDEXES.md
  • Documentation contains no indexes missing in JSON
  • File formatting preserved (minimal diff)

Pass/Fail: Pass only if all checks above are satisfied.

Risks & Mitigations

  • Updating docs only → ensure JSON is authoritative
  • Formatting churn → keep minimal line changes