research-tracker
Manage autonomous AI research agents with SQLite-based state tracking. Use when spawning long-running research sub-agents, tracking multi-step investigations, coordinating agent handoffs, or monitoring background work. Triggers on: research projects, sub-agent coordination, autonomous investigation, progress tracking, agent oversight.
Best use case
research-tracker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage autonomous AI research agents with SQLite-based state tracking. Use when spawning long-running research sub-agents, tracking multi-step investigations, coordinating agent handoffs, or monitoring background work. Triggers on: research projects, sub-agent coordination, autonomous investigation, progress tracking, agent oversight.
Teams using research-tracker should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/research-tracker/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How research-tracker Compares
| Feature / Agent | research-tracker | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage autonomous AI research agents with SQLite-based state tracking. Use when spawning long-running research sub-agents, tracking multi-step investigations, coordinating agent handoffs, or monitoring background work. Triggers on: research projects, sub-agent coordination, autonomous investigation, progress tracking, agent oversight.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Research Tracker
CLI tool for managing autonomous research agents with append-only state, instruction queues, and oversight.
## Prerequisites
```bash
brew tap 1645labs/tap
brew install julians-research-tracker
```
Or: `go install github.com/1645labs/julians-research-tracker/cmd/research@latest`
## Quick Start
### Start a research project
```bash
research init market-q1 --name "Q1 Market Analysis" --objective "Analyze competitor pricing and positioning"
```
### As the research agent — log progress
```bash
export RESEARCH_SESSION_ID="$SESSION_KEY" # Track which agent is writing
research log market-q1 STEP_BEGIN --step 1 --payload '{"task":"gather sources"}'
# ... do work ...
research log market-q1 STEP_COMPLETE --step 1
research heartbeat market-q1
```
### Check status (from main session or heartbeat)
```bash
research status market-q1 --json
research context market-q1 --last 5 # Truncated context for prompts
```
### Send instructions to running agent
```bash
research instruct market-q1 "Focus on enterprise segment" --priority URGENT
research stop-signal market-q1 # Request graceful stop
```
### Agent checks for instructions
```bash
research pending market-q1 --json
research ack market-q1 --all # Acknowledge after processing
research check-stop market-q1 # Exit 0 = stop, Exit 1 = continue
```
## Commands Reference
| Command | Purpose |
|---------|---------|
| `init <id> -o "..."` | Create project with objective |
| `list [--status active\|done\|all]` | List projects (includes `needs_attention` flag) |
| `show <id>` | Project details + recent events |
| `stop <id>` | Stop project, send STOP instruction |
| `archive <id>` | Archive completed project |
| `log <id> <event> [--step N]` | Log event (STEP_BEGIN, CHECKPOINT, BLOCKED, etc.) |
| `heartbeat <id>` | Update alive timestamp |
| `block <id> --reason "..."` | Mark blocked, needs input |
| `complete <id>` | Mark done |
| `status <id> [--json]` | Current state summary |
| `context <id> [--last N]` | Truncated context for agent prompts |
| `instruct <id> "text"` | Send instruction |
| `pending <id>` | List unacked instructions |
| `ack <id> [--all]` | Acknowledge instructions |
| `check-stop <id>` | Exit code: 0=stop, 1=continue |
| `audit <id> --verdict pass\|drift` | Log audit result |
## Event Types
`STARTED`, `STEP_BEGIN`, `STEP_COMPLETE`, `CHECKPOINT`, `BLOCKED`, `UNBLOCKED`, `AUDIT_PASS`, `AUDIT_DRIFT`, `HEARTBEAT`, `DONE`, `STOPPED`, `TIMEOUT`
## Integration Pattern
### Spawning a research agent
```
1. research init <project> --objective "..."
2. sessions_spawn with task including:
- Project ID and objective
- Instructions to use research CLI for state
- Check stop signal before each step
- Log progress with heartbeat
3. Heartbeat monitors: research list --json | check needs_attention
4. Send instructions via: research instruct <project> "..."
```
### Agent loop (in spawned agent)
```bash
while research check-stop $PROJECT; [ $? -eq 1 ]; do
research pending $PROJECT --json # Check instructions
research log $PROJECT STEP_BEGIN --step $STEP
# ... do work ...
research log $PROJECT STEP_COMPLETE --step $STEP
research heartbeat $PROJECT
STEP=$((STEP + 1))
done
research complete $PROJECT
```
## Attention Detection
`research list --json` includes `needs_attention: true` when:
- Last event is BLOCKED
- Has unacked URGENT or STOP instructions
- Heartbeat stale (>5 min since last HEARTBEAT event)
- Last audit was AUDIT_DRIFT
## Database
SQLite at `~/.config/research-tracker/research.db` (WAL mode, append-only events).
Run `research db migrate` after install. Schema auto-migrates on first use.Related Skills
task-tracker
Personal task management with daily standups and weekly reviews. Use when: (1) User says 'daily standup' or asks what's on their plate, (2) User says 'weekly review' or asks about last week's progress, (3) User wants to add/update/complete tasks, (4) User asks about blockers or deadlines, (5) User shares meeting notes and wants tasks extracted, (6) User asks 'what's due this week' or similar.
academic-deep-research
Transparent, rigorous research with full methodology — not a black-box API wrapper. Conducts exhaustive investigation through mandated 2-cycle research per theme, APA 7th citations, evidence hierarchy, and 3 user checkpoints. Self-contained using native OpenClaw tools (web_search, web_fetch, sessions_spawn). Use for literature reviews, competitive intelligence, or any research requiring academic rigor and reproducibility.
yandex-tracker
Work with Yandex Tracker (issues, queues, comments, attachments, links, search, bulk operations) via Python.
invoice-tracker-pro
Complete freelance billing workflow — generate professional invoices, track payment status, send automated.
saas-revenue-tracker
Track SAAS revenue, MRR growth, customer metrics, and profitability.
yutori-web-research
Use Yutori’s Research API and Browsing API (cloud browser) to research topics, collect sources, and extract structured facts from the web. Use when the user asks to “research X”, “monitor/find papers”, or “navigate to a site and extract info” and you have access to YUTORI dev/prod endpoints via YUTORI_API_BASE and an API key in env (YUTORI_API_KEY or ~/.openclaw/openclaw.json env.YUTORI_API_KEY).
research-library
Local-first multimedia research library for hardware projects.
research-assistant
Organized research and knowledge management for agents.
plant-tracker
Personal plant and garden management for gardeners.
pest-disease-tracker
Track garden pests and diseases with treatments.
compost-tracker
Track compost piles, monitor temperature, record turns, and manage your organic waste decomposition.
package-tracker
Track packages and shipments via the 17track API.