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

82%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Discovery

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.

This is a well-crafted skill description that clearly defines its scope around Fireflies.ai transcript data handling, with specific capabilities enumerated and explicit trigger guidance. It uses proper third-person voice, includes a 'Use when' clause with concrete scenarios, and provides branded trigger phrases that minimize conflict risk. This is an exemplary description that would enable accurate skill selection.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: export formats, PII redaction, retention policies, and compliance. Further elaborates with exporting transcripts, implementing data redaction, configuring retention, and ensuring GDPR/CCPA compliance.	3 / 3
Completeness	Clearly answers both 'what' (handle transcript data: export formats, PII redaction, retention policies, compliance) and 'when' (explicit 'Use when...' clause with specific scenarios plus a 'Trigger with phrases like...' section).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms including 'fireflies data', 'fireflies PII', 'fireflies GDPR', 'fireflies data retention', 'fireflies privacy', 'fireflies export'. These are terms users would naturally use when seeking help with Fireflies.ai data handling.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific 'Fireflies.ai' product focus combined with data governance actions (PII redaction, GDPR/CCPA). The trigger terms are all prefixed with 'fireflies', making conflicts with other skills very unlikely.	3 / 3
	Total	12 / 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 TypeScript code covering transcript export, PII redaction, retention, and GDPR compliance. Its main weaknesses are the lack of validation checkpoints for destructive operations (batch deletion without dry-run or confirmation) and the monolithic structure that could benefit from splitting detailed implementations into separate files. The content is mostly efficient but could be tightened by removing redundant sections.

Suggestions

Add a dry-run mode and explicit confirmation checkpoint before batch deletions in the retention policy (Step 4), e.g., log affected transcripts first, then require confirmation before proceeding.

Split the detailed export format implementations and PII patterns into separate reference files (e.g., EXPORT_FORMATS.md, PII_PATTERNS.md) and keep SKILL.md as a concise overview with links.

Remove the 'Output' section which merely restates what the code demonstrates, and trim the 'Prerequisites' to just the API key requirement.

Dimension	Reasoning	Score
Conciseness	The skill is fairly efficient but includes some unnecessary elements like the 'Prerequisites' section mentioning 'Understanding of transcript data structure' and the 'Output' section which just restates what the code already demonstrates. The code itself is well-structured but lengthy—some helper functions and the full export switch could be trimmed or referenced externally.	2 / 3
Actionability	All code is fully executable TypeScript with concrete GraphQL queries, complete function implementations, specific regex patterns for PII, and real API endpoints. The code is copy-paste ready with proper error handling, rate limiting, and format conversion logic.	3 / 3
Workflow Clarity	Steps are clearly sequenced (fetch → export → redact → retention → GDPR), but there are no explicit validation checkpoints between steps. The retention policy performs destructive batch deletions without a dry-run mode, confirmation step, or rollback mechanism, which should cap this at 2 per the rubric's feedback loop requirements for destructive/batch operations.	2 / 3
Progressive Disclosure	The content is mostly inline with all code in a single file, making it quite long (~200+ lines). The error handling table and resources section are well-organized, and there's a reference to 'fireflies-enterprise-rbac', but the export formats, PII patterns, and retention logic could be split into separate reference files with the SKILL.md serving as a concise overview.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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 — 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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 70e9fa4

Reviewed: 4 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.