Agent Native

suggest-expansions

This skill reviews a scientific theory and identifies concrete expansion opportunities such as generalizations, missing cases, unproven corollaries, or…

by ImbueOfficial publisherNot reviewed

Identity proven by GitHub's verified organisation badge (imbue-ai)

Agents
Claude Code
License
AGPL-3.0 (copyleft)
Pin
a2ee48cpinned Oct 9, 2026
Context cost
about 1,200 tokenswhen the skill loads
GitHub stars
36on imbue-ai/catalyst
Scripts
None found

What it does

“Review an entire theory and suggest concrete areas for expansion”
The author's description, from SKILL.md

Generated summary from the skill's own text

This skill reviews a scientific theory and identifies concrete expansion opportunities such as generalizations, missing cases, unproven corollaries, or connections to adjacent fields. The agent reads the entire theory, generates expansion ideas using structured strategies, validates them through experiments via the run-experiment skill, and writes a prioritized review with evidence for each suggestion.

When to use it

  • Extending an existing mathematical or scientific theory into new domains or regimes
  • Identifying gaps and unproven results that follow from current theorems
  • Finding connections between a theory and adjacent research areas
  • Planning the next research directions for a theory development project

When not to

  • Revising or fixing errors in an existing theory
  • Running experiments without systematic guidance or structure
  • Working with theories lacking clear mathematical or experimental foundation

Install

These commands install from the publisher's repository and need no account.

skills CLI

npx skills add imbue-ai/catalyst --skill suggest-expansions

Installs from the repository's default branch, which may have changed since the commit we checked.

GitHub CLI 2.90 or later

gh skill install imbue-ai/catalyst suggest-expansions@a2ee48c34741df5d4549d97b22aa44589d9eaa6a

Installs the commit we checked (a2ee48c).

Copy by hand

Download the folder at a2ee48c and put it in .claude/skills/suggest-expansions for Claude Code and in .agents/skills/suggest-expansions for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode.

Skill folder on GitHub at a2ee48c

Copy for your agent

A prompt for any coding agent. It installs this skill from GitHub at the pinned commit, copies the files as they are, and runs nothing unless you ask.

Prompt

Install the agent skill "suggest-expansions" by Imbue.

Source, pinned to commit a2ee48c34741df5d4549d97b22aa44589d9eaa6a:
https://github.com/imbue-ai/catalyst/tree/a2ee48c34741df5d4549d97b22aa44589d9eaa6a/src/claude_skills/skills/suggest-expansions

1. Download that folder at exactly this commit. Do not use the default branch.
2. Copy every file unchanged, keeping the folder structure, into .claude/skills/suggest-expansions/ for Claude Code and .agents/skills/suggest-expansions/ for Codex, Cursor, Gemini CLI, GitHub Copilot and OpenCode. Create the folders if they do not exist.
3. Do not edit the files, and do not run any script in the folder unless I ask you to.
4. When you are done, list the files you copied and where you put them.

Listing and checks: https://www.agentnative.dev/skills/imbue/suggest-expansions

SKILL.md at the pin

---
name: suggest-expansions
description: "Review an entire theory and suggest concrete areas for expansion"
argument-hint: "theory ID (e.g. T_20260414_143100_d4e5f6)"
---

You are the **Theory Expansion Scout**, an expert scientific agent. Your goal is to read an entire theory and identify the most promising directions for expanding it — new regimes, missing cases, potential generalizations, unproven corollaries, or connections to adjacent fields.

You do NOT rewrite or fix the theory. You SOLELY suggest areas for expansion and write them into a review.

## Mandate
- Work on the **entire theory** holistically.
- Identify concrete, actionable expansion opportunities backed by exploratory experiments or mathematical reasoning.
- All experiment execution must go through the `run-experiment` skill. Never run a Python experiment script directly. See the "Running experiments" section below. You may still derive mathematical arguments inline.
- Your output is a review of expansion opportunities, NOT a revised theory.

## Input
Arguments: $ARGUMENTS

The arguments contain a theory ID (like `T_20260414_...`). Parse the theory ID from the arguments.

## Folder setup
All commands must be run in the current working directory. Do not `cd` anywhere else, do not try to use the global `/tmp` folder or TMPDIR (only use the local `./tmp` folder).

Set up two folders — one for input context, one for your own output:
CONTEXT_DIR: `mktemp -d -p ./tmp suggest-expansions-context-XXXX`
OUTPUT_DIR: `mktemp -d -p ./tmp suggest-expansions-output-XXXX`

Run this command to populate the context:
```bash
uv run python <SKILL_BASE_DIR>/scripts/context_manager.py create_context --for_agent_type suggest-expansions --target_folder <CONTEXT_DIR> --from_theory <THEORY_ID>
```

- `<CONTEXT_DIR>/theory/` — the full theory (read-only input). Read `<CONTEXT_DIR>/theory/theory.md` and any artifacts.
- `<OUTPUT_DIR>/` — write your expansion review, experiments, and supporting notes here.

Any temporary files (including experiment scripts, intermediate results, etc.) must be stored only under `<OUTPUT_DIR>`.

## Running experiments
Every experiment, test, and validation must be set up and run through the `run-experiment` skill, using the AGENT_TYPE `suggest-expansions`.
Cite each experiment by its `X_ID` under the corresponding expansion suggestion in your `review.md`.

## Expansion Strategies
Consider these approaches across the whole theory:
1. **Generalization**: Can any result be stated for a broader class of models, activation functions, or architectures?
2. **Missing Cases**: Are there parameter regimes, boundary conditions, or data distributions the theory does not address?
3. **Unproven Corollaries**: What additional results follow naturally from existing theorems but are not yet stated?
4. **Structural Gaps**: Are there missing lemmas or sections needed to make the theory rigorous or complete?
5. **Connections**: Does the theory relate to known results in dynamical systems, statistical mechanics, random matrix theory, or other fields that could be made explicit?
6. **Quantitative Refinement**: Can asymptotic bounds or scaling laws be tightened?

## Expansion Review Format
Your `review.md` file MUST be formatted as follows:

```
# Expansion Review

## Theory Summary
[Brief summary of the theory's current scope]

## Suggested Expansions

### 1. [Expansion Name]
- **Strategy**: [e.g., Generalization / Missing Cases / Unproven Corollaries / etc.]
- **Description**: [What the expansion would add or generalize]
- **Motivation**: [Why this is worth pursuing — experimental evidence or mathematical argument]
- **Evidence**: [Relevant experiment ID or formula used to support this idea]
- **Feasibility**: [High / Medium / Low]
- **Impact**: [High / Medium / Low]

---

### 2. [Expansion Name]
...

## Prioritized Roadmap
[Rank expansion opportunities by expected impact and feasibility. List the top 3 most important next steps.]
```

## Execution Steps
1. **Context Review**: Read `<CONTEXT_DIR>/theory/theory.md` and any other files in `<CONTEXT_DIR>/theory/` to understand the full theory.
2. **Research**: Analyze the theory holistically. Generate expansion ideas using the strategies above.
3. **Implementation**: Support your suggestions with evidence.
   - **Experiment**: Invoke `run-experiment`. Reference each experiment's `X_ID` under the corresponding expansion suggestion.
   - **Analysis**: If applicable, derive mathematical arguments motivating the expansion.
4. **Reporting**: Write your expansion review to `<OUTPUT_DIR>/review.md` (this exact filename is required). See the output format above.
5. **Store results**: Persist your output and return the review ID:
   ```bash
   uv run python <SKILL_BASE_DIR>/scripts/context_manager.py store_results --from_agent_type suggest-expansions --from_folder <OUTPUT_DIR> --parent_theory <THEORY_ID>
   ```
   Note down the returned review ID (e.g. `R_20260414_143200_g7h8i9`) as the result of this skill and include it in your final message.

From imbue-ai/catalyst at a2ee48c, shown as plain text under its license: AGPL-3.0 (copyleft). The license text is in LICENSE.

View SKILL.md on GitHub at a2ee48c

Files

1 file, 5.0 KB in total. Each file has a sha256 in the pin's manifest; the first 12 characters are shown.

Skill folder on GitHub at a2ee48c
All 50 skills from Imbue

More from Imbue

  • architect

    Generates an architecture document for a feature by reading the existing spec, analyzing the codebase deeply, and conducting guided Q&A with the user to…

    Claude Code · about 4K tokens · pinned 6 days ago

  • build

    This skill executes a multi-step implementation plan by working through task files sequentially.

    Claude Code · about 1.1K tokens · pinned 6 days ago

  • build-sculptor-extension

    Build or modify Sculptor extensions, which are runtime ES modules that add panels, overlays, widgets, home views, or settings UI to the Sculptor frontend.

    Contains scripts

    Claude Code, Codex, Cursor +3 · about 3.3K tokens · pinned 6 days ago

  • fix-bug

    Fixes bugs using test-driven development with an interactive or autonomous workflow.

    Claude Code · about 9.8K tokens · pinned 6 days ago

  • handoff

    This skill hands off ongoing work to a fresh agent, either in the same workspace or a new isolated workspace, while preserving context through a synthesized…

    Claude Code · about 1.1K tokens · pinned 6 days ago

  • help

    This skill fetches the latest Sculptor documentation from GitHub and answers user questions about how to use Sculptor's features, including workspaces…

    Claude Code · about 880 tokens · pinned 6 days ago

All Docs and writing skills
  • n8n-docs-assistant

    This skill answers questions about n8n configuration, setup, credentials, nodes, and troubleshooting by retrieving information from current n8n documentation.

    by n8nOfficial publisher

    Claude Code, Codex, Cursor +3 · about 450 tokens · pinned 6 days ago

  • algodocs-automation

    This skill automates Algodocs document processing tasks through Composio's toolkit via the Rube MCP server.

    by ComposioOfficial publisher

    Claude Code, Codex, Cursor +3 · about 690 tokens · pinned 6 days ago

  • remotion-docs

    This skill enables agents to search and retrieve Remotion documentation via the Algolia API and fetch pages as Markdown.

    by RemotionOfficial publisher

    Claude Code, Codex, Cursor +3 · about 320 tokens · pinned 6 days ago

  • remotion-docs

    This skill searches the Remotion documentation using the Algolia API and retrieves documentation pages as Markdown.

    by RemotionOfficial publisher

    Claude Code, Codex, Cursor +3 · about 320 tokens · pinned 6 days ago

  • receipts

    This skill generates a personal Claude Code usage report from local session transcripts stored in ~/.claude/projects, mining activity across projects without…

    by AnthropicOfficial publisher

    Contains scripts

    Claude Code · about 4.1K tokens · pinned 6 days ago

  • solo

    This skill enables an agent to work through a single difficult mathematics problem independently within one session.

    by AnthropicOfficial publisher

    Claude Code · about 1.4K tokens · pinned 6 days ago

Open roles at Imbue

No open roles at Imbue on the Agent Native jobs board right now.

Browse the jobs board

The skills listed here are third-party software, collected from public GitHub repositories as a catalog of recent skills and provided as is. Agent Native does not write or control them and is not responsible for any harm, loss or damage caused by installing or using them. Labels and checks describe what we saw at one commit and are not a guarantee. Read a skill's files before you run it. Terms of use