メニュー
Read or verify Atlassian Jira and Confluence items through mcporter. Use for bankx.atlassian.net links, Jira issue keys, Confluence pages, Jira ticket validation, JQL/CQL searches, or when another Jira MCP wrapper fails.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run iterative agent evaluation and improvement loops (judge, improve, scenarios, playbooks) via pi-autocontext or autoctx CLI. Use when improving repeatable agent workflows (review rubrics, skill quality, scenario-based feedback), checking run status, or accumulating knowledge—not for one-off code edits or repo pattern drift (use continuity) or single PR review (use zereight-review).
Pi-native evaluate→improve→persist harness. Provides a systematic loop for generating candidates, judging them against rubrics, and accumulating knowledge as playbooks. Use for iterative output improvement, not for one-off edits (use continuity) or single PR review (use zereight-review).
Audit agent skills — token cost, duplicates, outdated plugin versions, unused skills, and overly long descriptions. Use when trimming skill prompt budget, finding duplicate or unused skills, auditing plugin versions, or deciding which skills to remove.
Diagnose why a skill is missing from Pi /skill or Cursor lists. Use when a skill exists on disk but does not appear, Pi shows only project or extension skills, or after adding a repo skill under .agents/skills/.
Comprehensive code review skill for practical PR feedback. Use for feature, bugfix, and refactor reviews. Prioritizes correctness, edge cases, logic invariants, fallback-chain safety, async state transitions, architecture analysis, OWASP security, and clear actionable feedback.
Skill map and inventory workflow. Use for scanning installed skills, skill overview, 스킬 목록, skill map.
| name | atlassian-with-mcporter |
| description | Read or verify Atlassian Jira and Confluence items through mcporter. Use for bankx.atlassian.net links, Jira issue keys, Confluence pages, Jira ticket validation, JQL/CQL searches, or when another Jira MCP wrapper fails. |
Use mcporter first for Atlassian work. Do not conclude that an issue/page is missing from a wrapper failure alone.
Inspect the server before fallback:
/Users/tao.exe/.nvm/versions/node/v22.22.2/bin/mcporter list atlassian --schema --json
If it fails with listen EPERM, rerun outside the sandbox with approval. The Atlassian MCP proxy may need local port binding.
Get accessible resources:
/Users/tao.exe/.nvm/versions/node/v22.22.2/bin/mcporter call atlassian.getAccessibleAtlassianResources
For Jira issues, use the Atlassian MCP JQL tool:
/Users/tao.exe/.nvm/versions/node/v22.22.2/bin/mcporter call atlassian.searchJiraIssuesUsingJql \
cloudId=bankx.atlassian.net \
jql='key = ISSUE-123' \
maxResults=10 \
fields='["summary","description","status","issuetype","priority","created","updated","project","assignee","reporter"]' \
responseContentFormat=markdown
If search returns an ARI or lightweight result, call atlassian.fetch for details.
mcp__Confluence_wiki__.execute_jql_search alone; it may use obsolete Jira APIs.https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/...
over only:
https://site.atlassian.net/rest/api/3/...