Execute Fireflies.ai secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "fireflies secondary workflow", "secondary task with fireflies".
Overall
score
28%
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-bActivation
0%This description fails on all dimensions by providing no concrete information about what the skill actually does. It relies entirely on placeholder-like language ('Core Workflow B', 'secondary use case') that gives Claude no basis for selecting this skill appropriately. The trigger phrases are artificial constructs rather than natural user language.
Suggestions
Replace 'Core Workflow B' and 'secondary use case' with specific concrete actions the skill performs (e.g., 'Exports meeting transcripts to CRM systems, generates action item summaries')
Add natural trigger terms users would actually say, such as specific Fireflies features, file types, or task descriptions (e.g., 'meeting notes', 'transcript export', 'action items')
Rewrite the 'Use when' clause to describe actual scenarios where this skill applies, not abstract references to 'secondary' or 'complementing' workflows
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses completely vague language like 'Core Workflow B' and 'secondary use case' without describing any concrete actions. There is no indication of what the skill actually does. | 1 / 3 |
Completeness | While it has a 'Use when' clause, both the 'what' and 'when' are essentially meaningless - 'secondary use case' and 'complementing primary workflow' provide no actual information about functionality or triggers. | 1 / 3 |
Trigger Term Quality | The trigger phrases 'fireflies secondary workflow' and 'secondary task with fireflies' are artificial and unlikely to be naturally spoken by users. No natural keywords describing actual functionality are present. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it provides no clear niche. Terms like 'secondary workflow' and 'complementing primary workflow' could apply to virtually anything and would conflict with any other Fireflies-related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%This skill is essentially a template with no actual content - all code blocks are empty placeholders and the instructions provide no concrete guidance. The structure suggests a well-organized skill, but without any executable code or specific instructions, it fails to teach Claude how to perform any task. The 'Error Handling' section is mislabeled and contains a workflow comparison table instead.
Suggestions
Replace all placeholder comments with actual executable TypeScript code showing real Fireflies.ai API calls and operations
Add concrete descriptions for each step explaining what the code does and why (e.g., 'Step 1: Authenticate and fetch recent transcripts')
Move the comparison table to an appropriate section or remove it, and add actual error handling code with specific error types and recovery strategies
Include at least one complete, copy-paste ready example that demonstrates the full workflow with real API endpoints and expected responses
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes placeholder comments instead of actual code, and the comparison table in 'Error Handling' section doesn't actually explain error handling - it's misplaced content that wastes tokens. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with zero executable code. Claude cannot act on these instructions as there is no concrete guidance on what to actually do. | 1 / 3 |
Workflow Clarity | Steps are labeled but completely empty of content. There are no validation checkpoints, no actual instructions for what each step does, and the 'Error Handling' section contains an irrelevant comparison table instead of error handling guidance. | 1 / 3 |
Progressive Disclosure | Structure is reasonable with clear sections and references to related skills (fireflies-install-auth, fireflies-core-workflow-a, fireflies-common-errors), but the main content is hollow, making the structure meaningless. | 2 / 3 |
Total | 6 / 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
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.