Multica Platform Jira
平台层 skill（占位壳）：Issue 跟踪系统（JIRA 类）的读写能力——Issue 查询、上游 Wiki 链接解析、Story 创建、流转、排期、描述回写、通知。与 Wiki 平台解耦；由产物编排 skill 调用。具体地址、项目、字段在 config.yaml 配置，不写进角色提示词。
Install
$ agentstack add skill-it235-multica-best-practices-multica-platform-jira ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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 Used
- ✓ 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-it235-multica-best-practices-multica-platform-jira) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
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 →About
Platform · JIRA（占位壳）
> 这是一个平台层占位壳。公开的 multica-best-practices 不绑定任何具体公司的内网地址与凭据。 > 团队接入自己的 Issue 系统时，只改本 skill 的 config.yaml 与 scripts/，所有上层角色与编排 skill 无需改动。
Purpose
提供「Issue 跟踪系统」类的 读 + 写 能力：
- 读：查询 Issue、从描述解析 Wiki 链接、JQL / 条件搜索。
- 写：创建 Story、状态流转、排期、描述追加（回写 Wiki 链接）、通知。
与 multica-platform-confluence（Wiki）解耦——本 skill 只负责 Issue 系统，不负责 Wiki 页面创建。
Files（建议结构）
multica-platform-jira/
├── SKILL.md
├── config.yaml
├── .env.example
└── scripts/
├── credentials.sh
├── issue.sh
└── validate.shRead（拉取 Issue / 定位上游 Wiki）
# Issue 详情（summary、description、fields）
bash scripts/issue.sh get-issue
# 从 Issue 描述 / 远程链接解析 Wiki URL 或 pageId
bash scripts/issue.sh get-wiki-url [text|json]
# 条件搜索
bash scripts/issue.sh search "" [max_results]典型链路：get-issue 读验收标准 → get-wiki-url 取 PRD pageId → multica-platform-confluence fetch-page 拉正文。
Write（产物 / 工作流写入）
# 创建 Story（PRD 编排由 multica-artifact-req-sync 调用）
bash scripts/issue.sh create-story --project --summary "..." ...
# 状态流转
bash scripts/issue.sh get-transitions
bash scripts/issue.sh transition
# 排期
bash scripts/issue.sh schedule
# 追加设计文档链接到描述（design-sync 编排调用）
bash scripts/issue.sh append-description ""
# 通知（如适用）
bash scripts/issue.sh notify Wiki 描述格式
追加块使用的标记语法取决于目标系统（Jira Wiki / Markdown / 纯文本），由团队在 scripts/ 内实现；大括号等需转义的字符按目标系统规则处理。
Workflow：Wiki 阻塞降级（PRD）
Wiki 创建失败时，multica-artifact-req-sync 可将 PRD 全文写入 Issue 描述（本 skill create-story / append-description），并标注「Wiki 降级」；恢复后再补建 Wiki 页面并更新描述链接。
与产物 skill 的关系
| 编排 skill | 调用本 skill | | --- | --- | | multica-artifact-req-sync | create-story / transition / schedule / notify / get-issue | | multica-artifact-design-sync | append-description（回写设计 Wiki 链接） |
Adapting To A New Team
改 config.yaml 中 issue.url、projects.*.fields、field_options、defaults、通知 webhook 映射。
为什么有效
Issue 系统自定义字段各团队差异大，独立 platform skill 后 Wiki / 设计发布变更不影响 Issue 脚本；读写分离后 Leader / Architect 可稳定从 Issue 定位上游 Wiki 产物。
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: it235
- Source: it235/multica-best-practices
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.