Skills github-issue-creator
๐Ÿ“ฆ

github-issue-creator

Content revision r1 Low Risk โš™๏ธ External commands

Create Developer-Ready GitHub Issues

Unstructured bug reports slow triage and omit critical details. This skill converts logs, notes, screenshots, and dictation into structured GitHub issue markdown.

Supports: Claude Codex Code(CC)
๐Ÿ“Š 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "github-issue-creator" from https://skillstore.io/skills/sickn33-github-issue-creator.md and its manifest at https://skillstore.io/api/skills/sickn33-github-issue-creator/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "github-issue-creator". The CSV export button spins forever after selecting more than 5,000 records. Chrome 126 on Windows. Smaller exports work.

Expected outcome:

Summary: CSV export stalls above 5,000 records. Environment: Chrome 126 on Windows. Impact: Medium because smaller exports provide a workaround.

Using "github-issue-creator". Publishing to the Teams channel returns PERMISSION_DENIED with status 403. It worked yesterday.

Expected outcome:

Summary: Teams publishing fails with a 403 permission error. Additional context: This is a regression from previously working behavior. Impact: High.

Using "github-issue-creator". Voice note says deployment finished, but the agent vanished from the list until the third retry.

Expected outcome:

Summary: Agent deployment completes without displaying the agent. Actual behavior: The agent disappears without an error. Impact: High because deployment is blocked.

Security Audit

Low Risk
v5 โ€ข 7/23/2026 Open versioned report

All 13 static findings are false positives caused by Markdown code fences and inline code spans. No Ruby or shell command execution appears in SKILL.md. The skill requests repository file creation, creating a limited filesystem write risk.

1
Files scanned
149
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (1)

Low
Repository File Creation Without Collision Safeguard
SKILL.md instructs the agent to create Markdown files in /issues/ with deterministic date-based names, but it does not require an existence check before writing.
Line 52 explicitly requires file creation and defines the naming format. No collision or overwrite safeguard is stated.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-github-issue-creator/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-github-issue-creator/security.svg)](https://skillstore.io/skills/sickn33-github-issue-creator?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-github-issue-creator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-github-issue-creator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-github-issue-creator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). github-issue-creator security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-github-issue-creator/audits/5

BibTeX citation

@techreport{sickn33-sickn33-github-issue-creator-2026, author = {sickn33}, title = {github-issue-creator security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-github-issue-creator/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "github-issue-creator security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-github-issue-creator/audits/5" identifiers: - type: other value: "skillstore:sickn33-github-issue-creator:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Convert Support Notes

Turn customer reports and support notes into structured issues for engineering triage.

Standardize Test Defects

Transform test observations, screenshots, and error output into consistent defect reports.

Document Production Failures

Capture incident symptoms, impact, environment details, and reproduction evidence for follow-up work.

Try These Prompts

Create an Issue from a Note
Create a GitHub issue from this bug note: [NOTE]. Use placeholders for sensitive data and ask about missing required details.
Structure an Error Report
Turn this error log and context into an issue: [ERROR LOG] [CONTEXT]. Include environment, reproduction steps, expected behavior, actual behavior, and impact.
Combine Multiple Evidence Sources
Create one issue from these notes, screenshots, and logs: [EVIDENCE]. Separate confirmed facts from inferred details and list unanswered questions.
Draft a Triage-Ready Regression
Draft a regression issue from [EVIDENCE]. Compare previous and current behavior, assess impact, redact sensitive values, and propose a collision-safe filename.

Best Practices

  • Provide exact errors, timestamps, environment details, and observable behavior whenever available.
  • Mark inferred details clearly and confirm them before filing the issue.
  • Remove secrets and personal data while preserving useful diagnostic context.

Avoid

  • Do not invent reproduction steps, environments, or causes that the evidence does not support.
  • Do not include credentials, tokens, customer identifiers, or private repository details.
  • Do not overwrite an existing issue file without explicit confirmation.

Frequently Asked Questions

Does this skill create an issue on GitHub?
No. It creates a Markdown issue draft in the repository issues directory.
What input formats can it use?
It can organize error logs, rough notes, screenshots, attachment references, support reports, and voice dictation.
How does it handle sensitive information?
It replaces sensitive project names, user identifiers, and similar values with descriptive placeholders.
Can it determine issue severity?
It maps supplied impact evidence to critical, high, medium, or low severity definitions.
Will it verify the reported bug?
No. Reproduction steps and inferred context require environment-specific validation.
Where are issue drafts stored?
The skill directs agents to store dated Markdown files in the repository issues directory.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Ref

88a8e9a07f4c54ab105c1c41b6267c287146b07b

Maintenance freshness

7/26/2026

Usage

7 downloads ยท 117 views

File structure

๐Ÿ“„ SKILL.md

More from sickn33

View all
View all