CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

74

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is lean and highly actionable with complete executable code throughout and good section organization. The main gap is workflow clarity: validation/feedback checkpoints for the integration-test path are implicit rather than explicit, and step ordering lets a user hit a missing-secret failure mid-sequence.

Suggestions

Add an explicit validation/feedback checkpoint in Step 1 or Step 5 — e.g., after storing secrets, note 'verify the secret exists with gh secret list before running integration tests' and include a retry loop for integration-test timeouts.

Reorder so secret storage (currently Step 2) is referenced before the workflow's integration job consumes it, or add a note in Step 1 that Step 2 must be completed first to avoid a missing-secret failure.

Consider extracting the two large inline test files (Steps 3 and 4, ~95 lines) into a tests/ reference bundle with short inline summaries, to keep the overview tighter and let readers drill down on demand.

DimensionReasoningScore

Conciseness

The body is dense with executable content — a full workflow, test files, secret commands, and scripts — with no padding explaining CI or GraphQL basics; nearly every token earns its place per the score-3 anchor.

3 / 3

Actionability

All code is complete and copy-paste ready: a working GitHub Actions workflow, real `gh secret set` commands, and Vitest tests with concrete assertions, matching the score-3 anchor for fully executable guidance.

3 / 3

Workflow Clarity

Five steps are clearly numbered and sequenced, but validation checkpoints are implicit — the integration job references a secret that Step 2 stores after Step 1, and the error-handling table mentions retry without an explicit validate-then-retry loop in the workflow — matching the score-2 anchor with present-but-implicit checkpoints.

2 / 3

Progressive Disclosure

Content is organized into clearly delimited sections (Overview, Prerequisites, Steps 1–5, Rate Limit, Error Handling, Output, Resources, Next Steps) with one-level-deep cross-skill references clearly signaled ('see fireflies-local-dev-loop', 'see fireflies-deploy-integration'), matching the score-3 anchor for clear overview and easy navigation.

3 / 3

Total

11

/

12

Passed

Description

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.

The description is strong: third-person voice, concrete actions, explicit 'Use when...' guidance, and distinct Fireflies-scoped trigger phrases. It fully satisfies all four dimensions with no vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names the Fireflies.ai CI/CD domain and multiple concrete actions — 'Configure CI/CD pipelines... with GraphQL testing' and 'validating Fireflies.ai queries in your build process' — matching the score-3 anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('Configure CI/CD pipelines for Fireflies.ai integrations with GraphQL testing') and when ('Use when setting up automated testing, configuring GitHub Actions, or validating...'), matching the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Provides explicit trigger phrases a user would naturally say — 'fireflies CI', 'fireflies GitHub Actions', 'fireflies automated tests', 'CI fireflies', 'test fireflies pipeline' — giving good coverage of natural variations per the score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Fireflies.ai — the term 'fireflies' appears in nearly every trigger — creating a clear niche unlikely to conflict with generic CI skills, matching the score-3 anchor.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.