Name: firebase-admin-sdk
Rating: 59.2 (1 reviews)
Author: membranedev

firebase-admin-sdk

Firebase Admin SDK integration. Manage data, records, and automate workflows. Use when the user wants to interact with Firebase Admin SDK data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/firebase-admin-sdk/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, command-driven integration guide with excellent actionability and a clear, validated connection workflow. Its main weaknesses are a conceptually padded opening paragraph and an unlabeled 'Step 2' reference that slightly muddies workflow navigation.

Suggestions

Trim or remove the opening conceptual paragraph ('The Firebase Admin SDK is a set of server-side libraries...') and the promotional 'so you can focus on the integration logic' phrasing, since Claude already knows what the Firebase Admin SDK is.

Label the workflow steps consistently (e.g. an explicit 'Step 2: Searching for actions' header) so the 'skip to Step 2' reference resolves unambiguously.

Add a brief output-validation note after running actions (e.g. checking the `output` field and handling non-zero/error states) to complete the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but the opening paragraph ('The Firebase Admin SDK is a set of server-side libraries...') and promotional phrasing ('so you can focus on the integration logic rather than auth plumbing') explain concepts and motivations Claude already knows.	3 / 5
Actionability	Provides fully executable, copy-paste-ready CLI commands covering install, login, connection setup, action search, action execution, and proxying, with clearly marked placeholders and a complete options table.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state checks and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll after user action), but the 'skip to Step 2' reference points to an unlabeled target and there is no post-action output validation.	4 / 5
Progressive Disclosure	The content is well-organized with clear single-level section headers and no nested or broken references, but all material is inlined (e.g. the full clientAction field breakdown and proxy options table) with no overview-pointing-to-detail references, and the ~165-line body exceeds the simple-skill exception.	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly names its Firebase Admin SDK niche and includes an explicit 'Use when' trigger, satisfying both what and when. However, the action list is generic ('manage data, records, automate workflows') rather than naming concrete Firebase capabilities, and trigger keywords lack natural synonyms.

Suggestions

Replace generic actions with concrete Firebase Admin SDK capabilities, e.g. 'Manage users, mint custom tokens, send push notifications, and access Realtime Database / Firestore data.'

Add natural trigger synonyms users would say, such as 'Firebase Auth', 'custom tokens', 'FCM/push notifications', 'Firestore', or 'Realtime Database'.

Sharpen the 'Use when' clause to reference concrete scenarios, e.g. 'Use when the user needs server-side Firebase access: user management, custom tokens, session cookies, Cloud Messaging, or database access from a backend.'

Dimension	Reasoning	Score
Specificity	Names the domain clearly and lists several action areas ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Firebase capabilities like user management, push notifications, or Realtime Database access.	3 / 5
Completeness	Both 'what' ('Firebase Admin SDK integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Firebase Admin SDK data.') are present, but neither is highly specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	The core term 'Firebase Admin SDK' is repeated, but no natural synonyms or related-service keywords users would say (Firestore, Firebase Auth, FCM, Realtime Database) are included.	3 / 5
Distinctiveness Conflict Risk	The 'Firebase Admin SDK' niche is well-defined and distinct, but the generic trigger phrasing ('interact with Firebase Admin SDK data') leaves minor overlap risk with a closely related general Firebase or Firestore skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/firebase-admin-sdk/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.