fnl-update
Update the plugin
Run only at the user's request. A session-start notice tells the agent to let the user know a newer version is available and that they can type /fnl-update (on Codex $fnl-update). Only the user can invoke this skill; the notice is not permission to update. An earlier yes to checking or opening this skill is not a yes to installing an update.
The helper and its shared core are in this skill's own scripts/ folder. Resolve <update_check.py> there. It uses fnl_metrics.state_dir() for all state, independently of metrics consent. It reads the plugin's own manifest when installed with the plugin; a standalone skill has no manifest, so its installed version is unknown. Use the host's installed-plugin listing to establish that version rather than guessing it.
Arguments: $ARGUMENTS
Show the facts, then ask
- Run
python3 -I <update_check.py> status. This reads local state only. Showinstalled,available(the cached latest stable release), whether it isnewer, whether the cache isstale, and any skipped versions or never-ask choice. A null value is unknown, not evidence that the plugin is current. Empty output means the check is off or a read failed: report that limitation. Do not fetch a release manually or claim a stale cache is current. The automatic startup hook schedules a background refresh after 24 hours; the result is read on a later startup. A standalone skill has no automatic hook. - If the user only asked for status, finish with those facts. If the user requests an update, identify the host and installed plugin identifier from its plugin listing. Report the proposed native command, the verified or unverified status below, and any required restart or trust step. Ask for a clear yes to running that command now. Wait for the answer. A skip, silence or ambiguous answer grants no permission to update.
- After that yes, run only a verified native update command for the matching host and installed identifier. Report the actual result. An error is an error, not a successful update. On Claude Code, tell the user to restart Claude Code before using the new plugin. On Codex, the plugin's hooks need trust again after an update: open
/hooksin a new session and review them. Verify the resulting installed version with the host's listing; a still-running session's manifest can describe the old loaded copy.
Host commands: checked 2026-11-04
These are CLI help observations, not proof that an update completed. No update was executed during implementation.