CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with complete executable scripts, but the inline bundle script and redundant summary tables add token weight, and the diagnostic workflow omits validation checkpoints that would catch a failed curl or missing API key before packaging.

Suggestions

Add a validation checkpoint in Step 1 before tarring the bundle - e.g. check that $FIREFLIES_API_KEY is set and that the API connectivity curl returned a 2xx, and abort with a clear message if not.

Tighten token usage by moving the full bundle script into a referenced scripts/ file (e.g. scripts/collect-bundle.sh) and keeping only the invocation in SKILL.md, which would also strengthen progressive disclosure with real bundle files.

Drop or merge the 'Error Handling' table since it restates content already captured by the script and the 'Sensitive Data Handling' section.

DimensionReasoningScore

Conciseness

The body is mostly efficient but carries some bulk that could be tightened - the full inline bash script in Step 1 plus a partly redundant 'Error Handling' table that restates what the script already does, and the 'Current State' node/python version probe adds little.

2 / 3

Actionability

Step 1 and Step 2 provide fully executable, copy-paste-ready bash with concrete curl/jq commands and a tar packaging step, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

Steps are numbered and the health check is sequenced, but the bundle-generation workflow lacks a validation checkpoint (e.g. verifying the API key is set, confirming curl succeeded, or checking the tarball before declaring success) - this is a batch/diagnostic operation where missing feedback loops cap clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist under references/scripts/assets, so this is a self-contained single-file skill with well-organized sections (Overview, Prerequisites, Instructions, Sensitive Data Handling, Output) - the simple-skill carve-out lets it score 3.

3 / 3

Total

10

/

12

Passed

Description

100%

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 strong, well-formed description: it states a concrete purpose, gives explicit 'Use when' trigger guidance, and lists natural trigger phrases scoped to a distinct Fireflies.ai niche. Voice is correctly third person.

DimensionReasoningScore

Specificity

The description names concrete actions - 'Collect Fireflies.ai debug evidence for support tickets and troubleshooting' and 'collecting diagnostic information' - rather than vague language, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

It answers both 'what' ('Collect Fireflies.ai debug evidence...') and 'when' with an explicit 'Use when...' clause plus named trigger phrases, satisfying the both what AND when anchor.

3 / 3

Trigger Term Quality

It lists natural trigger phrases a user would actually say - 'fireflies debug', 'fireflies support bundle', 'collect fireflies logs', 'fireflies diagnostic' - giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

The Fireflies.ai-specific scope and branded trigger phrases carve a clear niche that is unlikely to conflict with other skills.

3 / 3

Total

12

/

12

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.