CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

firebase-hosting-basics

Deploys and configures classic Firebase Hosting for static websites, single-page apps (SPAs), and microservices. Use when deploying static sites/SPAs, setting up custom domains, configuring firebase.json hosting settings (redirects, rewrites, headers, multi-site), or managing preview channels. Don't use for Firebase App Hosting (Next.js/SSR), Auth, Firestore queries/rules, Data Connect, or Crashlytics.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 instructional core is well-structured with excellent progressive disclosure to two real, well-scoped reference files, but the body spends about half its lines on marketing-style product overview (CDN speed, zero-config SSL, key features) that Claude neither needs nor can act on, and it omits any validation cue for the deploy-to-live workflow. Trimming the padded sections and adding a test-on-preview-channel note would raise it substantially.

Suggestions

Remove the Overview and Key Features sections (CDN caching, zero-configuration SSL, etc.) — they are product marketing that Claude already knows or cannot act on; the intro line plus Instructions cover the same ground in a fraction of the tokens.

Drop or compress 'Hosting vs App Hosting' to a single line, since the frontmatter description already carries this boundary verbatim.

Add a one-line validation cue in the Deploying section, e.g. test on a preview channel before promoting to live, pointing to deploying.md's hosting:channel:deploy and hosting:clone commands.

DimensionReasoningScore

Conciseness

Roughly half the body is non-instructional product copy — the Overview paragraph and Key Features bullets ("Files are cached on SSDs at CDN edges", "Zero-configuration SSL is built-in") explain concepts Claude already knows, and the "Hosting vs App Hosting" section duplicates the frontmatter boundary. That is several padded sections, matching anchor 2 rather than the 'some unnecessary explanation' of anchor 3.

2 / 5

Actionability

The emulation section is fully executable ("npx -y firebase-tools@latest emulators:start --only hosting" plus the resulting localhost URL) and the Configuration/Deploying sections route to real reference files with topic-enumerated pointers. It falls short of anchor 5 only because the most common case (deploying) has no inline command in the body itself.

4 / 5

Workflow Clarity

The numbered sections (1. Configuration, 2. Deploying, 3. Emulation) give a clear sequence, but the body contains no validation cue — test-before-live guidance exists only implicitly inside deploying.md's preview-channel content, and deploying overwrites the live site. Steps listed with checkpoints missing/implicit matches anchor 3.

3 / 5

Progressive Disclosure

The body is a clear, well-organized overview with two one-level-deep references (references/configuration.md and references/deploying.md, both verified real and holding the appropriately split detail content), each clearly signaled with descriptive link text and a scope summary. This matches the anchor-5 structure exactly.

5 / 5

Total

14

/

20

Passed

Description

100%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.

An exemplary description: third-person, concise, and specific, with a clear what/when pair and an explicit negative boundary separating classic Hosting from App Hosting and other Firebase products. No changes needed.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "Deploys and configures classic Firebase Hosting", "setting up custom domains", "configuring firebase.json hosting settings (redirects, rewrites, headers, multi-site)", "managing preview channels" — comprehensively covering the domain's main operations rather than leaving minor gaps.

5 / 5

Completeness

It explicitly answers both "what" ("Deploys and configures classic Firebase Hosting for static websites, single-page apps (SPAs), and microservices") and "when" with concrete trigger phrases ("Use when deploying static sites/SPAs, setting up custom domains, ... or managing preview channels"), matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural user phrases are comprehensively covered: "deploying static sites/SPAs", "setting up custom domains", "firebase.json", "redirects, rewrites, headers", "preview channels", with synonyms ("single-page apps (SPAs)") and the key file name present; no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

"classic Firebase Hosting" scopes the niche and the explicit exclusion clause ("Don't use for Firebase App Hosting (Next.js/SSR), Auth, Firestore queries/rules, Data Connect, or Crashlytics") disambiguates from every closely related Firebase skill, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

firebase/agent-skills

Path

skills/firebase-hosting-basics/SKILL.md

Reviewed

Table of Contents

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.