flowstate-cli Package Skill

Package: @epicdm/flowstate-cli Repository: epic-flowstate-community Path: packages/flowstate-cli Version: 1.1.11

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

FlowState CLI Agent Control Plane

Use this skill for CLI surfaces that control agents, agent credentials, autonomous execution, and runner tasks.

Source Map

• src/cli-commands/agent/*: agent list/provision/start/stop/status/model/budget/vault/runtime commands.
• src/cli-commands/agent-key/*: device/service key provisioning, rotation, vault insertion, and listing.
• src/cli-commands/runner/*: in-container runner control API client and commands.
• src/cli-agent.ts: flowstate-agent binary for autonomous spec workflow execution.
• src/core/ObsSessionContext.ts: session context used by agent execution and observability.
• src/types/agent-secrets.ts, src/lib/host-device-vault.ts, src/lib/developer-key-store.ts: secret and key support.

Workflow Map

• Agent lifecycle and settings: flowstate agent ....
• Agent key material: flowstate agent-key ....
• Runner HTTP control API: flowstate runner ....
• Legacy/autonomous spec execution binary: flowstate-agent run/status/init.
• Observability context: set through ObsSessionContext when execution should be traceable.

Guardrails

• Do not log bearer tokens, device keys, service keys, wallet secrets, or vault payloads.
• Runner commands talk to RUNNER_CONTROL_URL and RUNNER_CONTROL_TOKEN; keep those names stable unless all consumers are updated.
• flowstate-agent currently imports @epicdm/flowstate-agents/agent/* without that package being declared in flowstate-cli dependencies. Verify runtime packaging before claiming the binary works after publish.
• Keep agent identity, org id, user id, and workspace context explicit. Do not silently fall back across tenants.
• For autonomous agent workflows, clear ObsSessionContext in finally paths.

Verification

yarn workspace @epicdm/flowstate-cli test -- agent runner
yarn workspace @epicdm/flowstate-cli typecheck
yarn workspace @epicdm/flowstate-cli build
node packages/flowstate-cli/dist/cli.js agent --help
node packages/flowstate-cli/dist/cli.js runner --help
node packages/flowstate-cli/dist/cli-agent.js --help

Package Skill Inventory

Skill Inventory: @epicdm/flowstate-cli

Package path: packages/flowstate-cli.

Skillset

Composition Notes

• Use flowstate-cli-command-reference-maintenance after any command registration or option changes.
• Use flowstate-cli-cloud-and-dojo together with flowstate-cli-operator-workflows when authenticated profiles are involved.
• Use flowstate-cli-local-platform-ops for self-hosted/local services before using cloud-only commands.
• Use flowstate-cli-agent-control-plane before touching flowstate-agent, runner control, or agent secret provisioning.

Publication Readiness

Status: drafted, pending verification.

Before Dojo publication, rebuild package Dojo artifacts from this reviewed skillset and verify runtime help from built binaries.

Review Gate

Package Skill Review: @epicdm/flowstate-cli

Package path: packages/flowstate-cli.

Review Result

Status: drafted, source-backed, verified with existing package failures, pending publication.

The skillset is workflow-shaped around operator CLI use, agent/runner control, cloud/Dojo APIs, plugin/marketplace lifecycle, local platform operations, and command reference maintenance.

Checks

• Source review: completed from package metadata, binaries, programmatic exports, FlowStateCLI command registration, cloud/dojo/runner command groups, cli-agent, generated API type layout, and generated artifact drift.
• Skill inventory: completed.
• Skill files: completed.
• Verification: completed.
• Generated Dojo replacement: pending.
• Cloud Dojo publication: pending.

Verification Commands

Commands run:

yarn workspace @epicdm/flowstate-cli typecheck
yarn workspace @epicdm/flowstate-cli test
yarn workspace @epicdm/flowstate-cli build
yarn workspace @epicdm/flowstate-cli lint
node packages/flowstate-cli/dist/cli.js --help
node packages/flowstate-cli/dist/cli-agent.js --help
node packages/flowstate-cli/dist/cli.js dojo --help
node packages/flowstate-cli/dist/cli.js runner --help
yarn workspace @epicdm/flowstate-cli test src/cli/instance/__tests__/ComposeGenerator.test.ts --runInBand

Results:

• Skill file ASCII scan passed.
• Typecheck passed.
• Build passed; tsup reported existing unused zipSync import warnings in generated marketplace-lib outputs.
• Lint passed with 52 warnings.
• Built flowstate --help, flowstate dojo --help, and flowstate runner --help passed.
• Full test run failed and then hung after emitting failures; it was stopped rather than left running.
• Focused rerun confirmed src/cli/instance/__tests__/ComposeGenerator.test.ts has 1 failing assertion: core tier expects no flowstate-default-agent-net, but rendered YAML includes mcp-http attached to flowstate-default-agent-net.
• Built flowstate-agent --help failed with MODULE_NOT_FOUND for @epicdm/flowstate-agents/agent/autonomous-agent, matching the package review warning about an undeclared runtime dependency.
• docs:cli-reference and check:spec-drift were not run in this skill-authoring pass to avoid mutating generated docs/types outside package-local skills.

Publication Gate

Do not publish existing .flowstate/dojo artifacts until they are rebuilt from reviewed package skills.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/flowstate-cli/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.