adynato/adynato-atlassian
skills/adynato-atlassian/SKILL.md
Work with Jira, Confluence, and Atlassian Cloud links via Atlassian MCP instead of browser automation. Covers reading `atlassian.net` URLs, preferring MCP over Puppeteer for tickets and pages, summarizing issue state and comments, and falling back only when visual inspection is explicitly needed or MCP is unavailable. Use when a prompt includes Jira tickets, Confluence pages, or Atlassian links.
$ install --global
skillsauthnpx skillsauth add adynato/skills adynato-atlassianInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 17, 2026, 3:28 PM142.0s1 file scanned
SKILL.md
- name:
- adynato-atlassian
- description:
- Work with Jira, Confluence, and Atlassian Cloud links via Atlassian MCP instead of browser automation. Covers reading `atlassian.net` URLs, preferring MCP over Puppeteer for tickets and pages, summarizing issue state and comments, and falling back only when visual inspection is explicitly needed or MCP is unavailable. Use when a prompt includes Jira tickets, Confluence pages, or Atlassian links.
Atlassian Skill
Use this skill when a prompt includes Jira tickets, Confluence pages, or atlassian.net links.
Prefer Atlassian MCP for Atlassian Links
- If the user provides an
atlassian.netlink, use Atlassian MCP to read it first - Do not default to Puppeteer or browser automation just to inspect Jira or Confluence content
- Prefer MCP because it returns structured, authenticated Atlassian data instead of brittle rendered UI
- Use browser automation only if the user explicitly asks for a visual/UI check or Atlassian MCP is genuinely unavailable after confirming setup
Ticket Handling Workflow
When reading a Jira issue through Atlassian MCP, capture the parts the next decision depends on:
- Issue key and summary
- Status, assignee, priority, and type
- Description, acceptance criteria, reproduction notes, or implementation details
- Recent comments, blockers, and open questions
- Linked issues, related pages, or dependent work when relevant
Prefer MCP follow-up queries over manually clicking through browser pages.
Confluence and Related Context
- Use Atlassian MCP for Confluence page content when a page link is provided
- Follow linked Jira or Confluence context through MCP when it matters to the task
- Avoid scraping rendered HTML when structured content is available from MCP
If Atlassian MCP Is Not Set Up
- Prefer setting up Atlassian MCP in
.omp/mcp.jsonrather than using the browser as the default workaround - Follow the repo-local setup conventions in
adynato-omp-mcp - Do not act like browser automation is an equivalent replacement for authenticated MCP access
Atlassian Rovo MCP Endpoint
Use the official endpoint for new setups:
https://mcp.atlassian.com/v1/mcp
Prefer /mcp for new configurations; Atlassian is deprecating /sse.
Related Skills
adynato/adynato-coding
development
VerifiedTrustedCommunity
General coding conventions for any repository. Covers writing for the human who owns the code, clear naming, clean structure, comments that explain why, and following existing linting and formatting rules. Use when writing or modifying code in any language, especially for refactors, utilities, tests, and business logic. Prefer this as baseline guidance unless a more specific skill applies.
1SKILL.mdUpdated Apr 15, 2026
adynato/adynato-web
development
VerifiedTrustedCommunity
Web development conventions for Adynato projects. Covers image optimization with img4web, asset management, component patterns, styling, and performance best practices. Use when building or modifying web applications, adding images/assets, or creating UI components.
1SKILL.mdUpdated Mar 27, 2026
adynato/adynato-web-api
development
VerifiedTrustedCommunity
Web API development conventions for Adynato projects. Covers API routes, middleware, authentication, error handling, validation, and response formats for Next.js and Node.js backends. Use when building or modifying API endpoints, server actions, or backend logic.
1SKILL.mdUpdated Mar 27, 2026
adynato/adynato-vercel
development
VerifiedTrustedCommunity
Vercel deployment and configuration for Adynato projects. Covers environment variables, vercel.json, project linking, common errors like VERCEL_ORG_ID/VERCEL_PROJECT_ID, and CI/CD setup. Use when deploying to Vercel, configuring builds, or troubleshooting deployment issues.
1SKILL.mdUpdated Mar 27, 2026