daimon-design

Rework Aether Agents Daimon profiles to fix misalignment and configuration drift.

3|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/DarkArty07/Aether-Agents --skill daimon-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daimon-design
Source: https://github.com/DarkArty07/Aether-Agents/tree/main/home/skills/autonomous-ai-agents/daimon-design
Command: npx skills add https://github.com/DarkArty07/Aether-Agents --skill daimon-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the risk of misaligned, bloated, or outdated Aether Agents Daimon profiles that cause poor agent role adherence, excessive token overhead, and configuration drift between live configs and deployment templates.

Core Features & Use Cases

  • Agent Type Taxonomy: Classify Daimons as Actor, Consultant-Creator, or Consultant-Analyst to select correct toolsets and define write/read permissions.
  • SOUL.md Design Principles: Keep agent system prompts concise (80-130 lines), avoid duplication, and extract domain-specific content to on-demand skills to reduce per-turn token costs.
  • End-to-End Rework Workflow: Covers the full Daimon rework cycle from role definition and config selection to implementation, testing, template sync, and release, including toolset dependency audits and MCP content limit workarounds.
  • Use Case: When reworking a security-focused Daimon from a generic actor to a Consultant-Analyst, use this Skill to trim its SOUL.md, move detailed security checklists to a dedicated on-demand skill, and adjust toolsets to remove unnecessary write permissions.

Quick Start

Use the daimon-design skill to rework an existing Daimon's profile, update its toolset to match its new role, and extract verbose domain content to an on-demand skill to reduce per-turn token usage.

Frequently Asked Questions about daimon-design

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

FAQPage Schema
How do I reduce token overhead in multi-agent system profiles?

To reduce multi-agent system profile token overhead, author concise SOUL.md system prompts between 80-130 lines and extract verbose domain-specific content into on-demand skills to lower per-turn token costs.

What is the best way to classify agent types for correct toolset selection?

Classify agent types as Actor, Consultant-Creator, or Consultant-Analyst to select correct toolsets and define appropriate write and read permissions for multi-agent system configuration.

How do I fix configuration drift in Aether Agents Daimon deployments?

Fix configuration drift in Aether Agents Daimon deployments by running an end-to-end rework workflow that synchronizes live config.yaml toolsets with deployment templates and audits toolset dependencies.

When should I rework an agent profile to remove unnecessary write permissions?

Rework an agent profile to remove unnecessary write permissions when changing its role taxonomy, such as transitioning a generic actor to a Consultant-Analyst, requiring read-only access for security-focused operations.

Does this approach work for extracting domain content to on-demand skills?

Yes, this approach works for extracting domain content to on-demand skills by moving detailed checklists and verbose domain content out of the SOUL.md prompt, reducing per-turn token usage while maintaining agent identity.

What are the limitations of keeping verbose domain content in SOUL.md?

Keeping verbose domain content in SOUL.md causes poor agent role adherence, excessive per-turn token costs, and configuration duplication, making it necessary to extract detailed content to dedicated on-demand skills.