Create a minimal working Fireflies.ai example. Use when starting a new Fireflies.ai integration, testing your setup, or learning basic Fireflies.ai API patterns. Trigger with phrases like "fireflies hello world", "fireflies example", "fireflies quick start", "simple fireflies code".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill fireflies-hello-world71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 excellent trigger terms and clear when/what guidance. The main weakness is the lack of specific concrete actions - it describes the purpose (create an example) but not what that example actually does (e.g., authenticate, fetch transcripts, list meetings).
Suggestions
Add 1-2 specific actions the example demonstrates, e.g., 'Create a minimal working Fireflies.ai example that authenticates and fetches recent transcripts.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Fireflies.ai) and mentions 'minimal working example' and 'API patterns', but doesn't list specific concrete actions like 'authenticate', 'fetch transcripts', or 'create meeting notes'. | 2 / 3 |
Completeness | Clearly answers both what ('Create a minimal working Fireflies.ai example') and when ('Use when starting a new Fireflies.ai integration, testing your setup, or learning basic Fireflies.ai API patterns') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'fireflies hello world', 'fireflies example', 'fireflies quick start', 'simple fireflies code'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Fireflies.ai hello world/quickstart scenarios. The explicit product name and 'hello world'/'quick start' framing make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structure and organization but fails at its core purpose: providing a working hello world example. The code snippets are incomplete templates rather than executable examples, which defeats the purpose of a 'minimal working example.' The duplication between steps and examples sections wastes tokens without adding value.
Suggestions
Replace placeholder comments with actual API calls (e.g., fetching user info or listing transcripts) that demonstrate a complete, working example
Remove the duplicate TypeScript code - either consolidate into the Examples section or keep only in the Steps section
Add a verification step after the API call to confirm success (e.g., 'If you see your user ID printed, the setup is complete')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some redundancy - the TypeScript example is duplicated in both Step 2/3 and the Examples section. The step-by-step breakdown adds overhead for what could be a single code block. | 2 / 3 |
Actionability | The code examples are incomplete placeholders with '// Your first API call here' comments instead of actual executable API calls. A 'hello world' should demonstrate a real working call, not a template. | 1 / 3 |
Workflow Clarity | Steps are listed sequentially but lack validation checkpoints. No guidance on how to verify the setup worked beyond expecting console output. The error handling table is helpful but disconnected from the workflow. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate use of external resource links, and a clear pointer to the next skill. Content is well-organized for a simple hello world skill. | 3 / 3 |
Total | 8 / 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 | |
Table of Contents
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.