Skills for coding agents

Two skills for coding agents come with the package. One teaches an agent to read your logs, and the other reads your code and proposes where fsl would help it.

npx fsl install-skills copies two skills into .claude/skills/ in the current project, the folder Claude Code reads. Add --global to install them in ~/.claude/skills/ instead. For a different agent, see Other coding agents.

Skill	What it does
/fsl-logs	How to answer a question from the logs with fsl logs: the shape of a query, schema for the labels, --repeats for how often an error really happened, attachments for the files. See fsl logs.
/fsl-review [scope]	Reads the guide inside the installed package and the code in the scope, which is the app, a folder or a file. Then proposes how fsl could best serve that code: what to add, what to fix.

/fsl-review proposes and stops

It makes no edits and opens no issues. The scope is the whole app when none is given.

1. It finds the installed package. For a folder or file it walks up from the scope to the first node_modules/@dasasian/firebase-structured-logger. If the Cloud Functions folder has a different version from the project root, the proposal names both.
2. For the whole app, it runs npx fsl doctor --json first and folds the findings into the list. See fsl doctor.
3. It reads the guide, then your code, and returns a short list in the order it would do the changes. It says nothing about code that is already right.

The skills hold only steps. The facts come from that guide, a file named CAPABILITIES.md inside the package version that you run. So a skill that you installed last year still gives answers for the version you have today.

Trim the list, then have your agent make the changes, file issues, or both. Typical findings are a route with no breadcrumbs, a scheduled job with no logger, or a loading screen worth timing.

Other coding agents

The installer writes to Claude Code’s folder only. The skills themselves are plain markdown, and nothing in them is specific to one agent. For a different agent, do one of these:

• Copy the two folders in node_modules/@dasasian/firebase-structured-logger/skills/ to the folder where your agent looks for skills.
• Point the agent at one file. For example: “Read node_modules/@dasasian/firebase-structured-logger/skills/fsl-logs/SKILL.md and follow it.”

fsl logs and CAPABILITIES.md do not depend on the agent. A copy you make by hand is not stamped with the fsl version, so fsl doctor does not check it. Copy the folders again after you upgrade fsl.

Install and update

npx fsl install-skills
npx fsl install-skills --global
npx fsl install-skills --force

Flag	Effect
--global	Install into ~/.claude/skills/ instead of the project.
--force	Answer yes to every question.

install-skills stamps the fsl version into each skill’s frontmatter as fsl-version. It asks before it overwrites a file, and before it removes a skill this package no longer ships: the old /logs and /query-logs. It touches no other folder.

With no terminal to answer on, such as an agent’s shell or CI, and no --force, it asks nothing. It installs the skills that need no answer, says on stderr what it left, and exits 1.

Note

After you upgrade fsl, fsl doctor warns skill-out-of-date when a skill’s fsl-version differs from the installed package. Run npx fsl install-skills again. A skill with no fsl-version is not ours and is skipped.