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".
68
84%
Does it follow best practices?
Impact
—
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 guidance on when to use it. The only minor weakness is that the specific capabilities could be slightly more detailed in listing concrete actions beyond 'diagnose and fix'.
| 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
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable error reference skill that efficiently covers Fireflies.ai API error codes with concrete fixes and executable diagnostic scripts. Its main strengths are conciseness and actionability—every section provides specific, copy-paste-ready solutions. The weaknesses are minor: the diagnostic workflow could benefit from explicit conditional branching (if error X, do Y), and the references to other skills/bundles that don't exist in the bundle reduce the progressive disclosure score.
Suggestions
Add conditional logic to the diagnostic script (e.g., 'if HTTP 401, regenerate API key; if HTTP 429, check rate limit plan') to create a proper diagnose-fix-verify feedback loop.
Consider splitting the deprecated fields table and network errors into a separate reference file if the bundle structure supports it, keeping SKILL.md focused on the most common error codes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Each error code section provides only the essential information: the error message, the cause, and the fix. No unnecessary explanations of what GraphQL is or how APIs work. The diagnostic script and deprecated fields table are dense with useful information. | 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 sequential steps are less critical. However, the diagnostic script serves as a workflow and lacks explicit validation checkpoints or feedback loops (e.g., 'if this returns X, then do Y'). The error resolution steps are clear individually but don't guide through a diagnose-fix-verify cycle. | 2 / 3 |
Progressive Disclosure | The content references external skills ('fireflies-rate-limits' skill, 'fireflies-debug-bundle') and external docs, which is good. However, the inline content is fairly long and the deprecated fields table, network errors table, and diagnostic script could potentially be split out. No bundle files exist to support the references made, and the 'fireflies-rate-limits' skill reference is unverifiable. | 2 / 3 |
Total | 10 / 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
a04d1a2
- 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.