yjl9903 Eventernote
Use the eventernote CLI as the source of truth for Eventernote data.
Workflow
- Check that the command exists and its version is
0.1.0:
command -v eventernote
eventernote --version
If the command is missing or its version is not
0.1.0, run the requested query withnpx eventernote ...instead. Ifnpx eventernotefails or its version is also not0.1.0, stop and ask the user how they want to proceed.Choose the closest read-only query command for the user's request.
Prefer
--jsonfor agent use. Parse the JSON and summarize the relevant fields for the user. Do not expose raw JSON unless the user asks for it.Use
--page <page>when the user asks for a later page or when more results are needed.If a query is ambiguous, run a list/search command first and ask the user to choose from candidates unless the result is obvious.
Commands
eventernote actor list [keyword] [--popular] [--new] [--page <page>] [--json]
eventernote actor get <id,name> [--json]
eventernote event list [keyword] [--date YYYY-MM-DD] [--region <region>] [--prefecture <prefecture>] [--actor <actor>] [--place <place>] [--page <page>] [--json]
eventernote event get <id,name> [--json]
eventernote place list [keyword] [--prefecture <prefecture>] [--page <page>] [--json]
eventernote place get <id,name> [--json]
Read references/usage.md when choosing a command or interpreting JSON output.