Name: fireflies
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

fireflies

Fireflies integration. Manage Organizations. Use when the user wants to interact with Fireflies data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/fireflies/SKILL.md

Quality

Content

68%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 highly actionable with copy-paste-ready Membrane commands and a well-structured connection workflow, but it lacks validation safeguards for destructive operations and has a couple of small organization rough edges.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g. delete-transcript, proxy DELETE) so workflow_clarity can exceed the cap of 3.

Fix the dangling "skip to Step 2" reference by labeling the next section as Step 2 or rewording to "skip to Searching for actions".

Fill the empty Description column in the Popular actions table so actionability is unambiguous without a separate action-list call.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, copy-paste-ready commands and tables. There is one conceptual intro paragraph ("AI-powered meeting recording and transcription tool... improve collaboration and knowledge sharing") and minor fluff ("focus on the integration logic rather than auth plumbing"), but these are minor relative to the whole, matching anchor 4 rather than 3.	4 / 5
Actionability	Concrete executable commands cover the full workflow (install, login, connection ensure, poll, action list/run, request proxy) with clearly marked placeholders. Minor gaps prevent a 5: the Popular actions table has empty description cells and placeholders like <agentType> need user-supplied values.	4 / 5
Workflow Clarity	The connection sub-flow is well sequenced with poll-until-READY feedback loops, but the skill exposes destructive and batch operations (delete-transcript, proxy DELETE) with no validation/verification step, which caps workflow_clarity at 3 per the rubric. A dangling "skip to Step 2" reference with no labeled Step 2 reinforces the cap.	3 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized sections and no nested references (only an external docs link), which is appropriate given the empty bundle. Minor organization gaps (the dangling Step 2 reference and the empty action-description table) keep it at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Description

62%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 correctly includes an explicit Use-when trigger and names a distinct product, but it is thin on concrete actions and misses the natural meeting/transcript terms users would actually say.

Suggestions

Replace the vague "Fireflies integration" with concrete actions, e.g. "Search and manage Fireflies meetings, transcripts, and soundbites".

Add natural trigger terms users say: "Use when the user wants to find, transcribe, or search Fireflies meetings, transcripts, or recordings."

"Manage Organizations" is narrow and mismatches the skill's scope; broaden it to reflect meetings/transcripts/workspaces/users.

Dimension	Reasoning	Score
Specificity	"Manage Organizations" names one concrete action, but "interact with Fireflies data" is generic and the description does not enumerate the skill's actual scope (meetings, transcripts, workspaces, users). It sits between anchor 2 (minimal actions) and 3 (1-2 concrete actions), landing at 3 because one concrete action is present.	3 / 5
Completeness	Both halves are present: a partial "what" ("Manage Organizations") and an explicit "when" ("Use when the user wants to interact with Fireflies data"). The Use-when clause is explicit so it is not capped at 3, but the "what" is vague so it does not reach 5.	4 / 5
Trigger Term Quality	"Fireflies" is a relevant brand keyword, but the description omits the natural phrases users actually say (meetings, transcripts, recordings, meeting notes). Not a 2 because a relevant keyword is present; not a 4 because common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product (Fireflies) gives it a clear niche with low conflict risk, but the trigger ("interact with Fireflies data") is generic rather than concrete, so it does not fully match anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/fireflies/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.