api SKILL.md skillB
api from mulhamna/jira-commands is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mulhamna/jira-commands/api@git:20260420.281fd3aPins git:20260420.281fd3a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mulhamna/jira-commands
- Path
plugin/skills/api/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260420.281fd3a, committed Apr 20, 2026
- First version recorded
- Apr 15, 2026
- Size
- 1,181 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Execute a raw Jira REST API call through the jirac CLI, including GET, POST, PUT, DELETE, and PATCH requests to any Jira REST endpoint.
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
Execute raw Jira REST API requests with the `jirac` CLI.
Steps:
1. Check that `jirac` is available by running `jirac --version`. If it is missing, tell the user to install it with `cargo install jira-commands`.
2. Extract from the user's request:
- HTTP method
- API path, for example `/rest/api/3/issue/PROJ-123`
- JSON body when needed
3. Run the matching command:
- `jirac api get <PATH>`
- `jirac api post <PATH> --body '<JSON>'`
- `jirac api put <PATH> --body '<JSON>'`
- `jirac api delete <PATH>`
- `jirac api patch <PATH> --body '<JSON>'`
4. Show the response clearly.
5. If the user does not know the endpoint, help map their goal to the correct Jira REST path before running anything.
Examples:
- "get server info" → `jirac api get /rest/api/3/serverInfo`
- "get issue PROJ-123" → `jirac api get /rest/api/3/issue/PROJ-123`
- "get all projects" → `jirac api get /rest/api/3/project`
- "post to /rest/api/3/issue with body {...}" → `jirac api post /rest/api/3/issue --body '{...}'`Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/api@sha256:65c25fff073f6bfeThe line at the top of this page pins the label git:20260420.281fd3a, 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_lxwacjeavdlq4mvz)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Apr 15, 2026 and Apr 20, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260420.281fd3a latest | 2026-04-20 | 281fd3a | 1,181 B | B | view · diff |
| git:20260418.e640726 | 2026-04-18 | e640726 | 1,232 B | B | view · diff |
| git:20260415.2d33454 | 2026-04-15 | 2d33454 | 1,202 B | B | view |
Audit of the latest version
- fail: Frontmatter declares a name
- pass: Frontmatter block present
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1181 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
mulhamna/jira-commands · 54 stars · license a license file GitHub does not identify · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lxwacjeavdlq4mvz GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/api GET https://markdownregistry.com/api/v1/blob/65c25fff073f6bfe75f14f4e872f59652c8b16e3de0affddc1a71cf9465e9aea
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 mulhamna/jira-commands
Every file in mulhamna/jira-commands