New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Create Issue

by uw-syfi in uw-syfi/vibesys

Investigate, draft, and file well-scoped VibeSys GitHub issues using the repository issue forms and project conventions.

MITAuto-check passedTesting & QA

Install Create Issue

skills CLI
$ npx skills add uw-syfi/vibesys --skill create-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install uw-syfi/vibesys create-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/uw-syfi/vibesys.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/create-issue .claude/skills/create-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
create-issue
GitHub stars
103
Token cost
~848 tokens
SKILL.md length
403 words
Files
2
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Investigate, draft, and file well-scoped VibeSys GitHub issues using the repository issue forms and project conventions.

  • Works in 11 steps: Resolve the repository and requested… → Read… → Select exactly one matching form and… → …
  • A user asks to create
  • SKILL.md covers Overview, Workflow, Authoring Rules and GitHub Boundaries
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Issue is an agent skill from uw-syfi/vibesys. Investigate, draft, and file well-scoped VibeSys GitHub issues using the repository issue forms and project conventions. Use when a user asks to create, open, or file a bug report, engineering change, expansion scenario or harness, or research experiment issue, or asks to turn findings, TODOs, or proposed work into GitHub issues.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Testing & QA, covering QA and bug reports. It works with GitHub. The repository describes itself as: Can AI Agents Build Bespoke Systems? The licence is MIT.

When your agent uses it

  • A user asks to create
  • File a bug report
  • Engineering change
  • Expansion scenario

Example prompts

  • “/create-issue”

Workflow steps

11 steps, taken from the first numbered list in SKILL.md.

  1. Resolve the repository and requested write scope. If the user asks only for
  2. Read docs/contributing/issue-authoring.md completely.
  3. Select exactly one matching form and read it completely
  4. Search the codebase and both open and closed issues. Check related pull
  5. If the request is a duplicate or already implemented, stop before creating
  6. Draft an outcome-oriented title and a body with the form's rendered section
  7. Create the issue through the connected GitHub tooling. Apply the form's
  8. Add the native parent/sub-issue relationship when a parent is known. A body
  9. Verify membership in organization project uw-syfi/1. If auto-add did not
  10. Set Workstream only when the mapping is unambiguous. Do not set Priority,
  11. Re-read the created issue and verify its title, body, labels, project

What it can do on your machine

Read from SKILL.md and the folder at commit c7784eb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Create Issue loads about 848 tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 403 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~848

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from uw-syfi/vibesys at commit c7784eb, republished under its MIT licence (© uw-syfi). 403 words, ~848 tokens.

Download SKILL.mdSave it as .claude/skills/create-issue/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
create-issue
description
Investigate, draft, and file well-scoped VibeSys GitHub issues using the repository issue forms and project conventions. Use when a user asks to create, open, or file a bug report, engineering change, expansion scenario or harness, or research experiment issue, or asks to turn findings, TODOs, or proposed work into GitHub issues.

Create Issue

Overview

Create issues only after confirming that the work is not already tracked or implemented. Use the same schemas as human reporters, preserve project metadata, and leave prioritization to maintainers.

Workflow

  1. Resolve the repository and requested write scope. If the user asks only for a draft, do not create or modify GitHub state.
  2. Read docs/contributing/issue-authoring.md completely.
  3. Select exactly one matching form and read it completely:
    • .github/ISSUE_TEMPLATE/01-bug.yml
    • .github/ISSUE_TEMPLATE/02-engineering-change.yml
    • .github/ISSUE_TEMPLATE/03-expansion-work.yml
    • .github/ISSUE_TEMPLATE/04-experiment.yml
  4. Search the codebase and both open and closed issues. Check related pull requests when they may show that the behavior is already implemented.
  5. If the request is a duplicate or already implemented, stop before creating an issue. Report the supporting issue, pull request, and code evidence.
  6. Draft an outcome-oriented title and a body with the form's rendered section headings. Keep acceptance criteria observable and testable.
  7. Create the issue through the connected GitHub tooling. Apply the form's labels and redact credentials, tokens, private paths, and sensitive logs.
  8. Add the native parent/sub-issue relationship when a parent is known. A body reference alone is not a substitute for the native relationship.
  9. Verify membership in organization project uw-syfi/1. If auto-add did not add the issue and project write access is available, add it explicitly.
  10. Set Workstream only when the mapping is unambiguous. Do not set Priority, Effort, assignee, Target date, or milestone unless the user explicitly asks or an established maintainer decision already exists.
  11. Re-read the created issue and verify its title, body, labels, project membership, and parent relationship. Return its URL and any metadata that remains for triage.
Show full SKILL.md (136 more words)Show less

Authoring Rules

  • Make one issue represent one independently closable outcome.
  • Lead with the problem, evidence, or research question rather than a proposed implementation.
  • State non-goals for work that could otherwise expand without a clear bound.
  • Use checkboxes for acceptance or success criteria.
  • For expansion work, specify externally observable semantics and correctness checks without prescribing an optimization strategy.
  • For experiments, require a decision, baseline, metric, protocol, stopping condition, and retained artifacts.
  • Link related work using native parents, dependencies, and closing keywords where supported.

GitHub Boundaries

Prefer connected GitHub tooling for issue search and creation. Use local gh only for project or hierarchy operations the connector cannot perform. Resolve field and option IDs dynamically; never hard-code project item IDs in reusable commands.

Do not claim that duplicate searches, code inspection, reproduction, or verification occurred unless they actually did.

© uw-syfi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/create-issue of uw-syfi/vibesys.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit c7784eb

Compare with similar skills

Create Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Create Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Issue this skilluw-syfi/vibesys103—~848Automated safety check: PassMIT
Weavebench Cua ReproduceAMAP-ML/LongHorizon-Harness1.7k—~1.6kAutomated safety check: PassMIT
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Create GitHub IssueNVIDIA/OpenShell15k—~1.7kAutomated safety check: PassApache-2.0
Triage IssuesClickHouse/clickhouse-java1.6k—~904Automated safety check: PassApache-2.0
Gentle AI Issue CreationGentleman-Programming/gentle-shell1.2k—~2.5kAutomated safety check: PassApache-2.0

Similar skills

  • Weavebench Cua Reproduce

    AMAP-ML/LongHorizon-Harness

    Reproduce CUA-Harness experiments on WeaveBench from a GitHub checkout.

    1.7k GitHub stars~1.6k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Create GitHub Issue

    NVIDIA/OpenShell

    Official

    Create GitHub issues using the gh CLI. An agent skill from NVIDIA/OpenShell.

    15k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed

  • Triage Issues

    ClickHouse/clickhouse-java

    Analyzes a single GitHub issue at a time. An agent skill from ClickHouse/clickhouse-java.

    1.6k GitHub stars~904 tokensUpdated today
    Testing & QAAuto-check passed

  • Gentle AI Issue Creation

    Gentleman-Programming/gentle-shell

    Create and triage GitHub issues from repository evidence. An agent skill from Gentleman-Programming/gentle-shell.

    1.2k GitHub stars~2.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Termio Bug Report

    termio-sh/termio

    Diagnose a termio hang, beachball, crash, or 'it froze again' from the evidence macOS and termio actually leave behind — live process samples, crash and CPU-burn reports, the unified log, the…

    540 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed

More from uw-syfi/vibesys

All 15 skills in this repo

  • Neuron Nki Profiling

    uw-syfi/vibesys

    This skill guides using the cli to generate NKI kernel profiles (NEFF + NTFF pairs) to analyze performance on Neuron hardware.

    103 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed

  • Neuron Nki Debugging

    uw-syfi/vibesys

    This skill guides debugging NKI compilation errors on Neuron hardware.

    103 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Neuron Nki Docs

    uw-syfi/vibesys

    Research NKI documentation for API lookups, tutorials, error codes, architecture, and optimization guides.

    103 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Neuron Nki Profile Querying

    uw-syfi/vibesys

    Query and analyze NKI kernel profile data from neuron-explorer parquet files.

    103 GitHub stars~4.3k tokensUpdated yesterday
    Auto-check passed

  • Neuron Nki Writing

    uw-syfi/vibesys

    Guide for writing and modifying NKI kernels. An agent skill from uw-syfi/vibesys.

    103 GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

  • Triage PRs

    uw-syfi/vibesys

    Triage the open pull requests of the VibeSys repository. An agent skill from uw-syfi/vibesys.

    103 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Create Issue

What does Create Issue do?

Investigate, draft, and file well-scoped VibeSys GitHub issues using the repository issue forms and project conventions. Create Issue is an agent skill from uw-syfi/vibesys. Investigate, draft, and file well-scoped VibeSys GitHub issues using the repository issue forms and project conventions.

When should I use Create Issue?

Create Issue fits situations like: A user asks to create; file a bug report; engineering change; expansion scenario.

How do I install Create Issue in Claude Code?

Run `npx skills add uw-syfi/vibesys --skill create-issue -a claude-code`. Or copy the skill folder (.agents/skills/create-issue in uw-syfi/vibesys) into .claude/skills/create-issue in your project. Claude Code loads it when a task matches its description.

How do I install Create Issue in Codex?

Run `npx skills add uw-syfi/vibesys --skill create-issue -a codex`. Or copy the skill folder (.agents/skills/create-issue in uw-syfi/vibesys) into .agents/skills/create-issue in your project. Codex loads it when a task matches its description.

Can I use Create Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add uw-syfi/vibesys --skill create-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-issue, .gemini/skills/create-issue, .github/skills/create-issue and .opencode/skills/create-issue in your project.

What does Create Issue need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Issue is instructions for the agent only.

Does Create Issue access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Create Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Create Issue use?

Create Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Issue use?

About 848 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Issue?

Skills that share tags, products or a category with Create Issue: Weavebench Cua Reproduce (AMAP-ML/LongHorizon-Harness, 1.7k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Create GitHub Issue (NVIDIA/OpenShell, 15k stars) and Triage Issues (ClickHouse/clickhouse-java, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Issue?

uw-syfi (a GitHub organization) maintains it in uw-syfi/vibesys, which has 103 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 7, 2026.

Source: uw-syfi/vibesys on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.