fireflies-upgrade-migration
Handle Fireflies.ai API deprecations and migrate to current query patterns. Use when updating deprecated fields, migrating query patterns, or responding to Fireflies API changelog updates. Trigger with phrases like "upgrade fireflies", "fireflies deprecated", "fireflies migration", "fireflies breaking changes", "fireflies changelog".
68
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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-structured description with strong completeness and distinctiveness, clearly targeting a narrow niche (Fireflies.ai API migration). Its main weakness is that the specific capabilities could be more concrete — listing particular deprecated fields, query patterns, or migration actions would strengthen it. The explicit trigger phrases are a notable strength.
Suggestions
Add more specific concrete actions, e.g., 'Replace deprecated transcript fields like `speaker_name` with `speaker_id`, update `transcripts` query to use pagination parameters, migrate from v1 to v2 query patterns.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Fireflies.ai API) and some actions ('handle deprecations', 'migrate to current query patterns'), but doesn't list multiple specific concrete actions like which fields, which queries, or what specific migration steps are performed. | 2 / 3 |
Completeness | Clearly answers both 'what' (handle API deprecations, migrate query patterns) and 'when' (updating deprecated fields, responding to changelog updates) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit natural trigger phrases like 'upgrade fireflies', 'fireflies deprecated', 'fireflies migration', 'fireflies breaking changes', 'fireflies changelog' — these are terms users would naturally say when encountering this problem. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche — Fireflies.ai API deprecation handling is unlikely to conflict with any other skill. The trigger terms are highly distinctive and product-specific. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable migration skill with clear deprecated-to-current patterns and a well-sequenced workflow. Its main strengths are the concrete, executable code examples at every step and the inclusion of schema introspection as a validation mechanism. Minor weaknesses include some inline content that could be split into supporting files and slight verbosity in areas Claude could infer.
Suggestions
Consider extracting the migration helper (Step 2) and test file (Step 4) into bundle files referenced from SKILL.md to improve progressive disclosure.
Remove the 'Output' section as it merely restates what the steps already accomplish, saving tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete code examples, but includes some unnecessary elements like the migration helper file that explains what Claude could infer, and the Output section restates what the steps already cover. The error handling table is useful but some entries are somewhat obvious. | 2 / 3 |
Actionability | Fully executable code throughout: bash scanning commands, TypeScript migration helpers, curl introspection commands, and vitest test cases are all copy-paste ready with specific deprecated/current patterns clearly shown. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow: scan → update → introspect → test → monitor. Step 3 (introspect) serves as a validation checkpoint to discover actual schema state, and Step 4 provides explicit test verification before considering migration complete. The feedback loop of scan-then-verify is well-structured. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and headers, but everything is inline in a single file (~130 lines). The migration helper code and test code could be split into referenced files. The 'Next Steps' reference to 'fireflies-ci-integration' is good but no bundle files exist to support it. | 2 / 3 |
Total | 10 / 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 | |
- Commit
a04d1a2
- 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.