Fireflies Transcript Export

VerifiedCaution

Exports Fireflies transcripts to Markdown or JSON formats via a command line tool. Use this skill when you need to save a meeting transcript to a file for documentation, further processing, or sharing. Supports options to exclude summaries or timestamps, and can output to stdout or a specified file path.

Sby Skills Guide Bot
Data & AIBeginner
6/2/2026
Claude Code
#fireflies#transcripts#export#markdown#json

Recommended for

Automated summary

Exports Fireflies transcripts to Markdown or JSON formats.

Strengths

  • Supports both Markdown and JSON output formats
  • Options to exclude summary or timestamps
  • Can output to a file or stdout

Limitations

  • Requires a valid Fireflies API key
  • Only exports a single transcript at a time
  • No advanced Markdown formatting
When to use it

When you need to save or share Fireflies meeting transcripts as readable or structured files.

When not to use it

If you need batch processing of multiple transcripts or want direct integration without an intermediate file.

Security analysis

Caution
Quality score80/100

The skill relies on an external npm package and allows arbitrary arguments to be passed, which could lead to command injection if an attacker controls the input. While not overtly destructive, the combination of third-party code execution and file writing poses a moderate risk.

Findings
  • •Executes a third-party npm package (fireflies-api) which could contain malicious code or vulnerabilities.
  • •Potential shell injection risk if user-supplied arguments are not properly sanitized before being appended to the npm exec command.
How this analysis is made

Examples

Export transcript to Markdown file
Export the Fireflies transcript with ID 'transcript_123' to a Markdown file named meeting-notes.md.
Export transcript to JSON
Export the Fireflies transcript with ID 'transcript_456' to JSON format and save it as transcript.json.
Export transcript without summary
Export the Fireflies transcript 'transcript_789' to a file notes.md, excluding the summary.

name: ff-export description: Export transcripts to Markdown or JSON formats. Use when saving transcripts to files for documentation or processing. allowed-tools: Bash(npm exec --yes --package=fireflies-api -- fireflies-api export *)

Fireflies Export

Export transcripts to various formats (Markdown, JSON).

Command

npm exec --yes --package=fireflies-api -- fireflies-api export <id> [file] [options]

Options

  • --no-summary - Exclude summary from export
  • --no-timestamps - Exclude timestamps
  • --format <format> - Export format (md, json)

Arguments

  • <id> - Transcript ID (required)
  • [file] - Output file path (optional, defaults to stdout)

Examples

# Export to stdout
npm exec --yes --package=fireflies-api -- fireflies-api export "transcript_123"

# Export to markdown file
npm exec --yes --package=fireflies-api -- fireflies-api export "transcript_123" meeting-notes.md

# Export to JSON
npm exec --yes --package=fireflies-api -- fireflies-api export "transcript_123" meeting.json --format json

# Export without summary
npm exec --yes --package=fireflies-api -- fireflies-api export "transcript_123" notes.md --no-summary

# Export without timestamps
npm exec --yes --package=fireflies-api -- fireflies-api export "transcript_123" notes.md --no-timestamps

Instructions

  1. Verify API key is set:

    test -n "$FIREFLIES_API_KEY" && echo "Ready" || echo "ERROR: Set FIREFLIES_API_KEY"
    
  2. Ask user for preferred format if not specified.

  3. For file output, confirm the destination path with the user.

  4. Markdown format is human-readable; JSON is for programmatic use.

Usage Tips

Format Selection:

  • Use Markdown (.md) for human-readable documentation (default)
  • Use JSON only when user needs structured data for processing
  • When exporting to stdout, Markdown is easier to read in the terminal

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/fireflies-transcript-export-mm5t8bsd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/fireflies-transcript-export-mm5t8bsd/download' --output '.skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md.part' && mv '.skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md.part' '.skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(npm exec --yes --package=fireflies-api -- fireflies-api export *)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md' && test -s '.skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/ff-export' && cp -R '.skill-downloads/fireflies-transcript-export-mm5t8bsd' '.claude/skills/ff-export'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/fireflies-transcript-export-mm5t8bsd'

openskills read 'fireflies-transcript-export-mm5t8bsd'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/fireflies-transcript-export-mm5t8bsd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills