CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

firebase-crashlytics

Comprehensive guide for Firebase Crashlytics, including provisioning and SDK usage. Use this skill when the user needs help setting up Crashlytics, adding crash reporting, or using the Crashlytics SDK in their application.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 an exemplary hub: lean, well-structured, with verified one-level-deep platform references. Its weakness is that the SKILL.md itself carries almost no executable guidance — key actions like installing the MCP server or trying the SDK are delegated to references or another skill without commands or paths, leaving the body's actionability incomplete.

Suggestions

Add the MCP server install command directly in Prerequisites (e.g., `npx -y firebase-tools@latest`) instead of only naming the step — currently the command exists only in the frontmatter compatibility note.

Include one minimal inline snippet for the most common SDK usage task (e.g., logging a custom key or setting a user identifier) so the body is actionable without opening a reference file.

Give the `firebase-basics` cross-skill reference an explicit path (as the reference files themselves do, e.g., `firebase_basics/references/android_setup`) so the prerequisite step is followable.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no padding: it never explains what Crashlytics is or how crash reporting works, and every section is navigational ("choose your platform", "consult the documentation for your platform"). Only trivial framing ("The SDK provides a number of features...") could be trimmed, which still fits the 5 anchor's "every token earns its place" better than the 4 anchor's "minor instances of over-explanation".

5 / 5

Actionability

Some concrete guidance exists — prerequisites are named ("a Firebase project and a Firebase app"), platform paths link to real reference files, and the four SDK features are listed — but the body itself contains no executable commands or code. "Install the MCP server in the Firebase CLI" gives no command (the `npx -y firebase-tools@latest` invocation only appears in the frontmatter), and "See the `firebase-basics` skill for references" has no path. This matches the 3 anchor ("some concrete guidance but incomplete; missing key details") rather than 4, which requires mostly executable code or commands.

3 / 5

Workflow Clarity

The sections sequence a clear progression — Prerequisites → SDK Setup → SDK Usage — with unambiguous platform branching. It is not 5 because there are no validation checkpoints (e.g., verifying the SDK is initialized or crashes flow before customizing) and the "Prerequisites" step delegates verification entirely to another skill; it is above 3 because the sequence itself is complete and well-ordered.

4 / 5

Progressive Disclosure

Scored against the actual bundle: all three referenced files (references/android_setup.md, ios_setup.md, web_setup.md) exist, are substantive platform guides, and are exactly one level deep, clearly signaled per platform. The body is a concise overview that appropriately pushes detail to references, matching the 5 anchor ("clear overview with well-signaled one-level-deep references; content appropriately split").

5 / 5

Total

17

/

20

Passed

Description

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

A strong description: third-person voice, explicit "Use this skill when..." triggers, and a well-defined Crashlytics niche. Its main weaknesses are minor — some trigger synonyms (crashes, stack traces) are missing and the crash-data-analysis capability goes unmentioned.

DimensionReasoningScore

Specificity

Names several concrete actions — "provisioning and SDK usage", "setting up Crashlytics, adding crash reporting, or using the Crashlytics SDK" — with minor gaps (e.g., reading/analyzing collected crash data is not mentioned). Not a clean 5 because coverage omits a real capability and the listed actions partially repeat each other; clearly above the 3 anchor's "1-2 concrete actions, not comprehensive".

4 / 5

Completeness

Explicitly answers both: what ("Comprehensive guide for Firebase Crashlytics, including provisioning and SDK usage") and when ("Use this skill when the user needs help setting up Crashlytics, adding crash reporting, or using the Crashlytics SDK"), with concrete trigger phrases. The "when" clause is specific with three distinct triggers, matching the 5 anchor rather than the 4 anchor where "'when' could be more explicit".

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Crashlytics", "crash reporting", "setting up", "SDK" are phrases users would naturally say. Missing common variations like "crashes", "crash logs", "stack traces", or "error reporting", so it falls just short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"Firebase Crashlytics" is a clear niche with distinct, product-specific triggers; the description would not naturally fire for unrelated skills. Only negligible overlap risk with closely related Firebase skills, matching the 5 anchor's "clear niche with distinct triggers; minimal conflict risk".

5 / 5

Total

18

/

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-crashlytics/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.