Search across Fireflies.ai transcripts, use AskFred AI, and build meeting analytics. Use when searching meeting history, querying Fred AI assistant, or aggregating meeting data for reports. Trigger with phrases like "fireflies search", "ask fred", "fireflies analytics", "search meetings", "fireflies AskFred".
67
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 strong skill description that clearly identifies the specific product (Fireflies.ai), lists concrete capabilities, and provides both 'Use when' guidance and explicit trigger phrases. It uses proper third-person voice throughout and is concise without being vague. The product-specific terminology makes it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists three specific concrete actions: searching transcripts, using AskFred AI, and building meeting analytics. These are distinct, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (search transcripts, use AskFred AI, build meeting analytics) and 'when' (explicit 'Use when' clause plus a 'Trigger with phrases like' section providing concrete trigger terms). | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms: 'fireflies search', 'ask fred', 'fireflies analytics', 'search meetings', 'fireflies AskFred', plus contextual terms like 'meeting history', 'Fred AI assistant', and 'meeting data for reports'. Good coverage of how users would naturally phrase requests. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Fireflies.ai' and 'AskFred'/'Fred AI' references. Very unlikely to conflict with other skills since it targets a specific third-party service. | 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 strong actionability with complete, executable TypeScript/GraphQL examples covering search, AskFred AI, and analytics workflows. Its main weaknesses are the lack of validation checkpoints between steps (e.g., checking credits before AskFred calls, verifying search results) and some verbosity in the analytics section that could be trimmed or extracted. The error handling table is a useful addition but doesn't compensate for missing inline validation steps.
Suggestions
Add validation checkpoints: check AI credit availability before AskFred calls, verify search returns results before proceeding to thread creation, and add a feedback loop for empty results.
Extract the lengthy meetingAnalytics function into a separate reference file and keep only a concise usage example inline in SKILL.md.
Trim console.log statements and obvious inline comments to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary verbosity like console.log statements, inline comments explaining obvious things, and the analytics function is quite long when a more concise pattern could suffice. The overview and prerequisites sections add modest value. | 2 / 3 |
Actionability | Every step provides fully executable TypeScript code with complete GraphQL queries, variable definitions, and usage examples. The code is copy-paste ready with concrete examples like searching for 'quarterly review' in the last 30 days. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logically ordered (search → single meeting Q&A → continue thread → cross-meeting → analytics → manage threads). However, there are no validation checkpoints or feedback loops — no guidance on verifying search results before passing to AskFred, no error recovery steps between operations, and no verification that credits are available before making AskFred calls. | 2 / 3 |
Progressive Disclosure | References to external resources (fireflies-install-auth, fireflies-core-workflow-a, fireflies-rate-limits, fireflies-common-errors, external docs) are present and one-level deep. However, the analytics aggregation function (Step 5) is quite lengthy and could be split into a separate reference file, and there are no bundle files to support the references made. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%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 | |
a04d1a2
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.