issues SKILL.md skillA
issues from devskale/skale-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add devskale/skale-skills/issues@v1.5.1Pins v1.5.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- devskale/skale-skills
- Path
skills/issues/SKILL.md- Versions recorded
- 11
- Latest version
- v1.5.1, committed Oct 16, 2026
- First version recorded
- Oct 2, 2026
- Size
- 5,199 bytes
- Repository stars
- 3
- License
- none declared
Manage the cross-machine shared issue kanban (works/<project>/issues/). Create, triage, start, review, cancel, archive, or purge work items. One synced dir per project (repo .work → ~/code/skaleshare/works/<project>/), shared across machines and repos. Use when creating, reading, picking up, triaging, cleaning up, or asking about tickets, tasks, issues, the backlog, kanban, or the board — or when handing work off / passing tasks to another machine, repo, or person. Triggers on mentions of…
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
## What this is
Every project has **one synced kanban** at the shared works root
(`~/code/skaleshare/works/<project>/issues/`), reachable from every repo in the
project via a container symlink — **`.work`** by default (`ISSUES_LINK_NAME` to
override; legacy `.handoff` links keep resolving). One markdown file per issue.
One CLI manages everything:
```text
the chain (one line, top to bottom):
<repo>/.work → ~/code/skaleshare/works/<project>/issues/{backlog,active,review,archive,cancelled}
symlink shared works root (Syncthing) one .md file per issue
```
```bash
issues --help # ← all detail functions, config keys, troubleshooting
```
`issues` is a **machine-global** command (on PATH). It resolves the project by
**walking up** from `$PWD`: at each directory level it checks for the container
link — `.work` first (configurable via `ISSUES_LINK_NAME`), then legacy names
(`.handoff`) — until it finds one. A symlink target is the shared project dir;
a real dir is a local board (`init --local`). Nothing found → run `issues init`.
Setting up a NEW project board is one command, from any repo checkout:
```bash
…Read the whole file at its exact version.
How to install
mdr add devskale/skale-skills/issues@sha256:6268cdc360945b6aThe line at the top of this page pins the label v1.5.1, 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_lyvq524f73d4qbgv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 11 versions of this file, between Oct 2, 2026 and Oct 16, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.5.1 latest | 2026-10-16 | 364e674 | 5,199 B | A | view · diff |
| v1.5.0 | 2026-10-15 | 0a2b4be | 5,199 B | A | view · diff |
| v1.4.0 | 2026-10-15 | e31b989 | 5,199 B | A | view · diff |
| v1.4.0 | 2026-10-15 | a1c2c0d | 5,189 B | A | view · diff |
| v1.3.0 | 2026-10-14 | d3da3fa | 4,955 B | A | view · diff |
| v1.3.0 | 2026-10-14 | bef3c4c | 4,736 B | A | view · diff |
| v1.2.0 | 2026-10-11 | 8f8a902 | 4,507 B | A | view · diff |
| v1.2.0 | 2026-10-08 | 10e0ff4 | 4,476 B | A | view · diff |
| v1.2.0 | 2026-10-07 | e04a3f8 | 4,145 B | A | view · diff |
| v1.2.0 | 2026-10-05 | eadc00f | 3,822 B | A | view · diff |
| v1.2.0 | 2026-10-02 | de8bace | 3,392 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 (5199 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
devskale/skale-skills · 3 stars · license none declared · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lyvq524f73d4qbgv GET https://markdownregistry.com/api/v1/resolve?ref=devskale/skale-skills/issues GET https://markdownregistry.com/api/v1/blob/6268cdc360945b6a29bfb894644f9f1d5fac33204e9f0c96c53cc3cab80e252e
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 devskale/skale-skills
Every file in devskale/skale-skills