How do I install the Autodiscovery skill?

Run npx skillmds@latest add allenai/autodiscovery in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Autodiscovery safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Autodiscovery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Autodiscovery free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Autodiscovery?

allenai (@allenai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Autodiscovery by allenai — Agent Skill

Name: Autodiscovery
Author: allenai

Autodiscovery

Create, configure, and monitor AutoDiscovery runs — either via the hosted service (`asta autodiscovery`) or via the local CLI (`asta-autodiscovery`). Use when the user asks about their runs, experiments, discoveries, wants to check status, or wants to start a new discovery run.

allenai 4daa1f9 4 files · 13.0 KB Updated Sep 17, 2026

File contents

AutoDiscovery

AutoDiscovery is an AI-driven scientific discovery platform that runs iterative experiments guided by Bayesian surprise and MCTS optimization.

This skill is a router. Inspect the user's request, pick one workflow, then read its .md file in workflows/ and follow it. Do not execute a workflow from memory — always open the file first.

Workflows

Name	Purpose	Detailed instructions
remote	Use the hosted AutoDiscovery service via `asta autodiscovery`. Requires Asta auth and consumes credits; runs execute on Asta infrastructure.	`workflows/remote.md`
local	Run AutoDiscovery locally via the `asta-autodiscovery` CLI. Executes on the user's machine with user-provided API keys for making LLM calls	`workflows/local.md`

Routing

1. Honor explicit requests

"local", "on my machine", "offline", "run it myself", or any reference to the asta-autodiscovery CLI → local.
"remote", "hosted", "cloud", "Asta service", "my runs", "credits", or any reference to the asta autodiscovery (note the space) subcommand → remote.

2. Use signals when the request is ambiguous

Past runs are stored in a local directory for local runs, or on the remote server for remote runs
If the user is starting fresh and has not indicated a preference, ask which workflow they want before proceeding. Mention the tradeoff: remote uses Asta credentials and rate limits; local runs with the user's hardware and credentials.

3. No chaining

The two workflows are independent. Do not silently switch between them mid-task.

---name: autodiscoverydescription: Create, configure, and monitor AutoDiscovery runs — either via the hosted service (`asta autodiscovery`) or via the local CLI (`asta-autodiscovery`). Use when the user asks about their runs, experiments, discoveries, wants to check status, or wants to start a new discovery run.---# AutoDiscoveryAutoDiscovery is an AI-driven scientific discovery platform that runs iterative experiments guided by Bayesian surprise and MCTS optimization.This skill is a **router**. Inspect the user's request, pick one workflow, then read its `.md` file in `workflows/` and follow it. Do not execute a workflow from memory — always open the file first.## Workflows| Name | Purpose | Detailed instructions ||---|---------------------------------------------------------------------------------------------------------------------------------------------|---|| **remote** | Use the hosted AutoDiscovery service via `asta autodiscovery`. Requires Asta auth and consumes credits; runs execute on Asta infrastructure. | `workflows/remote.md` || **local** | Run AutoDiscovery locally via the `asta-autodiscovery` CLI. Executes on the user's machine with user-provided API keys for making LLM calls | `workflows/local.md` |## Routing### 1. Honor explicit requests- "local", "on my machine", "offline", "run it myself", or any reference to the `asta-autodiscovery` CLI → **local**.- "remote", "hosted", "cloud", "Asta service", "my runs", "credits", or any reference to the `asta autodiscovery` (note the space) subcommand → **remote**.### 2. Use signals when the request is ambiguous- Past runs are stored in a local directory for **local** runs, or on the remote server for **remote** runs- If the user is starting fresh and has not indicated a preference, ask which workflow they want before proceeding. Mention the tradeoff: remote uses Asta credentials and rate limits; local runs with the user's hardware and credentials.### 3. No chainingThe two workflows are independent. Do not silently switch between them mid-task.

Frequently asked questions