archive SKILL.md skillB
archive 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/archive@git:20260521.f34ad5ePins git:20260521.f34ad5e 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/archive/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260521.f34ad5e, committed May 21, 2026
- Size
- 1,752 bytes
- Repository stars
- 54
- License
- a license file GitHub does not identify
Archive Jira issues matching a JQL query with jirac.
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
Archive all issues matching a JQL query using `jirac`. Archive is destructive — issues are hidden from regular search and become read-only. Steps: 1. Check that `jirac` is available by running `jirac --version`. If missing, tell the user to install it (`cargo install jira-commands`). 2. Extract or build a JQL query from the user's request that scopes the archive cleanly (project, status, age, resolution). 3. Dry-run the JQL via `jirac issue list --jql '<JQL>'` so the user can see the affected set before archiving. 4. Confirm intent explicitly — archive is irreversible without admin assistance. 5. Run `jirac issue archive --jql '<JQL>'` (omit `--force` to keep the confirmation prompt; add `--force` only after explicit confirmation in agent flows). 6. Report how many issues were archived. Notes: - Archive requires sufficient Jira permissions (typically Project Administrator). - Archived issues remain in the database but are hidden from boards, dashboards, and standard JQL searches by default. - Prefer scoping by `project`, `resolution`, `updated`, and `status` — broad queries can archive far more than expected. …
Read the whole file at its exact version.
How to install
mdr add mulhamna/jira-commands/archive@sha256:c09f3e550277fcb6The line at the top of this page pins the label git:20260521.f34ad5e, 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_enpefhn5vpe7nsky)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 21, 2026.
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 (1752 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_enpefhn5vpe7nsky GET https://markdownregistry.com/api/v1/resolve?ref=mulhamna/jira-commands/archive GET https://markdownregistry.com/api/v1/blob/c09f3e550277fcb63cd2330e2bfc43d71062d4b7d4fec123c51f4b88edfca67d
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