multica-platform-jira SKILL.md skillA
multica-platform-jira from it235/multica-best-practices is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add it235/multica-best-practices/multica-platform-jira@git:20260910.699a593Pins git:20260910.699a593 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/platform/multica-platform-jira/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260910.699a593, committed Sep 10, 2026
- First version recorded
- Sep 10, 2026
- Size
- 3,535 bytes
- Repository stars
- 237
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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]
```
…Read the whole file at its exact version.
How to install
mdr add it235/multica-best-practices/multica-platform-jira@sha256:bd6236cd899c5c6eThe line at the top of this page pins the label git:20260910.699a593, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_jnns342ttx7f6rku)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 10, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.699a593 latest | 2026-09-10 | 699a593 | 3,535 B | A | view · diff |
| git:20260910.8db057c | 2026-09-10 | 8db057c | 3,533 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3535 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
it235/multica-best-practices · 237 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jnns342ttx7f6rku GET https://markdownregistry.com/api/v1/resolve?ref=it235/multica-best-practices/multica-platform-jira GET https://markdownregistry.com/api/v1/blob/bd6236cd899c5c6e3cf2374b6c04f683b3a8999264b107aa8ab18beff2004a35
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from it235/multica-best-practices
Every file in it235/multica-best-practices