CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

83%

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.

A well-structured, concise overview that uses progressive disclosure effectively to split platform-specific detail into one-level-deep references. The main weakness is actionability within the body itself, which relies on delegation to bundle files and external documentation rather than providing concrete executable guidance inline.

Suggestions

Add one small inline code snippet or concrete command (e.g., a minimal Crashlytics init example or the gradle/CocoaPods dependency line) so the body is actionable without requiring a reference hop for the common case.

Expand the SDK Usage feature list from abstract bullets ('Add custom keys') into one-line concrete API calls or method names so Claude knows what to invoke without consulting external docs.

Make the setup sequence's implicit checkpoints explicit (e.g., 'After adding the dependency, sync Gradle / run pod install before building') to strengthen workflow clarity for the provisioning steps.

DimensionReasoningScore

Conciseness

Lean overview with no padding or restating of concepts Claude already knows; every section earns its place and detail is correctly deferred to platform-specific reference files.

5 / 5

Actionability

The body itself provides navigation and an abstract feature list ('Add custom keys', 'Add custom logs') rather than concrete executable code or commands; the actionable guidance lives in the referenced bundle files and external docs, leaving key details missing from the body.

3 / 5

Workflow Clarity

A clear logical sequence is present (Prerequisites -> SDK Setup -> SDK Usage) appropriate for a configuration skill, with minor validation gaps and no explicit checkpoints.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to verified bundle files (android_setup.md, ios_setup.md) that themselves link only to external docs, with bulk detail correctly split out and easy platform-based navigation.

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 well-constructed description that clearly states what the skill does and when to use it, with natural trigger terms and a distinct niche. Slightly less granular in enumerating concrete actions, keeping specificity and trigger-term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('provisioning and SDK usage', 'setting up Crashlytics', 'adding crash reporting') with minor gaps in granular coverage, matching the 'lists several specific actions' anchor but not the comprehensive multi-action 5-anchor.

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.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('setting up Crashlytics', 'adding crash reporting', 'Crashlytics SDK') with good coverage, but lacks synonym/extension breadth that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

'Firebase Crashlytics' is a clear product niche with distinct triggers and minimal overlap risk with other skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
firebase/agent-skills
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.