fireflies-sdk-patterns
Apply production-ready Fireflies.ai GraphQL client patterns for TypeScript and Python. Use when implementing Fireflies.ai integrations, building typed clients, or establishing team coding standards for the GraphQL API. Trigger with phrases like "fireflies SDK patterns", "fireflies best practices", "fireflies client", "fireflies GraphQL wrapper", "typed fireflies".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/fireflies-pack/skills/fireflies-sdk-patterns/SKILL.mdQuality
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 skill description with explicit 'Use when' and 'Trigger with' clauses, strong distinctiveness due to the specific product focus (Fireflies.ai), and good trigger term coverage. Its main weakness is that the described capabilities are somewhat abstract ('apply patterns', 'establishing standards') rather than listing concrete actions the skill performs.
Suggestions
Replace abstract phrases like 'apply production-ready patterns' and 'establishing team coding standards' with concrete actions such as 'generate typed GraphQL queries, configure authentication, handle pagination, and structure error handling for Fireflies.ai API calls'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Fireflies.ai GraphQL client) and some actions ('apply patterns', 'implementing integrations', 'building typed clients', 'establishing team coding standards'), but the actions are somewhat abstract—'apply patterns' and 'establishing standards' are not concrete operations like 'extract text' or 'fill forms'. | 2 / 3 |
Completeness | Clearly answers both 'what' (apply production-ready Fireflies.ai GraphQL client patterns for TypeScript and Python) and 'when' (explicit 'Use when' clause with trigger scenarios and a 'Trigger with phrases like' section). | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms: 'fireflies SDK patterns', 'fireflies best practices', 'fireflies client', 'fireflies GraphQL wrapper', 'typed fireflies', plus mentions TypeScript, Python, and GraphQL API. These cover variations a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—Fireflies.ai is a specific product, and the combination of GraphQL client patterns, TypeScript/Python, and the named trigger phrases make it 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 skill provides highly actionable, executable code patterns for both TypeScript and Python Fireflies.ai clients. Its main weaknesses are the monolithic structure (all patterns inline rather than progressively disclosed), some redundancy between the TypeScript and Python sections, and the lack of validation checkpoints or testing guidance in the workflow. The error handling table and 'Output' section add little value and could be removed.
Suggestions
Add a validation/testing step after the client creation (e.g., 'Step 2: Verify connectivity by calling getUser() and confirming a successful response before proceeding').
Move advanced patterns (multi-tenant factory, Zod validation) to a separate referenced file to reduce the main skill's length and improve progressive disclosure.
Remove the 'Output' section which merely restates what was already demonstrated, and condense the error handling table into the relevant code sections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code, but includes some unnecessary elements like the 'Output' section that just restates what was already shown, and the error handling table that adds little value. The Python client largely duplicates the TypeScript client's logic, which could be tightened. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. The TypeScript client, Zod validation, singleton pattern, multi-tenant factory, and Python client are all concrete and complete with specific GraphQL queries and proper type definitions. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically (build client → singleton → multi-tenant → validation → Python equivalent), but there are no validation checkpoints or feedback loops. For an API integration skill involving runtime errors and schema drift, there's no guidance on testing the client, verifying API connectivity, or handling common failure modes beyond basic error throwing. | 2 / 3 |
Progressive Disclosure | The content is somewhat monolithic — all patterns are inline in a single long file rather than splitting advanced patterns (multi-tenant, Zod validation) into separate references. The 'Next Steps' reference to 'fireflies-core-workflow-a' is good but the main body could benefit from better separation of basic vs. advanced content. | 2 / 3 |
Total | 9 / 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
3e83543
- 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.