AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

File Ticket

skill-cloudbees-oss-devops-agent-kit-file-ticket · by cloudbees-oss

>

No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-cloudbees-oss-devops-agent-kit-file-ticket

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-cloudbees-oss-devops-agent-kit-file-ticket)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of File Ticket? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

File Jira Ticket

Parse arguments to determine issue type and description.

  1. If the agent has recent triage/scan context, use it. Otherwise, ask

which component and issue to reference.

  1. Build the Jira ticket:

For build failures:

  • Summary: "[Build Failure] {component} — {rootcausesummary}"
  • Description: Root cause analysis, failing step, log excerpt (if available),

fix recommendation, link to run

  • Labels: build-failure, devops-agent
  • Priority: High if blocking all builds, Medium if intermittent

For security findings:

  • Summary: "[Security] {component} — {findingtype} in {filepath}"
  • Description: Finding details (severity, scanner, file, line), SLA due date,

remediation steps, affected environments

  • Labels: security, devops-agent
  • Priority: based on severity (Critical/High = High, Medium = Medium, Low = Low)

For improvements:

  • Summary: "[Improvement] {description}"
  • Description: Current state, proposed change, expected impact,

implementation steps

  • Labels: improvement, devops-agent
  • Priority: Medium (default)
  1. Show the ticket preview and ask for confirmation
  2. Create via mcp__mcp-atlassian__jira_create_issue
  3. Confirm with ticket URL
  4. Offer to:
  • Post the ticket link to Slack
  • Add the ticket as a GitHub issue comment on the relevant PR

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.