Source profileQuality 66/100

dyoshikawa/rulesync/.rulesync/skills/create-scrap-issue/SKILL.md

create-scrap-issue

Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap. Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.

Source repository stars
1,263
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Create a GitHub issue that consolidates passed content into a single scrap issue with background context and solution details, labeled as maintainer-scrap.

Best for

  • Use when the user wants to create a scrap issue, jot down notes as a GitHub issue, or save findings for later.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/create-scrap-issue"
Safe inspection promptEditorial

Inspect the Agent Skill "create-scrap-issue" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/create-scrap-issue/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Review the content provided by the user. 2. Organize and enrich it with background information and proposed solutions. 3. Check available labels with gh label list and determine which labels to attach in addition to maintainer-scrap. 4. Draft the issue body in the structure a…

    Review the content provided by the user.Organize and enrich it with background information and proposed solutions.Check available labels with gh label list and determine which labels to attach in addition to maintainer-scrap.
  2. 02

    Requirements

    Write the issue entirely in English.

    Write the issue entirely in English.Always attach the maintainer-scrap label to the issue.Additionally, judge whether other labels are appropriate based on the content and attach them as needed. For example:

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score66/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars1,263SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
dyoshikawa/rulesync
Skill path
.rulesync/skills/create-scrap-issue/SKILL.md
Commit
310b711fbe8cffc14debb276ade8a384c2b89083
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Create a single GitHub issue that consolidates all the content provided by the user.

Requirements

  • Write the issue entirely in English.
  • Always attach the maintainer-scrap label to the issue.
  • Additionally, judge whether other labels are appropriate based on the content and attach them as needed. For example:
    • bug — if the content describes a defect or unexpected behavior
    • enhancement — if the content proposes a new feature or improvement
    • documentation — if the content relates to docs updates
    • refactor — if the content discusses code restructuring
    • Use gh label list to check available labels in the repository before attaching.
  • Structure the issue so it is easy to understand even when revisited later:
    • Background: Describe the context, motivation, and why this matters.
    • Details: Include the specific content, observations, or problems passed by the user.
    • Solution / Next Steps: Propose a solution or outline actionable next steps.
  • Use a clear, descriptive title that summarizes the scrap topic.
  • Use gh issue create to create the issue.

Workflow

  1. Review the content provided by the user.
  2. Organize and enrich it with background information and proposed solutions.
  3. Check available labels with gh label list and determine which labels to attach in addition to maintainer-scrap.
  4. Draft the issue body in the structure above.
  5. Create the issue with the appropriate labels using gh issue create --label maintainer-scrap --label <other-labels>.

Alternatives

Compare before choosing