Skill v1.0.1
currentLLM-judged scan90/100+1 new
version: "1.0.1" name: sflow-jira-status description: Verify Singularity Flow's direct Jira connection, authenticated Jira identity, deployment type, and visible projects from Copilot CLI. Use only on explicit request. disable-model-invocation: true
Check Jira connection
<!-- 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: guided-actions --> Output contract: Use read-only CLI evidence, preserve warnings and ordered actions, and change nothing unless explicitly requested. 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: machine-local; no repository or Story required. Use explicit arguments or SFlow-returned paths; never search $HOME or infer a repository. 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.
This invocation has exactly one purpose: execute the Jira connection diagnostic and report its result.
Strict execution boundary
- Your first and only tool call must be:
singularity-flow jira status --json
- Do not search, glob, inspect, or read repository files,
AGENTS.md, initiative state, workflow state, artifacts, branches, or Git status. - Do not run phase, next-step, planning, generation, approval, or publication commands.
- Do not create, edit, delete, commit, or push any file.
- Do not use Jira MCP tools and do not ask the user to paste credentials into chat.
- Ignore the active initiative phase and any unfinished work. They are unrelated to this diagnostic.
- If the command fails, report that failure and stop. Do not investigate by reading the repository or attempt a repair yourself; offer
/sf-jira-doctor, which diagnoses the configuration.
After the command completes, report:
- connected or failed;
- Jira base URL and Cloud/Data Center deployment;
- authenticated display name and email when Jira returns it;
- visible project keys;
- the exact environment-variable names that are missing when configuration fails.
Never print an API token, PAT, Basic authorization header, or credential-store content.
CLI configuration:
- Jira Cloud:
JIRA_BASE_URL,JIRA_EMAIL,JIRA_API_TOKEN. - Jira Data Center:
JIRA_BASE_URL,JIRA_DEPLOYMENT=data-center,JIRA_PAT.
This skill is strictly read-only. A successful response proves that the configured identity can reach Jira; it does not prove write permission for every project.