Recherche Fireflies

VérifiéPrudence

Effectue une recherche en texte intégral dans les transcriptions de réunions de Fireflies. Utile pour retrouver des contenus spécifiques, des interventions d'un intervenant, des questions ou des tâches mentionnées dans l'historique des réunions.

Spar Skills Guide Bot
ProductiviteDébutant
7002/06/2026
Claude Code
#fireflies#transcripts-search#meeting-notes#full-text-search

Recommandé pour

Notre avis

Recherche en texte intégral dans les transcriptions de réunions via l'API Fireflies.

Points forts

  • Recherche rapide dans de nombreuses transcriptions en un seul appel API.
  • Filtres pertinents : questions, tâches, locuteur, période.
  • Plusieurs formats de sortie (texte brut, tableau, JSON) adaptés à différents besoins.

Limites

  • Nécessite une clé API Fireflies valide configurée en variable d'environnement.
  • Ne remplace pas l'analyse approfondie d'une transcription individuelle.
  • La recherche ne couvre que les réunions indexées dans Fireflies.
Quand l'utiliser

Quand il faut retrouver rapidement une information spécifique (décision, question, action) dans l'historique des réunions.

Quand l'éviter

Quand vous avez besoin d'explorer le contenu détaillé d'une seule réunion ou d'une analyse hors ligne.

Analyse de sécurité

Prudence
Score qualité95/100

The skill runs a known npm package (`fireflies-api`) with a fixed command (`search`) and constrained options. While the command itself is read-only and not destructive, the use of `npm exec` to pull and run a third-party package introduces a supply chain risk. The skill does not attempt to exfiltrate the API key or perform destructive actions, but the package could theoretically be malicious. Given the legitimate nature of the Fireflies API, the risk is moderate.

Points d'attention
  • Executes third-party npm package via `npm exec`, introducing supply chain risk.
  • Requires `FIREFLIES_API_KEY` environment variable, which could be misused if the package is compromised.

Exemples

Search for budget mentions
Search all transcripts for the word 'budget' and show results in a human-readable format with context.
Find questions about deadlines
Search for 'deadline' but only in questions from the last week, output as a table.
Search action items by speaker
Search for 'action item' from the last 30 days, filtered by speaker 'Alice', showing surrounding context.

name: ff-search description: Full-text search across meeting transcripts. Use when finding specific content, speakers, or questions. allowed-tools: Bash(npm exec --yes --package=fireflies-api -- fireflies-api search *)

Fireflies Search

Full-text search across meeting transcripts.

Command

npm exec --yes --package=fireflies-api -- fireflies-api search <query> [options]

Options

Date Shortcuts (prefer these over --from/--to):

  • --today - Today's transcripts
  • --yesterday - Yesterday's transcripts
  • --last-week - Last 7 days
  • --last-month - Last 30 days
  • --days <n> - Last N days

Search Filters:

  • --speaker <name> - Filter by speaker name
  • --questions - Search only questions
  • --tasks - Search only task-related content
  • --context - Include surrounding context
  • --limit <n> - Number of results
  • --from <date> - Start date (YYYY-MM-DD) - only if shortcuts don't fit
  • --to <date> - End date (YYYY-MM-DD) - only if shortcuts don't fit
  • -o, --output <format> - Output format: json, jsonl, table, tsv, plain

Examples

# Basic search
npm exec --yes --package=fireflies-api -- fireflies-api search "budget"

# Search with speaker filter
npm exec --yes --package=fireflies-api -- fireflies-api search "proposal" --speaker "John"

# Search questions from last week
npm exec --yes --package=fireflies-api -- fireflies-api search "deadline" --questions --last-week

# Search with context
npm exec --yes --package=fireflies-api -- fireflies-api search "action item" --context --limit 20

Instructions

  1. Verify API key is set:

    test -n "$FIREFLIES_API_KEY" && echo "Ready" || echo "ERROR: Set FIREFLIES_API_KEY"
    
  2. Execute the search command with the user's query and any relevant filters.

  3. Suggest appropriate filters based on the user's intent (e.g., --questions for finding Q&A).

Usage Tips

Output Format:

  • Use -o plain for human-readable output with context
  • Use -o table for compact tabular view
  • Only use -o json if user needs structured data

When to Use Search:

  • Finding specific content across many transcripts (efficient - single call)
  • Finding who said something, questions asked, or action items mentioned
  • More efficient than listing transcripts + getting each one
Skills similaires