fireflies-core-workflow-a
Execute Fireflies.ai primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "fireflies main workflow", "primary task with fireflies".
Overall
score
38%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill fireflies-core-workflow-aActivation
0%This description fails on all dimensions by using placeholder-style language that provides no actual information about what the skill does. It appears to be a template that was never filled in with real content. The circular, self-referential triggers and complete absence of concrete actions make it impossible for Claude to know when to select this skill.
Suggestions
Replace 'Core Workflow A' and 'primary use case' with specific actions Fireflies.ai performs (e.g., 'Transcribe meeting recordings, extract action items, generate meeting summaries')
Add natural trigger terms users would actually say, such as 'meeting transcription', 'meeting notes', 'record call', 'Fireflies', 'meeting summary', or 'action items'
Rewrite the 'Use when' clause with concrete scenarios like 'Use when the user wants to transcribe meetings, extract highlights from calls, or integrate meeting notes with other tools'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'primary workflow', 'Core Workflow A', 'primary use case', and 'main features' without describing any concrete actions. No actual capabilities are specified. | 1 / 3 |
Completeness | While it attempts to answer both 'what' and 'when', both are extremely weak. 'Core Workflow A' tells nothing about what the skill does, and the triggers are circular references to the vague description itself. | 1 / 3 |
Trigger Term Quality | The trigger phrases 'fireflies main workflow' and 'primary task with fireflies' are artificial and unlikely to be naturally spoken by users. Real users would say things like 'transcribe meeting', 'meeting notes', or 'record call'. | 1 / 3 |
Distinctiveness Conflict Risk | Terms like 'primary workflow', 'main features', and 'core integration' are completely generic and could apply to virtually any skill. Nothing distinguishes this as specifically for Fireflies.ai functionality. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
42%This skill is a template/skeleton with no actual content - all code blocks and error handling contain placeholders. While the structure and organization are reasonable, the complete absence of executable code, concrete examples, or specific instructions makes this skill unusable in its current form.
Suggestions
Replace all placeholder code comments with actual executable TypeScript code showing the Fireflies.ai API calls
Fill in the error handling table with real errors, causes, and solutions specific to Fireflies.ai
Add a validation step after the Execute phase to verify the API response before proceeding to Finalize
Remove the prerequisites bullet about 'Understanding of Fireflies.ai core concepts' - this is vague and assumes Claude needs to be told to understand things
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonable but contains placeholder content that adds no value. The prerequisites section explains things Claude would know, and the template-style comments waste tokens without providing actual guidance. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code. The error handling table has placeholder values. This provides zero concrete, actionable guidance. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Initialize, Execute, Finalize), but there are no validation checkpoints, no feedback loops for error recovery, and the actual content of each step is missing entirely. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, external resource links, and a reference to related workflow. The organization is appropriate with overview, instructions, examples, and next steps clearly separated. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
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.