Skip to content
Back to skills

Research

ASecurity

Launch an autonomous research agent that iterates toward a goal through proofs, code, simulations, tests, and counterexample search. Fire-and-forget mode: the agent runs autonomously and writes all results to .research/ in the target project.

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 19, 2026
ai-agentsgo

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add queelius/claude-anvil --skill research --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Research?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Research
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/queelius-research/badge)](https://www.skillsdirectory.com/skills/queelius-research)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: research
description: >-
  Launch an autonomous research agent that iterates toward a goal through
  proofs, code, simulations, tests, and counterexample search.
  Fire-and-forget mode: the agent runs autonomously and writes all results
  to .research/ in the target project.
---

# Autonomous Research Agent

Launch an autonomous research agent that iterates toward a goal through proofs, code, simulations, tests, and counterexample search.

## Step 1: Parse the Goal

Read the user's message to extract:

1. **Goal** (required): The natural-language research objective. This is the main content of the user's message.
2. **Eval script** (optional): A path to an executable script. Look for phrases like "eval script at", "use ... as eval", or a path ending in `.sh`, `.py`, or similar.

If the goal is unclear, ask the user to clarify before proceeding. If no eval script is mentioned, the agent will self-evaluate.

## Step 2: Verify Eval Script (if provided)

If an eval script path was given, verify it exists (Read tool). If it does not exist, tell the user and ask whether to proceed with self-evaluation instead.

## Step 3: Check for an Existing Run

If `.research/` already exists in this directory (Glob tool), do not launch fresh. Tell the user a prior run lives here and offer: `/research-agent:resume` to continue it, or archiving it (`mv .research .research-archive/<timestamp>`) before starting fresh. The agent itself also refuses to clobber `goal.md`/`log.md`.

## Step 4: Launch the Agent

Spawn the researcher agent (Agent tool, `subagent_type: research-agent:researcher`) with this prompt structure:

    <goal>
    {the user's research goal, verbatim}
    </goal>

    <eval>
    {path to eval script, or "none - use self-evaluation"}
    </eval>

    <working_directory>
    {current working directory}
    </working_directory>

    Begin your research. Create .research/ and start the DECOMPOSE phase.

The agent runs autonomously from here. Inform the user:

> Research agent launched. It will work autonomously in this directory, writing progress to `.research/log.md`. When it finishes, the synthesis will be at `.research/synthesis.md`.
>
> While it runs, you can:
> - `/research-agent:status` to see cycle progress, current focus, and eval trend (read-only)
> - `/research-agent:resume` to continue after an interruption or session restart
> - `/research-agent:synthesize` to force conclusion if results are good enough or the agent is stalling

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.