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".
85
83%
Does it follow best practices?
Impact
Pending
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 solid, well-structured description for a niche skill. It clearly identifies the domain (Fireflies.ai API), the purpose (handling deprecations and migrations), and provides explicit trigger phrases. The main weakness is that the specific actions could be more concrete — listing particular deprecated fields or migration patterns would strengthen specificity.
Suggestions
Add more concrete action examples such as 'replace deprecated transcript fields, update pagination parameters, migrate from v1 to v2 query syntax' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Fireflies.ai API deprecations) and some actions (handle deprecations, migrate query patterns), but doesn't list specific concrete actions like 'update field X', 'replace deprecated Y with Z', or detail what migration steps are involved. | 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 listed. | 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 strong, highly actionable skill with clear before/after migration patterns and a well-sequenced workflow. Its main weakness is that it's somewhat long for a SKILL.md — the detailed code examples are valuable but could be organized with better progressive disclosure. The concrete grep commands, schema introspection, and test examples make this immediately useful.
Suggestions
Consider moving the detailed deprecation examples and migration helper code into a referenced file (e.g., FIREFLIES-DEPRECATIONS.md) to keep SKILL.md as a concise overview
Remove the 'Output' section as it merely restates what the steps already accomplish, saving tokens without losing clarity
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with concrete code examples, but includes some unnecessary elements like the migration helper file (which is more of a nice-to-have than essential) and the Output section which just restates what the steps already cover. The error handling table is useful but could be tighter. | 2 / 3 |
Actionability | Excellent actionability throughout — every deprecation has concrete before/after code examples, the scan step has executable bash commands, the migration helper is copy-paste ready TypeScript, and the test step includes runnable vitest tests. Schema introspection commands are fully executable with curl/jq. | 3 / 3 |
Workflow Clarity | Clear 5-step sequential workflow: scan → update → introspect → test → monitor. The scan step serves as validation/discovery, the test step provides verification, and the introspection step acts as a feedback mechanism to discover additional changes. The workflow handles the migration lifecycle well with explicit checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and a logical flow, but it's fairly long and monolithic. The deprecation examples, migration helper, and test code could potentially be split into referenced files. The 'Next Steps' reference to fireflies-ci-integration is a good touch but the main content could benefit from more splitting. | 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
70e9fa4
- 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.