YAAIF

Plugin yaaif-platform in yaaif/codex-plugin. Commands read from the repo's manifest — 21 days ago.

Skills (22)

• yaaif-auth

  Authenticate to YAA\F from Codex, select platform profile and tenant, and verify session before skills/MCP/ambient mutations. Use for YAA\F login, platform switch (hosted/local), tenant selection, whoami, ensure_session, or configure_check.

• yaaif-create-ambient

  Design and install YAA\F ambient workflows via the Codex MCP bridge for customer/partner tenants (no monorepo required).

• yaaif-create-file-workflow

  Create a custom file workflow on YAA\F via the Codex MCP bridge: an ambient workflow that runs when an uploaded file finishes extraction (file.ready / file.failed / file.review_decided), reads the extracted text or tables, runs your own tool steps and replies to where the file came from (chat, Teams

• yaaif-create-mcp

  Scaffold a YAA\F MCP server. HTTP servers deploy via mcp-deployments (docker_compose or kubernetes_gitops). Command/stdio servers publish to the desktop Package Registry from a local codebase. Mint/bind scoped API keys when the MCP calls platform APIs. For customer/partner workspaces without monorep

• yaaif-create-skill

  Author or maintain a YAA\F SKILL.md pack and load it into the tenant catalog via the yaaif Codex MCP bridge. Use when Admin UI Open in Codex / Create in Codex selected a skill_id, or when creating a new skill. Prefers platform local skill lifecycle tools when available.

• yaaif-doctor

  Run YAA\F Codex connectivity diagnostics (platform profile, OIDC, TLS/mTLS, auth/tenant, catalog ping, local tools API). Use when login fails, local Traefik TLS breaks, or before plan/create work.

• yaaif-governance

  Translate tenant business requirements into guardrail and harness settings, investigate policy-related failures, and apply explicitly confirmed governance proposals within the user's permissions.

• yaaif-kg-enhance

  Enhance the Context Store knowledge graph by discovering missing relationships between existing catalog nodes, proposing them for approval, and applying approved batches. Use when the user asks to enhance, enrich, or find missing links in the Entity Graph. Not for skill-authoring plans (use yaaif-kg

• yaaif-kg-skill-plan

  Propose an ordered skill-authoring plan grounded in the Context Store knowledge graph and hand chosen steps to skill authoring. Use when the user asks which skills to build from the catalog or wants a plan from the Entity Graph. Not for applying graph enrichments (use yaaif-kg-enhance).

• yaaif-login

  Select YAA\F platform profile, authenticate, and select a tenant

• yaaif-new-file-workflow

  Create a custom file extraction workflow on YAA\F (runs when an upload finishes extraction)

• yaaif-new-mcp

  Scaffold, deploy, and register MCP tools on YAA\F

• yaaif-new-skill

  Create a YAA\F skill and load it into the tenant catalog

• yaaif-new-workflow

  Create an ambient workflow on YAA\F and test-trigger it

• yaaif-ops-support

  Operations support for LLM sessions, ambient workflow runs, and desktop executions: correlate IDs, analyze failures, pull telemetry, and optionally write a confirmed OpsDiagnosisRecord back to YAAIF. Never pause/stop/approve/retry.

• yaaif-ops

  Read-only ops support — correlate and analyze session/ambient/desktop failures

• yaaif-plan-usecase

  Understand a business use case, propose a YAA\F architecture plan (chat skills, ambient workflows, desktop skills, agents, MCP tools, mappings), wait for approval, then execute via yaaif-create-* skills and bridge tools. Supports interview mode, dry-run, plan verify, approval strategies, and desktop

• yaaif-plan

  Plan a YAA\F use case (chat + ambient + desktop), then execute after approval

• yaaif-platform-tools

  Discover and correctly use YAA\F agent-service built-in local tools (skill lifecycle, files, ambient trigger, session/workflow state) when authoring skills or exercising platform functions from Codex.

• yaaif-requirements

  Write a customer requirement analysis, functional specification, technical specification, and an estimate with timeline for a YAA\F Scenario, then store them as downloadable file-registry documents. Use when the user asks for a requirement analysis, FS, TS, functional spec, technical spec, estimate,

• yaaif-scenario

  Create or maintain a YAA\F Scenario (Agent Spec): segments, architecture slots, bindings, workflow_design, coverage, and bidirectional catalog sync. Use when the user asks to create a spec/scenario, keep it in sync with live objects, sync objects from the spec, or Admin UI Open in Codex selected a s

• yaaif-sync-scenario

  Apply a YAA\F Scenario onto catalog objects, or explicitly adopt live catalog drift

MCP servers (1)

• yaaif

  runs: npx -y @yaaif/[email protected] --client codex

Similar plugins