fireflies-ci-integration
Configure CI/CD pipelines for Fireflies.ai integrations with GraphQL testing. Use when setting up automated testing, configuring GitHub Actions, or validating Fireflies.ai queries in your build process. Trigger with phrases like "fireflies CI", "fireflies GitHub Actions", "fireflies automated tests", "CI fireflies", "test fireflies pipeline".
85
83%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
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 clear 'what' and 'when' clauses and explicit trigger phrases, making it strong on completeness and distinctiveness. The main weakness is that the specific capabilities could be more concrete—listing particular actions like 'generate workflow YAML files', 'configure test stages', or 'set up query validation steps' would improve specificity. The use of second person ('your build process') is a minor style issue.
Suggestions
Add more concrete actions beyond 'configure'—e.g., 'generates GitHub Actions workflow files, sets up GraphQL query validation steps, configures test runners for Fireflies.ai API endpoints'.
Replace second person 'your build process' with third person phrasing like 'the build process' to match the expected voice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CI/CD pipelines for Fireflies.ai with GraphQL testing) and some actions (configure, set up automated testing, validate queries), but doesn't list multiple concrete actions in detail—e.g., what specific pipeline steps, what kinds of validation, what outputs. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure CI/CD pipelines for Fireflies.ai integrations with GraphQL testing) and 'when' (setting up automated testing, configuring GitHub Actions, validating Fireflies.ai queries in build process), with explicit trigger phrases. | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'fireflies CI', 'fireflies GitHub Actions', 'fireflies automated tests', 'CI fireflies', 'test fireflies pipeline', plus mentions of 'GraphQL testing', 'build process'. These are terms users would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—the combination of Fireflies.ai, GraphQL testing, and CI/CD pipelines is a very specific niche. Unlikely to conflict with generic CI/CD or generic GraphQL skills due to the Fireflies.ai specificity. | 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, highly actionable skill with complete, executable code examples and a clear multi-step workflow. Its main weakness is verbosity — the inline test examples are thorough but lengthy, and some content could be offloaded to supporting files. The workflow sequencing and error handling table are strong additions that make this practically useful.
Suggestions
Reduce the unit test examples from 3 to 1-2, or move the full test file to a bundle reference file and keep only a representative snippet inline.
Create bundle files for the referenced test code (e.g., tests/fireflies-client.test.ts) and reference them from SKILL.md to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary bulk. The unit test examples are quite lengthy with three full test cases when one or two would suffice to demonstrate the pattern. The error handling table and resources section add moderate value but could be trimmed. | 2 / 3 |
Actionability | Highly actionable with fully executable, copy-paste ready code: a complete GitHub Actions YAML workflow, bash commands for secret storage, full Vitest test files, and package.json script entries. Every step has concrete, runnable code. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical dependencies: workflow setup → secrets → unit tests → integration tests → scripts. The GitHub Actions workflow itself has built-in validation (unit tests must pass before integration tests via `needs: unit-tests`), integration tests are gated to main branch, and the error handling table provides a troubleshooting feedback loop. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but the lengthy inline test code (especially 3 full unit test cases and 2 integration tests) could be split into referenced files. References to `fireflies-local-dev-loop` and `fireflies-deploy-integration` are mentioned but no bundle files exist to support them. | 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
3a2d27d
- 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.