fireflies-install-auth

Configure Fireflies.ai GraphQL API authentication and verify connectivity. Use when setting up a new Fireflies.ai integration, configuring API keys, or initializing the GraphQL client for transcript access. Trigger with phrases like "install fireflies", "setup fireflies", "fireflies auth", "configure fireflies API key".

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/saas-packs/fireflies-pack/skills/fireflies-install-auth/SKILL.md

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-crafted skill description that clearly identifies a narrow, specific use case (Fireflies.ai API setup and authentication). It excels at completeness by providing both what/when guidance and explicit trigger phrases. The only minor weakness is that the capability actions could be slightly more detailed beyond just auth/connectivity verification.

Dimension	Reasoning	Score
Specificity	Names the domain (Fireflies.ai GraphQL API) and some actions (authentication, verify connectivity, configuring API keys, initializing GraphQL client), but the actions are somewhat narrow and not comprehensively listed beyond setup/auth tasks.	2 / 3
Completeness	Clearly answers both 'what' (configure Fireflies.ai GraphQL API authentication and verify connectivity) and 'when' (setting up a new integration, configuring API keys, initializing the GraphQL client) with explicit trigger phrases.	3 / 3
Trigger Term Quality	Includes excellent natural trigger terms that users would actually say: 'install fireflies', 'setup fireflies', 'fireflies auth', 'configure fireflies API key', plus mentions of 'integration', 'API keys', and 'GraphQL client'. Good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — targets a specific product (Fireflies.ai), a specific API type (GraphQL), and a specific task (authentication/setup). Very unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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 setup skill with complete executable examples for multiple languages and a clear step-by-step flow. Its main weaknesses are verbosity from providing three redundant verification methods inline and lacking explicit validation checkpoints that tie error handling back into the workflow steps. Trimming to one primary verification method with references to alternatives would significantly improve token efficiency.

Suggestions

Reduce to one primary verification method (e.g., cURL) inline and move TypeScript/Python alternatives to a separate reference file to improve conciseness.

Add explicit validation checkpoints after Step 4, e.g., 'If you see auth_failed, return to Step 1 and regenerate your API key; if you see rate limit errors, check your plan tier in the Rate Limits table.'

Move the rate limits and error handling tables to a separate REFERENCE.md file and link to it, keeping SKILL.md focused on the setup workflow.

Dimension	Reasoning	Score
Conciseness	The skill provides useful content but is somewhat verbose — it includes three separate verification methods (TypeScript, cURL, Python) which is redundant for a setup skill. The prerequisites section explains things Claude would know (what a GraphQL client library is). The rate limits table, while useful, adds bulk for a setup/auth skill.	2 / 3
Actionability	All code examples are fully executable and copy-paste ready — the TypeScript fetch example, cURL command, and Python requests example are all complete and concrete. Environment setup commands are specific and include safety measures like .gitignore entries.	3 / 3
Workflow Clarity	Steps are clearly sequenced (get key → configure env → install client → verify), but there's no explicit validation/feedback loop — if verification fails in Step 4, there's no 'go back and check Step 2' guidance. The error handling table exists but isn't integrated into the workflow as checkpoints.	2 / 3
Progressive Disclosure	The skill has reasonable section structure and references external docs and a next-steps skill ('fireflies-hello-world'), but the inline content is heavy — three full verification code blocks could be split into a separate reference file. The rate limits and error tables could also be externalized.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3e83543

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.