ashokraj2011/singularityflow/sflow-jira-status

Claude Code and agent skill by ashokraj2011/singularityflow

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Verify Singularity Flow's direct Jira connection, authenticated Jira identity, deployment type, and visible projects from Copilot CLI. Use only on explicit request.

Install

npx vskill@latest install ashokraj2011/singularityflow/sflow-jira-status

SKILL.md

The same SKILL.md was published earlier as ashokraj2011/singularityflow/sflow-jira-status.

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. This skill is already loaded; never call the skill tool for it. Unless paused, continue below in this turn.

<!-- 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. Never show a person a hash, digest or commit SHA: name the step, its generation, its files. Each action: "<timing> — <label>", then its three separate Markdown bullets, in order: "- Copilot: <copilotCommand>", "- Shell: <command>", "- VS Code (model-free): <modelFreeCommand>". Keep returned routes exact; never apart from their label, on one line or in a table. Missing Copilot: "no verified equivalent"; missing Shell or model-free: "not available for this action". Never invent routes or make more calls for formatting. <!-- 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.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/ashokraj2011/singularityflow/sflow-jira-status/badge)](https://verified-skill.com/skills/ashokraj2011/singularityflow/sflow-jira-status)

Something wrong with this skill or its page? Tell us.