SKILLEMALL.ai
GitHub ↗ RU Sign in

BB firebase-basics

Provides foundational Firebase CLI setup, CLI installation, version checks (`firebase-tools@latest --version`), CLI login (including --no-localhost), project creation, project selection (`firebase use`), and app config file downloads (`google-services.json`, `GoogleService-Info.plist`). Use ONLY for CLI login, project creation/switching, or downloading app config files. Don't use for Firebase Hosting deploy, Firestore, Auth, App Hosting, Data Connect, Crashlytics, or Remote Config.

firebase/agent-skills Agent Skills author: firebase Apache-2.0 20 files body ≈ 1 664 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Provides foundational Firebase CLI setup, CLI installation, version checks (firebase-tools@latest --version), CLI login (including --no-localhost), project…

As a process B 65/100 · Nearly there — weak spots: result and completion

IntegrationFirebaseInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
95
Quality 40%
92
Run on models
none yet
Process rating
B
65/100
Nearly there
Result and completion w 14
0
When it triggers w 12
50
Failures and branches w 10
55
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Dangerous commands cmd-shell-rc references/flutter_setup.md:21
      Writes to a shell startup file
      echo 'export PATH="$PATH:$HOME/development/flutter/bin"' >> ~/.zshrc

    Files scanned: 20. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 65/100

    • 0Result and completion. Does not say what the result is
    • 50When it triggers. No condition that starts the skill
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 33 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1664 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 486: enough signal without eating the budget
    • +4Structure: 4 headings
    • +3Step-by-step instructions: 33 items
    • +4Has examples (3 code blocks)
    • +4Reference files are cited in the instructions (6 of 7)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.