interactive-role-setup

Maps abstract role profiles to available AI models and persists the mapping to roles.toml.

Updated Jul 30, 2026
One-click install
npx skills add https://github.com/primax79/ai-architect-executor --skill interactive-role-setup-primax79
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interactive-role-setup
Source: https://github.com/primax79/ai-architect-executor/tree/main/plugins/shared/skills/interactive-role-setup
Command: npx skills add https://github.com/primax79/ai-architect-executor --skill interactive-role-setup-primax79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Multi-agent AI kits need model assignments per role, but hardcoding model names into skills creates vendor lock-in and silently breaks when hosts, plans, or allowlists change. This Skill discovers which models are actually reachable, ranks them into capability tiers with recorded evidence, and produces a verified role-to-model mapping. ## Core Features & Use Cases - Guided discovery and ranking: Enumerates reachable models per host (Kilo, Claude Code, others), ranks them into tiers using recorded evidence (host metadata, provider tier naming, model self-knowledge, or operator input), and proposes a four-profile mapping with justifications. - Persistent configuration: Writes the confirmed mapping to ~/.config/ai-architect-executor/roles.toml with host, model, effort, basis, and last_verified fields, without ever writing another tool's own config files. - Deterministic validation: Ships scripts/validate_roles.py to check that every skill declares a valid profile, no skill declares a model, all four roles are populated, and effort/model combinations are valid. - Use Case: After installing the Architect/Executor kit on a new machine, run the guided flow to detect available models, confirm a mapping of deep-reasoning to a high tier and bulk-execution to a cheap fast tier, then re-verify 24 hours later when the organization allowlist changes. ## Quick Start Ask the AI to run the interactive role setup to discover available models and configure the four role profiles in roles.toml.

Frequently Asked Questions about interactive-role-setup

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

FAQPage Schema
How do I configure which AI model handles each role in a multi-agent setup?▼

Run the guided flow, which discovers reachable models per host, ranks them into capability tiers with recorded evidence, and proposes a mapping for the four role profiles. After you confirm each row, it writes the result to ~/.config/ai-architect-executor/roles.toml.

How do I validate a roles.toml role mapping file?▼

Run scripts/validate_roles.py with --plugin-dir for each plugin and optionally --roles-file pointing to your roles.toml. It checks that every skill declares a valid profile, no skill declares a model, all four roles are populated, and effort values are valid for the pinned model.

Does this skill write Claude Code or Kilo configuration files?▼

No, it never writes another tool's configuration such as settings.json or agent frontmatter. It only writes its own roles.toml and hands off intent as a natural-language request that the operator applies through each host's own configuration flow.

Why does my configured effort level silently not apply to a model?▼

Some models do not support certain effort levels, and hosts silently fall back to the highest supported level. The validator flags combinations like effort xhigh pinned on models known not to support it, so the regression becomes visible instead of silent.

How often should role-to-model mappings be re-verified?▼

The skill uses a 24-hour cadence tracked via the last_verified field in each roles.toml entry. Stale entries trigger read-only re-verification, and a fresh discovery pass surfaces new models or changed allowlists without silently rewriting the mapping.