Skill
arsenal
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed Arsenal skills.
@mirkobozzettoView SkillDevelopment
Skill
/issue
Create, update or resume a GitHub issue as durable resolution memory when requested.
Install
$ npx -y skills add mirkobozzetto/arsenal --skill issue --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/issue
Context preview
The summary Claude sees to decide when to auto-load this skill.
Create, update or resume a GitHub issue as durable resolution memory when requested.
SKILL.md
issue.SKILL.mdname: issue
description: Create, update or resume a GitHub issue as durable resolution memory when requested.
argument-hint: "[create|update|resume|list] [#N | problem]"
Issue memory
Use the authenticated gh CLI. Read the specific issue and comments before updating it; do not query unrelated issues. Capture the problem, evidence, attempts, remaining action and verification so the issue can be resumed cold. Use references/issue-template.md when creating one.
Confirm before creating or closing an issue. Append requested progress as comments instead of overwriting the body. Preserve the existing claude-memory label and Pickup Directive contract. No code changes, commits or agents.
Resume reconstructs the current state from the issue, not stale memory. A solved issue does not trigger another diagnosis. List returns concise open items and stops. If the controlled shell has no external networking, report that authorization/capability boundary instead of claiming the GitHub action happened or attempting an execution escape.
Arsenal handoff
Return issue context and remaining actions to Arsenal when it called this skill. A request to fix the issue can continue through Arsenal's implementation route; reading or resuming context alone does not authorize code changes. Issue creation and closure retain their confirmation gates.
Execution policy
Work solo. Ask before any subagent or reviewer, even in auto mode. Explain the independent scope and expected benefit first. No hidden advisor, nested delegation, model retuning, repeated successful checks, or progress spam. Use existing context before asking questions. Stop when the requested result is delivered. User stops and scope changes override pending steps.
Read more
name: issue description: Create, update or resume a GitHub issue as durable resolution memory when requested. argument-hint: "[create|update|resume|list] [#N | problem]"
Issue memory
Use the authenticated gh CLI. Read the specific issue and comments before updating it; do not query unrelated issues. Capture the problem, evidence, attempts, remaining action and verification so the issue can be resumed cold. Use references/issue-template.md when creating one.
Confirm before creating or closing an issue. Append requested progress as comments instead of overwriting the body. Preserve the existing claude-memory label and Pickup Directive contract. No code changes, commits or agents.
Resume reconstructs the current state from the issue, not stale memory. A solved issue does not trigger another diagnosis. List returns concise open items and stops. If the controlled shell has no external networking, report that authorization/capability boundary instead of claiming the GitHub action happened or attempting an execution escape.
Arsenal handoff
Return issue context and remaining actions to Arsenal when it called this skill. A request to fix the issue can continue through Arsenal's implementation route; reading or resuming context alone does not authorize code changes. Issue creation and closure retain their confirmation gates.
Execution policy
Work solo. Ask before any subagent or reviewer, even in auto mode. Explain the independent scope and expected benefit first. No hidden advisor, nested delegation, model retuning, repeated successful checks, or progress spam. Use existing context before asking questions. Stop when the requested result is delivered. User stops and scope changes override pending steps.
Ships witharsenal
Portable workflow skills and controlled runtime for Pi, OMP, Codex, and Claude Code
Get the whole plugin
Stats
15
Stars
1
Forks
Active
Maintenance
Python
Language
MIT
License
9d ago
Last commit
3mo ago
Created
Repo: mirkobozzetto/arsenal
Other skills on arsenal.
@mirkobozzettoView SkillSkill
brief
Write a product brief and its task list when the user requests a product specification. Never implement it.
@mirkobozzettoView SkillSkill
next
Report unfinished work and the exact next action from existing artifact states. Never resume or implement automatically.
@mirkobozzettoView SkillSkill
propose
Design a concrete technical proposal with evidence and tradeoffs when a decision needs design. No implementation or automatic reviewer.
@mirkobozzettoView SkillSkill
ship
Implement a clear request or an approved brief/proposal. Work solo, make the smallest sufficient change, verify the changed behavior, and stop. Ask before any…
@mirkobozzettoView SkillSkill
trace
Read or explicitly record project progress using the existing deterministic trace script.
@mirkobozzettoView Skill