66 lines
2.9 KiB
Markdown
66 lines
2.9 KiB
Markdown
# Agent Instructions
|
|
|
|
## Scheduled Reminders
|
|
|
|
**Personal reminders for the user** (notifications about tasks they need to do) → use the `/remind` skill → stored in SQLite (`db/reminders.sqlite`). Never use the `cron` tool for these.
|
|
|
|
**Background agent tasks** (run a script, check something, autonomous action) → use the built-in `cron` tool directly.
|
|
|
|
Test: *Who is the recipient?* User gets notified → `/remind` skill (SQLite `db/reminders.sqlite`). Agent executes something → `cron` tool.
|
|
|
|
**Do NOT just write reminders to MEMORY.md** — that won't trigger actual notifications.
|
|
|
|
## Heartbeat Tasks
|
|
|
|
`HEARTBEAT.md` is checked on the configured heartbeat interval. Use file tools to manage periodic tasks:
|
|
|
|
- **Add**: `edit_file` to append new tasks
|
|
- **Remove**: `edit_file` to delete completed tasks
|
|
- **Rewrite**: `write_file` to replace all tasks
|
|
|
|
When the user asks for a recurring/periodic task, update `HEARTBEAT.md` instead of creating a one-time cron reminder.
|
|
|
|
## Databases (SQLite)
|
|
|
|
Always store SQLite databases under `db/*.sqlite` (relative to the workspace root).
|
|
Never use `/tmp/`, hardcoded absolute paths, or in-memory databases for persistent data.
|
|
|
|
## How you were extended & tuned
|
|
|
|
`develop/` records how this instance was extended and tuned — skills, config, service work — with verified facts and a change log you can learn from (not the upstream code). See `develop/README.md`; read on demand.
|
|
|
|
## Knowledge base
|
|
|
|
`knowledge/` holds verified facts and measured values you can draw on when answering (e.g. notes on the models available to you). See `knowledge/README.md` for what's there; read on demand.
|
|
|
|
## exec Tool
|
|
|
|
The exec safety guard blocks commands without an explicit workspace path (e.g. `lua -e '...'`, `which`). Write scripts to files inside the workspace (e.g. `tmp/script.lua`) and run them with `working_dir` set to the workspace root.
|
|
|
|
## File / Code Conventions
|
|
|
|
### Report / result files
|
|
- Save important reports to `results/` directory with descriptive, date-prefixed filenames (e.g., `2026-06-02_remind-skill-analysis-and-improvements.md`)
|
|
|
|
### Script-writing convention
|
|
- Location: always save scripts in the `scripts/` directory.
|
|
- Language choice:
|
|
- Extremely short script (a few lines) -> bash.
|
|
- Longer / non-trivial script -> Python.
|
|
- Override: if the user explicitly specifies a language or location, their instruction always takes precedence.
|
|
|
|
### Temporary files
|
|
- All temporary files go to `tmp/` directory.
|
|
- Clean up after tests and one-off operations.
|
|
|
|
### Code changes
|
|
- User prefers changes to be made in a temporary clone under `workspace/tmp/<repo-name>` for review before applying
|
|
|
|
## No proactive actions
|
|
|
|
When I ask you to **find out**, **investigate**, **look into**, or **check**
|
|
something, that is a request for information only. Report your findings, then
|
|
ask whether I want them carried out — never treat learning about a problem as a
|
|
request to fix it. When in doubt, ask first.
|
|
|