ericrisco/rsc-harness / skills/firebase
firebase
VerifiedUse when building on Firebase — Firestore data modeling, Security Rules, Auth and custom claims, Cloud Functions, Storage, modular Web/Admin SDK imports — including symptoms like a database open to the internet, a query rejected by rules, or a doc stuck at ~1 write/sec. NOT managed-Postgres BaaS with SQL and RLS (that is supabase).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| evals/README.md | markdown | 944 B |
| evals/cases.yaml | config | 4.2 KB |
| references/cloud-functions.md | markdown | 3.9 KB |
| references/data-modeling.md | markdown | 3.9 KB |
| references/security-rules.md | markdown | 4.8 KB |
| scripts/verify.shexecutable | script | 4.2 KB |
evals/README.md
View on GitHub# Eval harness — `firebase`
`cases.yaml` is a human/LLM-graded trigger-and-capability set; there is no automated runner in this
folder. To run it, feed each prompt to the routing model with only the `firebase` skill discoverable
and check that `should_trigger` prompts fire it (run 3–5 trials each, since the decision is
stochastic) while `should_not_trigger` prompts stay quiet and would plausibly route to the named
sibling. For each `capability` scenario, run the prompt with and without the skill loaded and grade
the answer against its `must_include` rubric — one point per bullet that is specifically and
correctly covered, not merely name-dropped. The skill passes when triggering is right on the large
majority of cases and the capability answer covers the rubric (and clearly beats the no-skill
baseline). Grade by hand or via the repo's shared eval harness; record trial counts and per-bullet
verdicts so a reviewer can audit.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |