agentleFS
AI-ModConAI-ModCon/genesis-skills/skills/academy/SKILL.md

academy

Skill30 starsChanged 49 days agoBSD-2-ClauseView on GitHub

Academy agent framework for distributed scientific computing. Use when building agents with @action decorators, configuring exchanges and managers, creating HPC integrations, or designing multi-agent scientific workflows.

  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Academy when you need:

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Academy Agent Framework

Academy is middleware for deploying autonomous agents across federated research ecosystems, including HPC systems, experimental facilities, and data repositories.

When to Use Academy

Use Academy when you need:

  • Distributed execution across multiple machines or HPC systems
  • Stateful agents that maintain state across interactions
  • Inter-agent coordination via message passing
  • Federation across institutional boundaries (via Globus)
  • Long-running autonomous workflows for scientific discovery

Core Concepts

Agents

Python classes inheriting from Agent with @action-decorated async methods:

from academy.agent import Agent, action

class SimulationAgent(Agent):
    @action
    async def run_simulation(self, parameters: dict) -> dict:
        # Perform computation
        return {"energy": -127.5, "status": "completed"}

Actions

Methods decorated with @action can be invoked remotely by users or other agents. They must be async and can accept/return serializable data.

Loops

Methods decorated with @loop run autonomously and continuously. A loop receives a shutdown event and must check it every iteration (and yield control, e.g. by sleeping), or the agent will hang at shutdown:

import asyncio
from academy.agent import Agent, action, loop

class MonitorAgent(Agent):
    @loop
    async def monitor(self, shutdown: asyncio.Event) -> None:
        while not shutdown.is_set():
            data = await self.collect_data()
            if self.should_alert(data):
                await self._coordinator.notify(data)
            await asyncio.sleep(1)

Handles

Proxy objects for inter-agent communication. When you receive a Handle, you can call its actions as if it were local:

@action
async def set_analyzer(self, analyzer: Handle) -> None:
    self._analyzer = analyzer

@action
async def process(self, data: dict) -> dict:
    # Call remote agent's action
    return await self._analyzer.analyze(data)

Manager and Exchange

The Manager launches and coordinates agents. The Exchange handles message transport:

from concurrent.futures import ThreadPoolExecutor
from academy.manager import Manager
from academy.exchange import LocalExchangeFactory
from academy.logging.recommended import recommended_logging

async with await Manager.from_exchange_factory(
    factory=LocalExchangeFactory(),  # Local dev
    executors=ThreadPoolExecutor(),  # Where agents run (default: event loop)
    log_config=recommended_logging(),
) as manager:
    agent = await manager.launch(SimulationAgent)
    result = await agent.run_simulation({"temp": 300})

Installation

pip install "academy-py==0.5.*"

Additional Resources

  • For detailed agent patterns, see agents.md
  • For communication patterns, see communication.md
  • For orchestration patterns, see patterns.md
  • For scientific workflow examples, see examples.md

Quick Reference

DecoratorPurpose
@actionRemote-callable method
@loopAutonomous continuous execution
Exchange TypeUse Case
LocalExchangeFactorySingle-process development/testing
RedisExchangeFactoryMulti-machine deployment via a Redis server
HttpExchangeFactoryHosted cloud exchange; cross-site/federated (Globus auth)

To run agents on HPC, pass a Globus Compute Executor to the Manager's executors= — the exchange moves messages; executors decide where agents run.

Links

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.