Github issues
Skill Martin-Hausleitner/martins-awesome-skills/skills/github/github-issues
Martin's Awesome Skills: public-safe Hermes and OpenClaw agent skills with Telegram approval workflows
npx -y skills add Martin-Hausleitner/martins-awesome-skills --skill github-issuesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when triaging, creating, labeling, searching, or closing GitHub issues
SKILL.md
1.0 KB, as published. Nobody here has run it
GitHub Issues
Overview
Use issues as lightweight, searchable work records. Keep them specific enough that another agent or human can act without recovering hidden context.
Common Commands
gh issue list --limit 20
gh issue view ISSUE_NUMBER --comments
gh issue create --title "Short title" --body "Context, tasks, acceptance criteria"
gh issue edit ISSUE_NUMBER --add-label documentation
gh issue close ISSUE_NUMBER --comment "Resolved by PR #123"
Triage Shape
- Problem: what is broken or missing.
- Evidence: logs, screenshots, commands, or reproduction steps.
- Scope: files, skills, docs, or workflows likely involved.
- Done when: concrete acceptance criteria.
Safety
- Do not paste private chat logs, tokens, local account data, or personal identifiers into public issues.
- Summarize sensitive evidence instead of copying it verbatim.