Agent skill

Flare

Manage Flare error tracking and performance monitoring using the flare CLI.

MITAuto-check passed

Install Flare

skills CLI

$ npx skills add freekmurze/dotfiles --skill flare -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install freekmurze/dotfiles flare --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/config/claude/skills/flare .claude/skills/flare && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "flare" agent skill from https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare into .claude/skills/flare/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flare", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add freekmurze/dotfiles --skill flare -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install freekmurze/dotfiles flare --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/config/claude/skills/flare .agents/skills/flare && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "flare" agent skill from https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare into .agents/skills/flare/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flare", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add freekmurze/dotfiles --skill flare -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install freekmurze/dotfiles flare --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/config/claude/skills/flare .cursor/skills/flare && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "flare" agent skill from https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare into .cursor/skills/flare/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flare", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/freekmurze/dotfiles.git --path config/claude/skills/flare

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add freekmurze/dotfiles --skill flare -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install freekmurze/dotfiles flare --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/config/claude/skills/flare .gemini/skills/flare && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "flare" agent skill from https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare into .gemini/skills/flare/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flare", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install freekmurze/dotfiles flare

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add freekmurze/dotfiles --skill flare -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/config/claude/skills/flare .github/skills/flare && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "flare" agent skill from https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare into .github/skills/flare/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flare", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add freekmurze/dotfiles --skill flare -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install freekmurze/dotfiles flare --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/freekmurze/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/config/claude/skills/flare .opencode/skills/flare && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "flare" agent skill from https://github.com/freekmurze/dotfiles/tree/main/config/claude/skills/flare into .opencode/skills/flare/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "flare", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: flare
GitHub stars: 1k
Token cost: ~2.1k tokens
SKILL.md length: 379 words
Files: 3 (incl. references)
Skills in repo: 52
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage Flare error tracking and performance monitoring using the flare CLI.

The user wants to list
SKILL.md covers Prerequisites, Authentication, Quick command reference and Common workflows, plus 1 more section
Calls composer
Manage projects

What it does

Flare is an agent skill from freekmurze/dotfiles. Manage Flare error tracking and performance monitoring using the flare CLI. Use when the user wants to list, triage, resolve, snooze, or debug errors; manage projects; create projects and retrieve API keys; check error counts; investigate slow routes, queries, jobs, or commands; view aggregated performance data and traces; or interact with flareapp.io from the command line.

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/commands.md` and `references/workflows.md`).

The licence is MIT.

When your agent uses it

The user wants to list
Manage projects
Create projects and retrieve API keys
Check error counts

Example prompts

“/flare”

What it can do on your machine

Read from SKILL.md and the folder at commit 8874280. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- composer
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- flareapp.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Flare loads about 2.1k tokens when it runs, and up to ~8.4k if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 379 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~96
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~8.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from freekmurze/dotfiles at commit 8874280, republished under its MIT licence (© freekmurze). 379 words, ~2,063 tokens.

Download SKILL.mdSave it as .claude/skills/flare/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: flare
description: Manage Flare error tracking and performance monitoring using the flare CLI. Use when the user wants to list, triage, resolve, snooze, or debug errors; manage projects; create projects and retrieve API keys; check error counts; investigate slow routes, queries, jobs, or commands; view aggregated performance data and traces; or interact with flareapp.io from the command line.
license: MIT
metadata.author: spatie
metadata.version: 0.0.1

Flare CLI

The flare CLI lets you manage Flare error tracking and performance monitoring from the terminal. Every Flare API endpoint has a corresponding command.

Prerequisites

Check that the CLI is installed:

bash

flare --version

If not installed:

bash

composer global require spatie/flare-cli

Ensure Composer's global bin directory is in PATH:

bash

composer global config bin-dir --absolute

Authentication

bash

# Log in — you'll be prompted for your API token
flare login

# Log out
flare logout

Get your API token at https://flareapp.io/settings/api-tokens.

If any command returns a 401 error, the token is invalid or expired. Run flare login again.

Quick command reference

All commands output JSON. See references/commands.md for full parameter details.

User & team

bash

# Who am I?
flare get-authenticated-user

# Get team details (includes members and roles)
flare get-team --team-id=1

# Remove a user from a team
flare remove-team-user --team-id=1 --user-id=42

Projects

bash

# List all projects (paginated)
flare list-projects

# Filter by name or team
flare list-projects --filter-name="My App" --filter-team-id=1

# Include team info
flare list-projects --include=team

# Create a project
flare create-project --field name="My App" --field team_id=1 --field stage=production --field technology=Laravel

# Delete a project
flare delete-project --project-id=123

Errors

bash

# List errors for a project
flare list-project-errors --project-id=123

# Filter by status, class, file, stage, or level
flare list-project-errors --project-id=123 --filter-status=open --filter-exception-class=RuntimeException

# Sort by most recent
flare list-project-errors --project-id=123 --sort=-last_seen_at

# Get error counts for a date range
flare get-project-error-count --project-id=123 --start-date="2025-01-01 00:00:00" --end-date="2025-01-31 23:59:59"

# Get occurrence counts for a date range
flare get-project-error-occurrence-count --project-id=123 --start-date="2025-01-01 00:00:00" --end-date="2025-01-31 23:59:59"

Error actions

bash

# Resolve an error
flare resolve-error --error-id=456

# Reopen a resolved error
flare unresolve-error --error-id=456

# Snooze forever
flare snooze-error --error-id=456 --field snooze_type=snooze_forever

# Snooze until a date
flare snooze-error --error-id=456 --field snooze_type=snooze_until --field snooze_until=2025-06-01T00:00:00Z

# Snooze for N more occurrences
flare snooze-error --error-id=456 --field snooze_type=snooze_number_of_occurrences --field snooze_number_of_occurrences=50

# Unsnooze
flare unsnooze-error --error-id=456

Occurrences

bash

# List occurrences for an error (includes frames, attributes, events, solutions)
flare list-error-occurrences --error-id=456

# Sort oldest first
flare list-error-occurrences --error-id=456 --sort=received_at

# Get a single occurrence by ID
flare get-error-occurrence --occurrence-id=789

Performance monitoring

The --type parameter accepts: routes, queries, jobs, commands, external-http, views, livewire-components.

The --filter-interval parameter accepts: 1h, 3h, 6h, 24h (default), 48h, 7d, 14d.

bash

# Get a performance summary for a project (metrics + trends + top-10 slowest)
flare get-monitoring-summary --project-id=123

# List aggregated performance data for routes (paginated, sortable, filterable)
flare list-monitoring-aggregations --project-id=123 --type=routes --sort=-p95

# Filter aggregations — the operator is encoded in the parameter name (e.g. p95:>=), pass only the value
flare list-monitoring-aggregations --project-id=123 --type=queries --filter-p95=500

# Get time series data for a monitoring type
flare get-monitoring-time-series --project-id=123 --type=routes --filter-interval=7d

# Get details for a specific aggregation (e.g. a single route or query)
flare get-monitoring-aggregation --type=routes --uuid=<uuid> --include=parents,children

# List traces for an aggregation (slowest first by default)
flare list-aggregation-traces --type=routes --uuid=<uuid> --sort=slowest

# Get a full trace with span tree, events, resources, and contexts
flare get-trace --trace-id=<trace-id>

Pagination

All list commands support pagination:

bash

flare list-project-errors --project-id=123 --page-number=2 --page-size=20

Response includes meta (current_page, total, last_page) and links (next/prev URLs).

Common workflows

Error triage

List open errors, categorize by exception class, resolve or snooze in batches. See references/workflows.md for the full triage workflow.

Quick version:

bash

# 1. List open errors sorted by most recent
flare list-project-errors --project-id=123 --filter-status=open --sort=-last_seen_at

# 2. Review each error, resolve fixed ones
flare resolve-error --error-id=456

# 3. Snooze noisy but non-critical errors
flare snooze-error --error-id=789 --field snooze_type=snooze_forever

Debug an error with local code

Fetch an occurrence, find application frames, then read the corresponding local files. See references/workflows.md for detailed steps.

Quick version:

bash

# 1. Get the latest occurrence
flare list-error-occurrences --error-id=456 --sort=-received_at --page-size=1

# 2. Look at the frames where application_frame=true
# 3. Read the local file at the reported line number
# 4. Check attributes for request context, events for log trail, solutions for fixes

Investigate slow performance

Get a performance overview, drill into slow aggregations, and inspect individual traces. See references/workflows.md for the full workflow.

Quick version:

bash

# 1. Get the performance summary
flare get-monitoring-summary --project-id=123 --filter-interval=24h

# 2. List the slowest routes by p95
flare list-monitoring-aggregations --project-id=123 --type=routes --sort=-p95

# 3. Get details on a specific slow route
flare get-monitoring-aggregation --type=routes --uuid=<uuid> --include=children

# 4. List traces for that route, slowest first
flare list-aggregation-traces --type=routes --uuid=<uuid>

# 5. Inspect the slowest trace
flare get-trace --trace-id=<trace-id>

Create a project and get API keys

Create a project via CLI, retrieve API keys, and verify errors are flowing. See references/workflows.md for the step-by-step guide.

Show full SKILL.md (152 more words)Show less

Output format

All commands return JSON. When presenting results to the user:

Errors: Show as a table with columns: ID, exception class, message (truncated), status, occurrence count, last seen. Always include the latest_occurrence_url_on_flare link.
Occurrences: Highlight application frames (where application_frame is true) — these are the user's code, not vendor code. Show the relative_file and line_number.
Solutions: If solutions is non-empty, always present them prominently — they contain actionable fix suggestions.
Attributes: Group by the group field (e.g., request, user, environment) when displaying context.
Events: Show chronologically — they represent the execution trail leading to the error (queries, logs, jobs, etc.).
Flare URLs: Include latest_occurrence_url_on_flare so the user can view the full error in the Flare dashboard.
Monitoring aggregations: Show as a table with columns: name/label, p95, average, count, error rate. Highlight aggregations with high p95 or error rate.
Traces: Show the span tree hierarchically. Highlight spans with the longest duration — these are the bottlenecks.

Files

SKILL.md and 2 other files (references) in config/claude/skills/flare of freekmurze/dotfiles.

SKILL.md
references/commands.md
references/workflows.md

Open the folder on GitHubat commit 8874280

Compare with similar skills

Flare next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Flare compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Flare this skillfreekmurze/dotfiles	1k	—	~2.1k	Automated safety check: Pass	MIT	yesterday
Cost Trackingaffaan-m/ECC	276k	1 repos	~1.3k	Automated safety check: Pass	MIT	4 days ago
TrackingBuilderIO/agent-native	7.1k	—	~8k	Automated safety check: Pass	None	today
Time Trackingsickn33/agentic-awesome-skills	47k	1 repos	~3.8k	Automated safety check: Pass	MIT	today
Horizon Trackruvnet/ruflo	74k	—	~744	Automated safety check: Notes	MIT	today
Cost Trackruvnet/ruflo	74k	—	~773	Automated safety check: Notes	MIT	today

Similar skills

Cost Tracking
affaan-m/ECC
Track and report Claude Code token usage, spending, and budgets from the local ECC cost-tracker metrics log.
276k GitHub starsUsed in 1 repo~1.3k tokens
AI & LLM EngineeringAuto-check passed
Tracking
BuilderIO/agent-native
Server-side analytics tracking with pluggable providers. An agent skill from BuilderIO/agent-native.
7.1k GitHub stars~8k tokensUpdated today
Backend & APIsAuto-check passed
Time Tracking
sickn33/agentic-awesome-skills
Time entry register: employee, project, client, task, hours, billable flag, rate and amount, invoice and approver.
47k GitHub starsUsed in 1 repo~3.8k tokens
Productivity & AutomationAuto-check passed
Horizon Track
ruvnet/ruflo
Track long-horizon objectives across multiple sessions with milestone checkpoints, progress persistence, and drift detection
74k GitHub stars~744 tokensUpdated today
Product & Project ManagementAuto-check: notes
Cost Track
ruvnet/ruflo
Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace
74k GitHub stars~773 tokensUpdated today
AI & LLM EngineeringAuto-check: notes
Analytics Tracking
alirezarezvani/claude-skills
Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality.
28k GitHub starsUsed in 1 repo~3.8k tokens
Data & AnalyticsAuto-check passed

Questions about Flare

What does Flare do?

Manage Flare error tracking and performance monitoring using the flare CLI. Flare is an agent skill from freekmurze/dotfiles. Manage Flare error tracking and performance monitoring using the flare CLI.

When should I use Flare?

Flare fits situations like: the user wants to list; manage projects; create projects and retrieve API keys; check error counts.

How do I install Flare in Claude Code?

Run `npx skills add freekmurze/dotfiles --skill flare -a claude-code`. Or copy the skill folder (config/claude/skills/flare in freekmurze/dotfiles) into .claude/skills/flare in your project. Claude Code loads it when a task matches its description.

How do I install Flare in Codex?

Run `npx skills add freekmurze/dotfiles --skill flare -a codex`. Or copy the skill folder (config/claude/skills/flare in freekmurze/dotfiles) into .agents/skills/flare in your project. Codex loads it when a task matches its description.

Can I use Flare in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add freekmurze/dotfiles --skill flare -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/flare, .gemini/skills/flare, .github/skills/flare and .opencode/skills/flare in your project.

What does Flare need to run?

Going by SKILL.md and its folder, Flare needs the command-line tools its instructions call (composer).

Does Flare access the network?

SKILL.md names 1 domain. As links in the text: flareapp.io. This is read from the text; nothing was executed.

Is Flare safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Flare use?

Flare is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Flare use?

About 2.1k tokens (SKILL.md is roughly 8.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.4k tokens, read only when the agent opens those files.

What are the alternatives to Flare?

Skills that share tags, products or a category with Flare: Cost Tracking (affaan-m/ECC, 276k stars), Tracking (BuilderIO/agent-native, 7.1k stars), Time Tracking (sickn33/agentic-awesome-skills, 47k stars) and Horizon Track (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Flare?

freekmurze (a GitHub user) maintains it in freekmurze/dotfiles, which has 1,013 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 2026.

Source: freekmurze/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Flare

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Flare CLI

Prerequisites

Authentication

Quick command reference

User & team

Projects

Errors

Error actions

Occurrences

Performance monitoring

Pagination

Common workflows

Error triage

Debug an error with local code

Investigate slow performance

Create a project and get API keys

Output format

Files

Compare with similar skills

Similar skills

More from freekmurze/dotfiles

Questions about Flare