From fireflies-pack
Optimize Fireflies.ai costs through tier selection, sampling, and usage monitoring. Use when analyzing Fireflies.ai billing, reducing API costs, or implementing usage monitoring and budget alerts. Trigger with phrases like "fireflies cost", "fireflies billing", "reduce fireflies costs", "fireflies pricing", "fireflies expensive", "fireflies budget".
How this skill is triggered — by the user, by Claude, or both
Slash command
/fireflies-pack:fireflies-cost-tuningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Optimize Fireflies.ai per-seat subscription costs by right-sizing seat count, configuring selective recording, and managing transcript storage. Fireflies charges per seat per month (Pro: ~$18/seat/month, Business: ~$29/seat/month, Enterprise: custom).
Optimize Fireflies.ai per-seat subscription costs by right-sizing seat count, configuring selective recording, and managing transcript storage. Fireflies charges per seat per month (Pro: ~$18/seat/month, Business: ~$29/seat/month, Enterprise: custom).
set -euo pipefail
# Identify members who aren't using their seats
curl -X POST https://api.fireflies.ai/graphql \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-d '{"query": "{ teamMembers { email role transcripts_count last_active } }"}' | \
jq '.data.teamMembers | sort_by(.transcripts_count) | .[] | {email, transcripts: .transcripts_count, last_active}'
# Members with 0-1 transcripts per month are wasting seats
# Seat optimization strategy
current_state:
total_seats: 20
active_users: 12 # >2 recordings/month
low_usage: 5 # 1-2 recordings/month
inactive: 3 # 0 recordings/month
optimized_state:
total_seats: 14 # Keep active + low_usage, remove inactive
savings: 6 seats * $29/month = $174/month
Remove inactive members or downgrade them to Viewer roles (which don't consume seats on most plans).
# Instead of recording every meeting (wastes transcription credits):
auto_record_policy:
record:
- internal meetings with 3+ participants
- external meetings (client/prospect calls)
- meetings with "standup" or "review" in title
skip:
- 1-on-1 informal chats
- social/team-building events
- meetings shorter than 5 minutes
Configure in Fireflies Settings > Auto-Join > Selective Recording.
set -euo pipefail
# Check storage usage
curl -X POST https://api.fireflies.ai/graphql \
-H "Authorization: Bearer $FIREFLIES_API_KEY" \
-d '{"query": "{ workspace { storage_used_gb storage_limit_gb } }"}' | \
jq '.data.workspace | {used_gb, limit_gb, usage_pct: (.storage_used_gb / .storage_limit_gb * 100)}'
# Delete old transcripts that are no longer needed
# Set auto-deletion policy: delete transcripts older than 365 days
# Decision matrix for plan selection
pro_18_per_seat:
storage: 8000 min transcription/seat # 8000: API server port
best_for: Teams that record <15 meetings/week per person
features: [transcription, search, basic AI summaries]
business_29_per_seat:
storage: Unlimited transcription
best_for: Sales teams recording every call
features: [transcription, search, AI summaries, CRM integration, analytics]
tip: Only worth it if team averages 20+ meetings/week per person
# If your team averages <10 meetings/week per person, Pro tier saves $11/seat/month
| Issue | Cause | Solution |
|---|---|---|
| Seat cost growing | Auto-provisioning new members | Disable auto-provisioning, manually add seats |
| Storage limit approaching | Recording every meeting | Enable selective recording, delete old transcripts |
| Paying for unused features | On Business tier but only using transcription | Downgrade to Pro tier |
| Invoice higher than expected | New members auto-added | Set member invitation to admin-only |
Basic usage: Apply fireflies cost tuning to a standard project setup with default configuration options.
Advanced scenario: Customize fireflies cost tuning for production environments with multiple constraints and team-specific requirements.
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin fireflies-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
4plugins reuse this skill
First indexed Jul 11, 2026