fireflies-debug-bundle
Collect Fireflies.ai debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Fireflies.ai problems. Trigger with phrases like "fireflies debug", "fireflies support bundle", "collect fireflies logs", "fireflies diagnostic".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/fireflies-pack/skills/fireflies-debug-bundle/SKILL.mdQuality
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 solid skill description with excellent trigger terms and completeness. It clearly identifies both when and what, and is highly distinctive due to the specific product focus. The main weakness is that the specific capabilities could be more concrete — listing exactly what debug evidence is collected (e.g., logs, API responses, configuration snapshots) would strengthen specificity.
Suggestions
Add more concrete actions to improve specificity, e.g., 'Captures browser console logs, API error responses, extension version info, and meeting sync status for Fireflies.ai troubleshooting.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Fireflies.ai debug evidence) and some actions (collect debug evidence, prepare support tickets, collect diagnostic information), but doesn't list multiple specific concrete actions like 'capture logs, export meeting transcripts, gather API error traces'. | 2 / 3 |
Completeness | Clearly answers both 'what' (collect Fireflies.ai debug evidence for support tickets and troubleshooting) and 'when' (encountering persistent issues, preparing support tickets, collecting diagnostic information) with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases: 'fireflies debug', 'fireflies support bundle', 'collect fireflies logs', 'fireflies diagnostic'. These are specific, natural terms a user would say, with good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific product (Fireflies.ai) and a specific task (debug evidence collection). The trigger terms are unique and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable bash scripts for collecting Fireflies.ai debug information, with good attention to security (redaction guidelines). However, it's somewhat verbose with redundant information collection (Current State section duplicates script content, error handling table restates what the script does), and lacks explicit validation/decision points in the workflow for when specific diagnostic checks fail.
Suggestions
Remove the `## Current State` dynamic commands at the top since the debug bundle script already collects the same environment info, reducing redundancy.
Add decision-point guidance after the health check (e.g., 'If auth returns 401: verify API key format and permissions. If calendar sync is false: check calendar integration settings at...').
Consider moving the full debug bundle script to a separate file (e.g., `fireflies-debug-bundle.sh`) and keeping only the quick health check inline, with a reference to the full script.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The script is fairly long and repetitive with many similar curl commands. The `## Current State` dynamic commands at the top are redundant since the debug bundle script itself collects the same info. The error handling table partially duplicates what's already evident from the script. However, it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | Fully executable bash scripts with specific curl commands, GraphQL queries, jq processing, and tar packaging. Both the full debug bundle and quick health check are copy-paste ready with proper error handling (set -euo pipefail, 2>/dev/null fallbacks). | 3 / 3 |
Workflow Clarity | The two steps (create bundle script, quick health check) are clearly presented, but there's no validation checkpoint between them or guidance on what to do if specific checks fail. For a diagnostic/debugging workflow, there should be explicit decision points like 'if auth fails, check X before proceeding' rather than just collecting everything blindly. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the main debug bundle script is quite long inline (~60 lines of bash). The sensitive data handling and error handling sections are well-organized. The reference to `fireflies-rate-limits` is a good one-level-deep pointer, but the bulk of the content could benefit from better splitting. | 2 / 3 |
Total | 9 / 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
70e9fa4
- 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.