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".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger terms and completeness. It clearly identifies the niche (Fireflies.ai GraphQL API errors) and provides explicit trigger phrases. The only minor weakness is that the specific capabilities could be more granular — listing concrete actions like resolving specific error codes or handling particular failure modes.
Suggestions
Add more specific concrete actions such as 'resolve 401 authentication failures, handle 429 rate limits, debug malformed GraphQL queries, interpret error response codes' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Fireflies.ai GraphQL API) and some actions (diagnose, fix errors by error code), but doesn't list specific concrete actions like 'resolve authentication failures, handle rate limiting, parse error responses'. | 2 / 3 |
Completeness | Clearly answers both 'what' (diagnose and fix Fireflies.ai GraphQL API errors by error code) and 'when' (encountering errors, debugging failed requests, troubleshooting auth/rate limit issues) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'fireflies error', 'fix fireflies', 'fireflies not working', 'debug fireflies', 'fireflies 429', plus mentions of authentication and rate limit issues. These are phrases users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific product (Fireflies.ai) and a specific API type (GraphQL). Extremely unlikely to conflict with other skills given the narrow niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-structured error reference skill that provides actionable, executable guidance for each Fireflies.ai error code. Its main strength is the combination of concise error descriptions with copy-paste-ready diagnostic commands. The only notable weakness is the lack of explicit decision-tree logic connecting the diagnostic script output to specific error resolution paths.
Suggestions
Add a brief decision flow after the Quick Diagnostic Script showing how to interpret results and which error section to jump to (e.g., 'If HTTP 401 → see auth_failed; if HTTP 429 → see too_many_requests').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. Each error code gets only the essential information: the error, its cause, and the fix. No unnecessary explanations of what GraphQL is or how APIs work. The diagnostic script and deprecated fields table are practical additions that earn their tokens. | 3 / 3 |
Actionability | Provides fully executable bash scripts for diagnostics and authentication testing, concrete TypeScript code for the bypass_size_check fix, specific curl commands for schema introspection, and precise instructions for each error resolution. All code is copy-paste ready with proper error handling (set -euo pipefail). | 3 / 3 |
Workflow Clarity | This is primarily a reference/lookup skill rather than a multi-step workflow, so strict sequencing is less critical. However, the diagnostic script lacks explicit validation checkpoints or feedback loops — it runs checks but doesn't guide Claude on what to do based on the results (e.g., 'if HTTP 401, proceed to auth_failed section'). The 'Output' section implies a workflow but doesn't define verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, a concise overview, and appropriate references to external resources (fireflies-rate-limits skill, fireflies-debug-bundle, official docs). The error codes are individually navigable with horizontal rules. No deeply nested references or monolithic walls of text. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.