← Back to Skills Marketplace
Research Tracker
by
julian1645
· GitHub ↗
· v0.1.0
3008
Downloads
1
Stars
14
Active Installs
1
Versions
Install in OpenClaw
/install research-tracker
Description
Manage and track autonomous AI research projects with state logging, instruction queues, agent coordination, and progress monitoring via SQLite.
Usage Guidance
This skill appears to be a wrapper around a local CLI that tracks agent work in a SQLite DB — functionally coherent. However: (1) the SKILL.md tells you to add an unknown Homebrew tap and to go install code from github.com/1645labs — review that repository and the brew tap contents before installing; these sources can run arbitrary code. (2) The registry metadata omits required binaries/env/config that the instructions use (research binary, RESEARCH_SESSION_ID, and ~/.config/research-tracker/research.db) — ask the publisher to fix metadata. (3) Treat SESSION_KEY and RESEARCH_SESSION_ID as potentially sensitive; avoid exporting secrets into long-lived environment variables unless you understand what they contain. (4) Prefer installing from a verified release (checksums, signed releases), run initial installs in an isolated environment (VM/container), and inspect the code/migration scripts before running migrations. If you cannot audit the tap/repo, consider this a risk and do not install on a sensitive machine.
Capability Analysis
Type: OpenClaw Skill
Name: research-tracker
Version: 0.1.0
The skill bundle is classified as suspicious primarily due to its reliance on external, potentially untrusted sources for installation. The `SKILL.md` instructs the AI agent to install a tool via `brew tap 1645labs/tap && brew install julians-research-tracker` or `go install github.com/1645labs/julians-research-tracker/cmd/research@latest`. This introduces a significant supply chain risk, as the integrity of the `1645labs` Homebrew tap or the specified Go repository cannot be guaranteed, potentially leading to the installation of malicious software. While the skill's stated purpose and internal instructions appear benign, the method of acquiring its core functionality is a high-risk behavior.
Capability Assessment
Purpose & Capability
SKILL.md describes a local CLI (research) that manages SQLite state for coordinating autonomous agents — this matches the skill name/purpose. However, the registry metadata lists no required binaries or config paths while the instructions clearly require installing a 'research' binary and will use ~/.config/research-tracker/research.db. That metadata/instruction mismatch should be clarified.
Instruction Scope
Instructions are narrowly scoped to installing/running the 'research' CLI, logging events, heartbeats, checking for instructions, and using a local SQLite DB. The SKILL.md does not instruct the agent to read arbitrary unrelated files or to exfiltrate data. It does reference exporting RESEARCH_SESSION_ID (and implies SESSION_KEY) which could be sensitive, so care is needed when setting session environment variables.
Install Mechanism
There is no formal install spec in the registry, but the SKILL.md tells users/agents to 'brew tap 1645labs/tap' and 'brew install julians-research-tracker' or 'go install github.com/1645labs/julians-research-tracker/cmd/research@latest'. Both commands fetch and install code from third-party sources (unknown tap/org). Homebrew taps and go installs can execute arbitrary code; this is the highest-risk area and should be audited or replaced with verified release artifacts/checksums.
Credentials
The skill declares no required environment variables, but the docs reference RESEARCH_SESSION_ID (and SESSION_KEY) for tracking agent sessions. The local DB path (~/.config/research-tracker/research.db) is also used. Requested environment access is minimal and consistent with purpose, but the mismatch between declared and referenced env vars should be fixed and SESSION_KEY may be sensitive—avoid exporting secrets without review.
Persistence & Privilege
The skill does not request elevated privileges or an 'always' presence. It will create and persist a local SQLite DB in the user's home config directory and run migrations; that persistent local state is expected for this tool but you should be aware it will store events and state on disk.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install research-tracker - After installation, invoke the skill by name or use
/research-tracker - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of research-tracker CLI.
- Manage autonomous research agents with explicit project/objective tracking.
- Append-only state/event log using local SQLite database.
- Instruction queue system enables agent handoffs and urgent/operator interventions.
- Heartbeat and attention detection for monitoring long-running or background research.
- Multi-step investigation supported with progress/state checkpoints.
- Includes auditing, blocking, stop signals, and archive functions for project oversight.
Metadata
Frequently Asked Questions
What is Research Tracker?
Manage and track autonomous AI research projects with state logging, instruction queues, agent coordination, and progress monitoring via SQLite. It is an AI Agent Skill for Claude Code / OpenClaw, with 3008 downloads so far.
How do I install Research Tracker?
Run "/install research-tracker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Research Tracker free?
Yes, Research Tracker is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Research Tracker support?
Research Tracker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Research Tracker?
It is built and maintained by julian1645 (@julian1645); the current version is v0.1.0.
More Skills