intername

Generates deterministic, human-readable names for agents and agencies in orchestration systems.

3|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/mistakeknot/Demarch --skill intername
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: intername
Source: https://github.com/mistakeknot/Demarch/tree/main/.gemini/generated-skills/intername
Command: npx skills add https://github.com/mistakeknot/Demarch --skill intername

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides memorable and deterministic identities for agents and agencies, ensuring clear and legible orchestration across all surfaces.

Core Features & Use Cases

  • Agent Naming: Assigns human-readable names to internal agent types.
  • Agency Naming: Provides distinct names for groups of agents.
  • Theming: Supports multiple naming conventions (e.g., culture, diplomatic, NATO phonetic).
  • Use Case: When an agent named fd-safety is dispatched, it appears as "Lapsed Pacifist" in logs and UIs, making it easier to understand its role.

Quick Start

Use the intername skill to resolve the name for the agent type 'fd-safety'.

Frequently Asked Questions about intername

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

FAQPage Schema
How do I assign human-readable names to agents in an orchestration system?

Agent naming generates legible, deterministic identities for internal agent types within an orchestration system. It maps technical identifiers like 'fd-safety' to memorable names like 'Lapsed Pacifist' so logs and UIs display consistent, human-readable agent roles.

What are agent naming themes and which conventions are supported?

Naming themes are customizable conventions that define how agent identities are generated. Supported themes include cultural references, diplomatic terminology, and NATO phonetic alphabets, ensuring names fit your operational context while remaining deterministic and consistent across all dispatch surfaces.

How do I resolve an agent name programmatically for log formatting?

Programmatic name resolution uses the provided library to translate internal agent type identifiers into formatted dispatch names. When an agent like 'fd-safety' is dispatched, the library resolves it to a themed name like 'Lapsed Pacifist' for clear display across logs and UIs.

Does agent naming require any dependencies to run in my orchestration system?

No external dependencies are required. The agent naming skill operates independently using bundled scripts, references, and assets, allowing you to integrate deterministic name resolution and dispatch formatting into your orchestration system without prerequisite packages.

Why do my agent logs show unreadable identifiers instead of descriptive names?

Agent logs show unreadable identifiers when no naming layer resolves internal types to human-readable identities. Applying a deterministic naming skill maps technical identifiers to themed names like 'Lapsed Pacifist', making agent roles clear and memorable across all operational surfaces.