sflow-sgos

Run an exact Singularity Governed Operating System command without changing its CLI family or bypassing its authority and confirmation boundaries.

SKILL.md

GitHub

Governed SGOS command relay

<!-- sflow-copilot-pause -->

Before any boundary lookup or SFlow action, run singularity-flow pause status --json and follow its data.agentInstruction. If data.paused, answer as native Copilot, only offer /sf-pause off and never resume implicitly.

<!-- sflow-output-contract: explicit-selection -->

Output contract: Collect every required choice explicitly; never infer or preselect; preserve errors, artifacts, and next actions. Summarize artifacts with verified Markdown-preview links; never paste document bodies, code or diffs into Copilot. For code, list touched paths and observed added/deleted/created line counts; unavailable stays unavailable. Use existing evidence, not extra calls solely for display. Summaries, links and opened previews are not human review or approval. For every next action, honor returned commandGuidance in order: Copilot, Shell, VS Code (model-free) using modelFreeCommand; if absent, say "not available for this action". Missing Copilot: "no verified equivalent". Never invent routes.

<!-- sflow-execution-boundary -->

Boundary: no Story required; cwd=opened Git root or verified repositoryPath from singularity-flow workspace current --json; refuse if neither resolves; never search $HOME/parents. Use exact CLI-returned paths. repositoryPath is command cwd, not a prefix for absolute file paths. Never rebase paths or strip .git/worktrees. Issued private/external files are exact exceptions to repository confinement, not wider read/write permission; writes still need authorization. Resolve relative paths only against their declared base. On failure, preserve the path and error; never search or recreate it.

Relay one explicitly requested SGOS command to the same CLI family.

  1. Require one listed family and an explicit subcommand. Never infer either value.
  2. Run singularity-flow $ARGUMENTS from the resolved repository and preserve the complete result. Never prepend workflow or translate it into singularity-flow workflow ....
  3. Preserve every CLI model, trust, identity, revision, exact-hash, confirmation, and authority check. Never invent a file, ID, choice, approval, credential, digest, or human response.
  4. Show a returned preview, plan, confirmation digest, or next command with its effects and stop. Confirm only after the contributor explicitly accepts the exact result in a later turn.
  5. Never run a returned next command automatically. Execute only the explicitly requested operation after all CLI guards pass.
  6. Use /sf-sgos-create for singularity-flow intent workflow-guide and singularity-flow intent workflow-create; /sf-learn for learning; and /sf-workflows only for the separate singularity-flow workflow ... catalog.

Report the exact singularity-flow $ARGUMENTS action on all three surfaces per the Output contract; preserve its operands.