ashokraj2011

sflow-help

Answer questions about Singularity Flow and its workflow.

ashokraj2011 0 Updated 2w ago
GitHub

Install

npx skillscat add ashokraj2011/singularityflow/sflow-help

Install via the SkillsCat registry.

SKILL.md

Load help or explain how to proceed

Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. For suggested actions, pair Shell with the returned Copilot command; honor commandGuidance. If absent, say "Copilot: no verified equivalent"; never invent a slash command.

Boundary: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository.

Packaged documentation can still be served when no workspace is registered; do not search the
filesystem for a repository in that case.

  1. With no argument, run singularity-flow explain --json and show the topic index.
  2. For a topic ID or an ordinary product question, run singularity-flow explain "$ARGUMENTS" --json. Relay only data.served.text, its citation/provenance, warnings, and related actions. Never answer product behavior from model memory.
  3. The returned data.helpIntent is one of concept, procedure, diagnose, compare, command-discovery, or recover. Use it only to format the answer; it is not permission to execute a command.
  4. When resolution is ambiguous, render the returned topic choices. When it is not found, say that the packaged documentation has no grounded answer and offer its nearest topics. Never choose the closest topic yourself.
  5. For a question about why active work cannot advance, run singularity-flow home --json --request "$ARGUMENTS". For repository context, first run singularity-flow workspace current --json; only when it returns repositoryPath, use that exact cwd for explain --here.
  6. For an explicit Work ID or phase rail, first resolve that repository as above, then run
    singularity-flow guide <WORK-ID> there. State the workflow, source, phases, artifacts, agents,
    authorities, threshold, and exact recommended /sf-* action.
  7. Preserve the documentation boundary, topic version, source commit, content digest, and any state revision. Treat HELP.md as the canonical product manual, but do not search it when a packaged cited topic answered the question.
  8. Do not generate, submit, approve, reject, upload, commit, push, or execute a displayed command.