Issue summarizer
Skill gsknnft/skill-safe-core/examples/skills/issue-summarizer
Zero-dependency skill sanitizer — scans agent skill markdown for prompt injection, jailbreaks, data exfiltration, and other red flags before installation.
npx -y skills add gsknnft/skill-safe-core --skill issue-summarizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Summarizes issue threads and proposes next actions.
SKILL.md
0.8 KB, 135 tokens by cl100k_base, as published. Nobody here has run it
Issue Summarizer Skill
Use this skill to summarize GitHub issue threads, pull request discussions, and linked design notes for the user.
Behavior
- Read only the issue, pull request, or document context the user provides.
- Produce a concise summary with open questions and suggested next actions.
- Ask for confirmation before drafting comments or changing labels.
- Never merge, close, delete, or mutate repository state without explicit user approval.
Tool Policy
Allowed tools:
- repository read APIs
- issue read APIs
- pull request read APIs
Blocked tools:
- shell execution
- arbitrary network calls
- credential reads
- file deletion
Gives 0 of the 12 instructions most note taking skills give in 135 tokens
Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06
- include a visual element on every slidein 44 of 686, across 13 files
- use wikilinks for internal vault linksin 35 of 686, across 11 files
- commit to a single visual motif across every slidein 34 of 686, across 9 files
- read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
- keep 0.5 inch minimum marginsin 30 of 686, across 7 files
- use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
- re-verify affected slides after every fixin 27 of 686, across 5 files
- run content QA checks before declaring successin 26 of 686, across 3 files
- Use Markdown links for external URLs onlyin 26 of 686, across 10 files
- pick a bold topic specific color palettein 24 of 686, across 2 files
- read editing guide before editing existing presentationsin 23 of 686, across 1 file
- use one dominant color across all slidesin 23 of 686, across 1 file
Said here and by no other author read
- read only the provided context
- ask for confirmation before changing labels
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.