anarlog

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included.

File history ↗

Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.

agent-plugins/anarlog/skills/anarlog/SKILL.md

Download bundle ↓
main · 143e3d85 bundle filesScanned 2026-09-15

references/errors.md

438 tokens · o200k_base · 1,974 bytes

Source excerpt starting at line 1.
# Errors ## Meeting not found List or search meetings again and use the returned ID. Do not retry a guessed ID. ## No meetings returned If Cloud `list_meetings` returns an empty list, search again with `anarlog --json meetings list` when the local CLI is available. An empty Cloud list usually means snapshots are off or that meeting has not uploaded. Tell the user none were found only after the sources you can reach are empty. Do not invent meetings. ## Database not found Run `anarlog --json doctor`. Ask the user to open Anarlog once if the database does not exist. If they keep data in a custom location, use `--db-path FILE` or `ANARLOG_DB_PATH` after they provide the path. ## Database operation failed Confirm the desktop app and CLI come from compatible revisions. Do not run migrations or write SQL from the agent. ## Cloud command failed Preserve the CLI's hosted error code. Run `anarlog auth login` again for `unauthorized`, ask the user to enable **Cloud API & Connectors** for `cloud_api_not_enabled`, and wait for the reported retry delay after `rate_limited`. Do not silently switch a user-requested `--source cloud` read to local data. ## Export output exists Choose a new path. Pass `--force` only when the user explicitly approves replacing that exact file. ## MCP server exits Run `anarlog --json meetings list` to distinguish database access from client configuration. Confirm the MCP command is `anarlog` and its only required argument is `mcp`. Missing meetings and proposals are invalid parameters. Validation and conflict failures, including declining a non-pending proposal, are internal MCP errors. With `--json`, errors contain `schema_version` and an `error` object with `code`, `message`, and `exit_code`. CLI exit codes are `1` for an operation failure, `2` for missing data, `3` for a missing database, and `4` for an existing export target. Invalid CLI arguments use Clap's exit code and the `invalid_arguments` error code. 
Referenced from SKILL.md