fireflies-data-handling

Handle Fireflies.ai transcript data: export formats, PII redaction, retention policies, and compliance. Use when exporting transcripts, implementing data redaction, configuring retention, or ensuring GDPR/CCPA compliance. Trigger with phrases like "fireflies data", "fireflies PII", "fireflies GDPR", "fireflies data retention", "fireflies privacy", "fireflies export".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The skill delivers dense, executable guidance with lean prose and clear sequencing, but its destructive batch operations lack validation feedback loops and several referenced helper functions are undefined. Progressive disclosure is limited because everything is inline with no bundle files.

Suggestions

Define or stub getTranscriptList and archiveToSummaryOnly (referenced in Step 4) so the retention workflow is fully executable end-to-end.

Add validation checkpoints to the destructive retention and GDPR-deletion steps — e.g. a dry-run summary of affected transcripts and explicit confirmation before issuing deleteTranscript calls.

Move the long per-step code implementations into reference files under references/ and keep SKILL.md as an overview with one-level-deep links to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable TypeScript with minimal prose and no explanations of concepts Claude already knows (no "what is a transcript" padding); every section earns its place. It is not below 3 because there is no wasted explanation, though the code volume is large.	3 / 3
Actionability	Most steps give concrete, executable TypeScript, but Step 4 calls undefined helpers getTranscriptList(200) and archiveToSummaryOnly(t.id) that are never shown, leaving the end-to-end flow incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced with an error-handling table, but the destructive/batch retention deletion loop (Step 4) and GDPR deletion (Step 5) lack validation checkpoints or dry-run confirmation, which caps workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	The file is organized into labeled sections and links external docs under Resources, but ~280 lines of full code implementations live inline with no bundle files to offload them to, so content that could be split into references is kept in SKILL.md.	2 / 3
	Total	9 / 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.

The description is concise, third-person, and answers both what the skill does and when to use it, with strong natural trigger phrases and a distinctive Fireflies.ai niche. It is among the strongest examples in the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "export formats, PII redaction, retention policies, and compliance" — each tied to the Fireflies.ai transcript domain, matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers what (export, redaction, retention, compliance) and when ("Use when exporting transcripts, implementing data redaction, configuring retention, or ensuring GDPR/CCPA compliance"), with an added explicit trigger-phrase clause.	3 / 3
Trigger Term Quality	Provides natural phrases a user would say ("fireflies data", "fireflies PII", "fireflies GDPR", "fireflies data retention", "fireflies privacy", "fireflies export") plus plain-language variants like "exporting transcripts" and "GDPR/CCPA compliance".	3 / 3
Distinctiveness Conflict Risk	The "fireflies"-prefixed triggers carve out a clear niche (Fireflies.ai transcript data handling) that is unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 1628598

Reviewed: about 12 hours 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.