fkst-control-plane-operation-manual

The fkst control plane operations are automated through the NyxID CLI credential proxy, handling GitHub repo creation, .fkst directory initialization, and substrate session management. You can trigger and manage these workflows programmatically.

Bootstrapping a .fkst directory and creating a GitHub repo is handled by triggering the fkst control plane operation. This skill initializes the .fkst directory directly into an existing or newly created GitHub repository under your account or organization.

Yes, you need the NyxID CLI installed and fkst-control-plane service access to trigger fkst-substrate sessions. The CLI functions as the credential proxy required to start sessions with specific input arguments and manage the lifecycle.

Checking the status of all fkst-substrate sessions and stopping or terminating specific ones is supported. The skill manages the full session lifecycle, allowing you to monitor active sessions and terminate them based on user commands.

Triggering a fkst-substrate session fails without fkst-control-plane service access because the NyxID CLI proxy requires valid credentials to interact with the control plane and start the session with the necessary input arguments.