aevatar-feasibility-advisorlisted

Use before building when a user asks whether Aevatar can achieve a goal, what prerequisites it has, or why it is unavailable. Triggers include bots and third-party APIs, inbound channels, external HTTP triggers, schedules, service exposure, Agent Profiles and tool ceilings, and bounded managed or private-host codex_exec work. It distinguishes outbound connectors from inbound channels and separates not connected, host-gated, not deployed, and genuinely unsupported outcomes. It chooses managed_sandbox versus private_ssh without promising repository, model, credential, runtime, or deployment capabilities the caller does not control, then routes feasible work to the owning Aevatar skill.
ChronoAIProject/NyxID · ★ 36 · AI & Automation · score 78

Install: claude install-skill ChronoAIProject/NyxID

# Aevatar feasibility advisor Before you (or the user) commit to building something on Aevatar, answer three questions **honestly**: *Is it possible? What must be in place first? If not, why — and what's the alternative?* This skill exists so you negotiate scope up front instead of discovering a hard blocker halfway through. It only **advises** — once a plan is feasible, hand off to `aevatar-workflow-authoring` → `aevatar-team-builder` → `aevatar-service-publisher` → `aevatar-scheduler`, or to `aevatar-agent-profile-management` for the Agent Profile surface (see `aevatar-platform-map`). For `codex_exec`, choose the target here, then hand setup or repair to `aevatar-codex-exec-node-setup`, require the public `aevatar-codex-exec-workflow-sample` proof, and only then author the real workflow. ## Three different reasons a thing can be unavailable — never blur them They have different owners and different fixes. Collapsing them into "it's host-gated" is the most common wrong answer here. | Reason | What it looks like | Who fixes it | |---|---|---| | **Not connected** | The connector is in `/api/v1/catalog` but missing from authoritative `/api/v1/keys` | **The user**, self-serve | | **Host-gated** | The capability is deployed and works, but a host policy governs one aspect (NyxID external exposure; Agent Profile *rollout admission*) | **The host** — not you, not the user | | **Not deployed** | The capability's whole API surface is absent from the running build | **The host**, b