AG Graph Builder

Convert Python scripts into AetherGraph workflows using @tool and @graphify.

7|Updated Nov 3, 2025
One-click install
npx skills add https://github.com/AIperture/aethergraph --skill ag-graph-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AG Graph Builder
Source: https://github.com/AIperture/aethergraph/tree/main/src/aethergraph/plugins/agents/graph_builder/skills
Command: npx skills add https://github.com/AIperture/aethergraph --skill ag-graph-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Turn user intent and/or existing Python scripts into reliable AetherGraph @tool + @graphify workflows, with optional artifact checkpointing for expensive steps.

Core Features & Use Cases

  • Converts goals and scripts into deterministic DAG workflows using @tool and @graphify.
  • Preserves existing Python imports and wraps functions into graph nodes for easy reuse.
  • Adds artifact checkpointing for expensive or iterative steps to enable resumable runs.
  • Provides strict graph construction invariants and guidance to ensure correct orchestration.
  • Use cases include transforming a data processing script into a production-grade graph and iteratively refining workflows.

Quick Start

Provide your goals and any Python script references to generate a graphify workflow.

Frequently Asked Questions about AG Graph Builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Python scripts into DAG-based automation workflows?

To convert Python scripts into DAG-based automation workflows, provide your script and goals to generate a deterministic graph. The process wraps existing functions into graph nodes using @tool and @graphify forms while preserving your original imports.

What is graphify workflow orchestration and when do I need it?

Graphify workflow orchestration is the process of structuring scripts into deterministic directed acyclic graphs (DAGs) using @tool and @graphify. You need it when building reliable pipelines that require strict task ordering and typed inputs for complex automation.

Can I add artifact checkpointing to expensive steps in an AetherGraph workflow?

Yes, you can add artifact checkpointing to expensive steps in an AetherGraph workflow. This feature enables resumable runs by saving intermediate outputs, which is critical for iterative processing or long-running complex orchestration tasks.

Does the graph conversion process preserve existing Python imports?

Yes, the graph conversion process explicitly preserves existing Python imports. When wrapping your functions into graph nodes, the original import statements are maintained to ensure the generated @tool and @graphify workflow executes correctly without missing dependencies.

What are the limitations of converting scripts to AetherGraph flows?

A key constraint is that conversion requires strict graph construction invariants. You must enforce explicit @tool and @graphify forms with typed inputs, meaning scripts lacking clear function boundaries or untyped parameters will require refactoring before orchestration.

What is the best way to structure intent for building AetherGraph workflows?

The best way to build AetherGraph workflows is to provide clear user intent alongside Python script references. This allows the conversion mechanism to apply strict invariants and generate a deterministic graph that accurately reflects your automation goals.