Is github-issue-creator safe to install?

SaferSkills independently audited github-issue-creator (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/github-issue-creator/SKILL.md · 1 file

skills/github-issue-creator/SKILL.md2.2 KB · Markdown

name: github-issue-creator

description: Structure bug reports, requirements, logs, or screenshots into actionable GitHub issues. Use it when you need acceptance criteria, scope definition, and a validation plan.

GitHub Issue Creator

Purpose

Turn unstructured input into a GitHub issue that is ready for development.

Core Principles

Put the acceptance criteria at the top using Given/When/Then.
Separate In Scope from Out of Scope.
An issue without a validation plan, automated or manual, is not complete.
If information is missing, ask follow-up questions instead of guessing.
Replace sensitive information with placeholders such as [USER_ID] or [TOKEN].
Include at least one recommended PR label for release categorization in the issue body.

Release Label Hints

Based on .github/release.yml, PR labels determine the release category.

New Features: feat, feature, enhancement
Bug Fixes: fix, bug, bugfix
Maintenance (Chore): chore, dependencies, ci, build, refactor
Unmatched or missing labels: Other Changes

Recommended:

Include the recommended PR label in the issue.
Apply the same label on the implementation PR to avoid release-note classification gaps.

Output Format

Title

[type] one-line summary
type: feat|fix|refactor|docs|chore|test

Acceptance Criteria

Given ...
When ...
Then ...

Background or Problem

Current state
User or operational impact

Scope

In Scope
Out of Scope

Implementation Direction

Target areas or modules
Constraints and dependencies
Risks
Recommended PR label (feat|feature|enhancement|fix|bug|bugfix|chore|dependencies|ci|build|refactor)

Validation Plan

Automated validation: lint, build, test
Manual validation: key scenarios
For UI changes: screenshot checkpoints

Completion Criteria

AC satisfied
No regressions
Release impact and cautions documented

Checklist

[ ] Implementation complete
[ ] Tests complete
[ ] Regression check complete
[ ] Recommended PR label assigned or confirmed
[ ] Docs or release notes updated if needed

When Information Is Missing

Draft the issue first.
Limit follow-up questions to three.

github-issue-creator— agent skill

Is github-issue-creator safe to install?

GitHub Issue Creator

Purpose

Core Principles

Release Label Hints

Output Format

Title

Acceptance Criteria

Background or Problem

Scope

Implementation Direction

Validation Plan

Completion Criteria

Checklist

When Information Is Missing

Audit the pieces. Scan the whole. Decide.