github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep issues', 'close stale issues', 'handle issue #N', 'backlog sweep', 'label issues', 'stale pass', 'wont-fix pass', 'issue accounting', 'how many issues', 'backlog health', or any request involving issue lifecycle management for the ZeroClaw project.
Static checks cannot guarantee safety.
Critical Safety system bypass instruction
Open the leading finding →33970c5Source unchanged, checked Oct 28, 2026Historical result (archived, not the current assessment)
- Source badge at capture
- Archived Fail as archived
Archived explanation: Skill failed: 1 hard fail in security or structure checks.
Pass and Fail now belong to Framework checks.
Scanners, signals and record facts
- Assessed
- Oct 28, 2026
- Content hashA Git tree SHA of the skill's folder. It identifies the files that were assessed. It is not a commit.
33970c5- Next source check
- Oct 29, 2026
- Files
- 2 in the skill, 2 with findings (File structure)
- Record ID
dc27e2b
github-issue-triageWhich scanners reported what
| Scanner | Run | Security severity reported | Security findings | Other findings | Notes |
|---|---|---|---|---|---|
vettd | Completed | Critical | 2 | 0 | 0 |
cisco | Completed | Informational | 0 | 0 | 1 |
The overall score is F: 1 critical finding. It counts findings in every category. Security severity is Critical, the highest security finding across the scanners that ran (vettd reported critical; cisco reported informational). No captured run is recorded for snyk, socket and gen-trust-hub.
Security findings
- Critical
- Medium
- Note
What this assessment does not cover
Static checks only, not a safety guarantee. What this does not cover
- Static checks only. Nothing in the skill was run.
- Pages linked from SKILL.md were not fetched or checked.
- This record is not signed yet, so you can't verify it came from Vettd unchanged.
- Name, description, author, version and license are shown as the author wrote them. Vettd didn't verify them.
- Cost, runtime characteristics and usage are not assessed.
- Framework checks (OWASP Top 10 for LLM Applications 2025): not assessed for this record.
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep issues', 'close stale issues', 'handle issue #N', 'backlog sweep', 'label issues', 'stale pass', 'wont-fix pass', 'issue accounting', 'how many issues', 'backlog health', or any request involving issue lifecycle management for the ZeroClaw project.
Static checks cannot guarantee safety.
Critical Safety system bypass instruction
Open the leading finding →33970c5Source unchanged, checked Oct 28, 2026Historical result (archived, not the current assessment)
- Source badge at capture
- Archived Fail as archived
Archived explanation: Skill failed: 1 hard fail in security or structure checks.
Pass and Fail now belong to Framework checks.
Full record · metadata, license, scanners and provenance
- Assessed
- Oct 28, 2026
- Content hashA Git tree SHA of the skill's folder. It identifies the files that were assessed. It is not a commit.
33970c5- Next source check
- Oct 29, 2026
- Files
- 2 in the skill, 2 with findings (File structure)
- Record ID
dc27e2b
github-issue-triageWhich scanners reported what
The overall score is F: 1 critical finding. It counts findings in every category. Security severity is Critical, the highest security finding across the scanners that ran (vettd reported critical; cisco reported informational).
vettdCritical2 security findingsciscoInformational0 security findingsSecurity findings
- Critical
- Medium
- Note
Not covered
Static checks only. Linked pages not fetched. Record not signed yet. Author details not verified. Framework checks not assessed.