CtrlK
BlogDocsLog inGet started
Tessl Logo

fireflies-common-errors

Diagnose and fix Fireflies.ai GraphQL API errors by error code. Use when encountering Fireflies.ai errors, debugging failed requests, or troubleshooting authentication and rate limit issues. Trigger with phrases like "fireflies error", "fix fireflies", "fireflies not working", "debug fireflies", "fireflies 429".

67

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

82%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 tight, highly actionable error-code reference with executable commands and a diagnostic script that includes validation checkpoints. Structure and external references are clear, though the error table is kept inline and a couple of sections could be trimmed.

Suggestions

Add an explicit 're-run the diagnostic script to confirm the fix resolved the error' verification step so the feedback loop is uniform across all error codes, not just auth_failed.

Trim the 'Output' section or fold it into the diagnostic workflow, as it restates outcomes already implied by the fixes.

Consider moving the per-error reference into a separate REFERENCES file and keeping SKILL.md as an overview with pointers, to strengthen progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly lean — each error gets a short message and fix with executable commands, and it avoids explaining what GraphQL is — but the 'Output' section and a few explanatory lines could be trimmed, fitting 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Provides copy-paste-ready bash (curl with auth, jq parsing, set -euo pipefail), a complete TypeScript mutation example, an introspection query, and a full diagnostic script that cover the common cases.

5 / 5

Workflow Clarity

The diagnostic script and the auth_failed 'Test authentication' curl provide real validation checkpoints across a clear diagnose→fix→verify sequence, with only minor gaps (no explicit re-verify step for non-auth errors).

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep, well-signaled external pointers ('See fireflies-rate-limits skill', 'see fireflies-debug-bundle', Resources links); not a 5 because the bulk error reference is inlined rather than split into separate files.

4 / 5

Total

17

/

20

Passed

Description

82%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 well-constructed: it states a concrete purpose, gives explicit 'Use when' guidance, and lists natural trigger phrases for a distinct niche. The only mild gap is specificity, which names just two actions rather than a comprehensive list.

DimensionReasoningScore

Specificity

Names the domain ('Fireflies.ai GraphQL API errors') and two concrete actions ('Diagnose and fix... by error code'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly answers both what ('Diagnose and fix Fireflies.ai GraphQL API errors by error code') and when ('Use when encountering Fireflies.ai errors...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Lists five natural trigger phrases ('fireflies error', 'fix fireflies', 'fireflies not working', 'debug fireflies', 'fireflies 429') giving good keyword coverage, though a few synonyms are absent and file extensions do not apply to this API-debugging skill.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Fireflies.ai GraphQL API error codes) with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.