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
Pending
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 strong completeness and distinctiveness. It clearly identifies its niche (Fireflies.ai CI/CD with GraphQL testing) and provides explicit trigger phrases. The main weakness is that the specific capabilities could be more concrete—listing particular actions like 'generate workflow YAML files' or 'configure test stages' would strengthen specificity.
Suggestions
Add more concrete actions beyond 'configure'—e.g., 'generates GitHub Actions workflow files, sets up GraphQL query validation steps, configures test reporting for Fireflies.ai API calls'.
| 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 provided. | 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'. These are phrases a user would plausibly say, and the explicit trigger list covers common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Fireflies.ai, GraphQL testing, and CI/CD pipelines. Very unlikely to conflict with other skills given the narrow domain focus and specific trigger terms. | 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 complete, executable code for every step of setting up CI/CD for Fireflies.ai integrations. The workflow is well-sequenced with appropriate gating and conditional execution. The main weakness is length — the three full test examples inline make the skill quite long, and some sections (Output, Resources) add little value for Claude.
Suggestions
Remove the 'Output' section as it merely restates what the steps produce, and trim the 'Resources' section since Claude already knows these docs.
Consider reducing the unit test examples to one representative test case inline, with a reference to a separate file for the full test suite.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code, but includes some unnecessary sections like the 'Output' bullet list (which just restates what the steps already produce) and the 'Resources' links to docs Claude already knows about. The unit test examples are thorough but could be trimmed to one representative test case. | 2 / 3 |
Actionability | Fully executable code throughout: complete GitHub Actions YAML, copy-paste ready bash commands for secrets, complete Vitest test files with mocks, integration tests, and package.json scripts. Every step is concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with logical progression (workflow → secrets → unit tests → integration tests → scripts). Integration tests are gated behind unit tests via `needs: unit-tests`, and live API tests are conditionally skipped with `describe.skipIf(!hasApiKey)`. The error handling table provides a feedback loop for common CI failures. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the skill is quite long (~180 lines of content) with extensive inline code that could benefit from being split into referenced files (e.g., the full test files could be in separate examples). The reference to `fireflies-local-dev-loop` and `fireflies-deploy-integration` shows awareness of cross-referencing but the main body is monolithic. | 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
c8a915c
- 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.