Name: extension-to-functions-codebase
Rating: 58.4 (1 reviews)
Author: firebase

extension-to-functions-codebase

Skill for converting an installed Firebase Extension (or extension source) into a standalone Cloud Functions for Firebase codebase or publishable npm package, including V1 to V2 trigger upgrades, lifecycle hooks, and declarative security

Quality

67%

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/extension-to-functions-codebase/SKILL.md

Quality

Content

65%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 content is well-structured, concise, and largely actionable across a clear migration sequence. It loses points for missing validation checkpoints in a destructive workflow and for not signaling the existing reference bundle files.

Suggestions

Add explicit validation checkpoints (e.g., run the preserved jest tests, verify each trigger is V2, confirm dry-run before deploy) to lift workflow_clarity above the destructive-operation cap.

Link the three reference files from the relevant steps (e.g., 'See references/destructuring-shim.md' in Step 3, 'references/configuration-migration.md' in Steps 1-2, 'references/signature-mapping.md' for handler signatures) so progressive disclosure is clearly signaled.

Provide a complete lifecycle hook handler example in Step 4 rather than a one-line mapping, and a concrete README skeleton in Step 5.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and assumes Claude's competence, with only minor over-explanatory phrases such as the concurrency/pricing note and the declarative-IAM framing, placing it at anchor 4 rather than the lean anchor 5.	4 / 5
Actionability	It provides mostly executable guidance (onInit param snippet, peerDependencies JSON, trigger imports) with minor gaps such as one-line lifecycle mappings and an ungenerated README, matching anchor 4 rather than fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	A clear five-step sequence is present, but this destructive/batch migration has no validation or verification checkpoints (no test run, no trigger-upgrade verification), and the rubric caps such workflows at 3.	3 / 5
Progressive Disclosure	Section and step structure exists and reference bundle files are present in references/, but the body never links to them and inlines material (destructuring shim, configuration migration) that belongs in those files, matching anchor 3.	3 / 5
	Total	14 / 20 Passed

Description

70%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 is specific and distinctive, clearly communicating a narrow migration capability with concrete sub-tasks. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when migrating an installed Firebase Extension to a standalone Cloud Functions codebase or npm package, or upgrading 1st Gen triggers to 2nd Gen.'

Include common synonyms users might say (e.g., '1st Gen to 2nd Gen', 'migrate', 'publish') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete actions ('converting... into a standalone Cloud Functions codebase or publishable npm package', 'V1 to V2 trigger upgrades', 'lifecycle hooks', 'declarative security') with minor coverage gaps, matching anchor 4 rather than the comprehensive anchor 5.	4 / 5
Completeness	The description gives a clear 'what' but provides no 'Use when...' trigger guidance, and the rubric explicitly caps completeness at 3 when such a clause is missing.	3 / 5
Trigger Term Quality	Contains natural terms a user would say ('Firebase Extension', 'Cloud Functions for Firebase', 'npm package', 'V1 to V2 trigger upgrades') with good coverage, missing only a few synonyms like '1st Gen to 2nd Gen' or 'migrate', so it sits at anchor 4 rather than 3 or 5.	4 / 5
Distinctiveness Conflict Risk	It targets a narrow, clearly delineated niche (Firebase Extension to Cloud Functions migration) with distinct triggers and minimal overlap with other skills, matching anchor 5.	5 / 5
	Total	16 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: firebase/agent-skills
Path: skills/extension-to-functions-codebase/SKILL.md
Commit: a0b4e14

Reviewed: ~2 hours 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.