agentsclimarketplace

Firestore operations manager

Skill ComeOnOliver/skillshub/skills/jeremylongshore/claude-code-plugins-plus-skills/firestore-operations-manager

🧠 The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.

Install
npx -y skills add ComeOnOliver/skillshub --skill firestore-operations-manager

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Manage Firebase/Firestore operations including CRUD, queries, batch processing, and index/rule guidance. Use when you need to create/update/query Firestore documents, run batch writes, troubleshoot missing indexes, or plan migrations. Trigger with phrases like "firestore operations", "create firestore document", "batch write", "missing index", or "fix firestore query".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.8 KB, as published. Nobody here has run it

Firestore Operations Manager

Operate Firestore safely in production: schema-aware CRUD, query/index tuning, batch processing, and guardrails for permissions and cost.

Overview

Use this skill to design Firestore data access patterns and implement changes with the right indexes, security rules, and operational checks (emulator tests, monitoring, and rollback plans).

Prerequisites

  • A Firebase project with Firestore enabled (or a local emulator setup)
  • A clear collection/document schema (or permission to propose one)
  • Credentials for the target environment (service account / ADC) and a plan for secrets

Instructions

  1. Identify the operation: create/update/delete/query/batch/migration.
  2. Confirm schema expectations and security rules constraints.
  3. Implement the change (or propose a patch) using safe patterns:
    • prefer batched writes/transactions where consistency matters
    • add pagination for large queries
  4. Check indexes:
    • detect required composite indexes and provide firestore.indexes.json updates
  5. Validate:
    • run emulator tests or a minimal smoke query
    • confirm cost/perf implications for the query pattern

Output

  • Code changes or snippets for the requested Firestore operation
  • Index recommendations (and config updates when needed)
  • A validation checklist (emulator commands and production smoke tests)

Error Handling

  • Permission denied: identify the rule/role blocking the operation and propose least-privilege changes.
  • Missing index: provide the exact composite index needed for the query.
  • Hotspot/latency issues: propose sharding, pagination, or query redesign.

Examples

Example: Fix a failing query

  • Request: “This query needs a composite index—what do I add?”
  • Result: the exact index definition and a safer query pattern if needed.

Example: Batch migration

  • Request: “Backfill a new field across 100k docs.”
  • Result: batched write strategy, checkpoints, and rollback guidance.

Resources

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.