Spawn Instance

Clone GitHub repositories and register them as configured Aeon instances.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/enuno/noesis-aeon --skill spawn-instance-enuno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Spawn Instance
Source: https://github.com/enuno/noesis-aeon/tree/main/skills/spawn-instance
Command: npx skills add https://github.com/enuno/noesis-aeon --skill spawn-instance-enuno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the cloning of a GitHub repo, configuring it with specific skills, and registering it in the Aeon fleet, significantly reducing the manual work involved in setting up new instances.

Core Features & Use Cases

  • Automated Repo Cloning: Automatically clones a repository and sets up the necessary configurations.
  • Dynamic Skill Configuration: Based on the purpose, it configures the instance with relevant skills.
  • Registration in Fleet: Registers the new instance in the Aeon fleet for further operations.
  • Use Case: Create a new Aeon instance for monitoring a specific market by forking a repository and configuring it with relevant skills.

Quick Start

To spawn a new instance, run 'spawn-instance name: "market-monitor: observe market trends"'

Frequently Asked Questions about Spawn Instance

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

FAQPage Schema
How do I automate cloning a GitHub repository and configuring it for Aeon?

To automate cloning a GitHub repository for Aeon, you can use a skill that handles repository cloning, applies specific skill configurations, and registers the instance in the Aeon fleet. This reduces manual setup work.

What's the best way to register a forked GitHub repo into an Aeon fleet?

The best way to register a forked GitHub repo into an Aeon fleet is by using an automated instance spawning tool. It handles secret propagation, API key isolation, and fleet registration automatically during the setup process.

Do I need GitHub authentication to clone repositories for Aeon instances?

Yes, GitHub authentication is required to clone repositories and configure Aeon instances. The automation process relies on authenticated access to handle secret propagation and API key isolation securely.

Can I dynamically configure skills on a cloned GitHub repo for market monitoring?

Yes, you can dynamically configure skills on a cloned GitHub repo for market monitoring. Based on the instance's defined purpose, the automation applies relevant skills before completing the fleet registration.

Does the Aeon instance spawning process support API key isolation?

Yes, the Aeon instance spawning process supports API key isolation. It manages secret propagation securely during the repository cloning and configuration phases to ensure keys remain isolated per instance.