Multica Platform Jira
Platform-layer skill (placeholder shell): read/write capability for Issue-tracking systems (JIRA-class) — Issue query, upstream-Wiki-link parsing, Story creation, transition, scheduling, description write-back, notification. Decoupled from the Wiki platform; called by artifact-orchestration skills. Concrete URLs / projects / fields live in config.yaml, never in role prompts.
Install
npx skills add it235/multica-best-practices --skill multica-platform-jiragit clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/en_US/skills/platform/multica-platform-jira ~/.claude/skills/multica-platform-jiraPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Platform · JIRA (placeholder shell)
> This is a **platform-layer placeholder shell**. The public multica-best-practices binds to no specific company's internal URLs or credentials.
> To onboard your own Issue system, only edit this skill's `config.yaml` and `scripts/`; all upstream roles and orchestration skills stay untouched.
## Purpose
Provide **read + write** capability for "Issue-tracking system" class platforms:
- **Read**: query Issues, parse Wiki links from descriptions, JQL / conditional search.
- **Write**: create Stories, transition states, schedule, append to description (write back Wiki links), notify.
Decoupled from `multica-platform-confluence` (Wiki); this skill only handles the Issue system, not Wiki page creation.
## Files (suggested structure)
```text
multica-platform-jira/
├── SKILL.md
├── config.yaml
├── .env.example
└── scripts/
├── credentials.sh
├── issue.sh
└── validate.sh
```
## Read (pull Issue / locate upstream Wiki)
```bash
bash scripts/issue.sh get-issue <ISSUE-KEY>
bash scripts/issue.sh get-wiki-url <ISSUE-KEY> [text|json]
bash scripts/issue.sh search "<JQL>" [max_results]
```
**Typical chain**: `get-issue` reads acceptance criteria → `get-wiki-url` gets PRD pageId → `multica-platform-confluence` `fetch-page` pulls body.
## Write (artifact / workflow write-back)Details
- Skill name
multica-platform-jira- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/platform/multica-platform-jira/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
FAQ
What does the Multica Platform Jira skill do?
Platform-layer skill (placeholder shell): read/write capability for Issue-tracking systems (JIRA-class) — Issue query, upstream-Wiki-link parsing, Story creation, transition, scheduling, description write-back, notification. Decoupled from the Wiki platform; called by artifact-orchestration skills. Concrete URLs / projects / fields live in config.yaml, never in role prompts.
How do I install the Multica Platform Jira skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-platform-jira. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multica Platform Jira popular?
It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.
Related skills
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Multica Artifact Architect
279it235/multica-best-practices
架构师产物薄编排:校验设计草稿规范,落地时只调 multica-platform-confluence + multica-platform-jira。用于 @Architect 发布设计文档。
Multica Artifact Backend
279it235/multica-best-practices
Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.
Multica Platform Jira
279it235/multica-best-practices
JIRA 读写:Issue 查询、Confluence 链接解析、Story 创建、流转、排期、描述回写、钉钉。平台 skill,与 Confluence 解耦。跨平台优先 jira_cli.py。
Slm Compress
278qualixar/superlocalmemory
Compress large text, tool output, or transcripts to reduce context-window usage while keeping the full 1M window intact — call slm_compress(content, mode, reversible, ttl_seconds) to shrink content; if the result is lossy a ccr_id is returned so you can call slm_retrieve(ccr_id) later to recover the exact original; always fail-open (ok:false → continue with the original).
To Article
192sugarforever/boring-video-studio
Use when an approved content topic, research bundle, and evidence need to become a complete platform-independent article before video beats or publication adaptation.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.