New: 97,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

File Issue

by open-thoughts in open-thoughts/OpenThoughts-Agent

File a GitHub issue for a bug or improvement found this session.

Apache-2.0Auto-check passed

Install File Issue

skills CLI
$ npx skills add open-thoughts/OpenThoughts-Agent --skill file-issue -a claude-code

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

GitHub CLI
$ gh skill install open-thoughts/OpenThoughts-Agent file-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/open-thoughts/OpenThoughts-Agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/file-issue .claude/skills/file-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
file-issue
GitHub stars
301
Token cost
~1.6k tokens
SKILL.md length
776 words
Files
1
Skills in repo
44
Repo updated
First seen
Licence
Apache-2.0

At a glance

File a GitHub issue for a bug or improvement found this session.

  • Works in 8 steps: Gather Context from Conversation → Classify the Issue → Duplicate Check → …
  • SKILL.md covers Background, Issue Kinds and Body Structure, Workflow and Writing Style, plus 1 more section
  • Calls gh

What it does

File Issue is an agent skill from open-thoughts/OpenThoughts-Agent. File a GitHub issue for a bug or improvement found this session.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. The repository describes itself as: Data recipes and robust infrastructure for training AI agents. The licence is Apache-2.0.

Example prompts

  • “/file-issue”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Gather Context from Conversation
  2. Classify the Issue
  3. Duplicate Check
  4. Draft the Issue
  5. Compress and Inspect the Payload
  6. Confirm or File Directly
  7. File the Issue
  8. Report Back

What it can do on your machine

Read from SKILL.md and the folder at commit 3bd1917. 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

    Shell commands in SKILL.md call:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

File Issue loads about 1.6k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 776 words of instructions outside code blocks.

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

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 open-thoughts/OpenThoughts-Agent at commit 3bd1917, republished under its Apache-2.0 licence (© open-thoughts). 776 words, ~1,643 tokens.

Download SKILL.mdSave it as .claude/skills/file-issue/SKILL.md (or your agent's skills folder).
name
file-issue
description
File a GitHub issue for a bug or improvement found this session.
<!-- Vendored from marin-community/marin-style v0.3.0 — do not edit; re-run `marin-style sync`. -->

Skill: File GitHub Issue

Create a GitHub issue in the current repository from bugs, regressions, or improvements identified in the current conversation. gh defaults to the repo of the current checkout; pass --repo <owner>/<name> only to target a different one.

Background

Read first: AGENTS.md.

Before drafting, read:

  • .agents/skills/writing-style/SKILL.md
  • .agents/skills/writing-style/issues.md
  • .agents/skills/writing-style/ai-writing-donts.md

Issue Kinds and Body Structure

Pick the kind, then use the matching body structure below. There are no GitHub issue templates — these structures live here.

KindWhen to useLabels
bugA bug or regression was foundbug, agent-generated
taskAn improvement, refactor, or feature requestagent-generated + priority if known
experimentAn experiment needs trackingexperiment, agent-generated
Bug body
markdown
<what is broken and its impact -- concrete symptoms or error messages>

Reproduce:
1. <step>
2. <step>

Expected: <what should happen instead>

<optional: concise evidence or confirmed root cause>
Task body
markdown
<what needs to be done and why -- enough context for anyone on the team>

Done when:
<specific, testable completion criteria>
Experiment body
markdown
## TL;DR

<One-paragraph current summary. Leave blank only when the work is just being kicked off.>

## Description

<Context someone outside the thread can understand.>

## Hypothesis or Goal

<What are you trying to learn, fix, or achieve?>

## Status

<Current state; update as evidence lands.>

## Links

* Logbook:
* Report:
* Important updates:

## Decision Log

## Conclusion

Workflow

1. Gather Context from Conversation

Extract from the conversation:

  • What is broken or missing -- concrete symptoms, error messages, failing test output.
  • Where it happens -- file paths, line numbers, module names.
  • How to reproduce -- steps, commands, or minimal config that triggers it.
  • Root cause (if known).
  • Severity -- blocks work, causes data loss, or cosmetic?

If it's ambiguous what to file, ask the user before proceeding.

2. Classify the Issue

Pick the kind (bug, task, or experiment). If unsure, ask the user.

3. Duplicate Check

Search for existing issues first:

bash
gh issue list --state open --search "<keyword>"

If a match exists, tell the user and offer to comment on it instead.

4. Draft the Issue

Title: At most 80 characters, optionally prefixed with a scope tag. State a factual symptom for a bug (e.g. [training] Gradient accumulation drops the last microbatch) and an imperative outcome for a task (e.g. [training] Handle partial accumulation steps). Do not add bug:, task:, or another type prefix.

Body: Use the section structure for the chosen kind (see above).

Rules for the body:

  • No filler ("I noticed...", "During our conversation...").
  • No markdown images or tables.
  • Reference code with file:line links, not inline dumps.
  • Keep every fact needed to understand and act on the issue. Remove history, repetition, and implementation narration that does not define the problem or completion criteria; experiment issues may retain more tracking context.
  • Do not repeat the title in a Description section.
  • Do not inventory files, functions, or proposed implementation steps that are not required to define the problem or completion criteria.
  • Include error messages or stack traces in code blocks, trimmed to the relevant frames.
  • For task issues: include concrete Done when criteria.
  • For bug issues: include numbered reproduction steps.
5. Compress and Inspect the Payload

Apply the writing-style final compression pass to the exact title and body that will be sent to GitHub. For a bug or task, verify the title is at most 80 characters. Every remaining sentence must add a symptom, impact, reproduction step, observation, expected behavior, or completion criterion.

This review is required even when the user explicitly asked to file the issue. It is an author self-check, not a request for approval.

Show full SKILL.md (305 more words)Show less
6. Confirm or File Directly

If the user explicitly asked to file an issue, skip the preview — file it and share the link. If the agent surfaced the issue (not explicitly requested), show the drafted title and body and wait for approval or edits.

7. File the Issue

Write the body to a uniquely named temp file, then pass it with --body-file. Do not inline the body with shell substitution (--body "$(cat <<'EOF' ...)") — multiline text can be corrupted by pasted output or escaping mistakes. Do not reuse a fixed path like /tmp/issue-body.md; concurrent agent runs can overwrite each other's drafts on shared hosts.

bash
body_file="$(mktemp "${TMPDIR:-/tmp}/issue-body.XXXXXX.md")"
trap 'rm -f "$body_file"' EXIT

cat > "$body_file" <<'EOF'
<body>
EOF

issue_url="$(gh issue create \
  --title "<title>" \
  --label "agent-generated" \
  --body-file "$body_file")"

Add kind-appropriate labels (bug, experiment). If a relevant label does not exist, skip it rather than creating new labels. For task issues, add a priority label (p1, p2, p3) if the user specifies one or severity is clear.

Before creating the issue, re-open the body file and verify it contains no unrelated shell output (pre-commit logs, pytest session headers, prompt transcripts). If it does, clean the draft before posting.

After creating the issue, fetch its published text with gh issue view "$issue_url" --json title,body and correct any text added or altered by the publishing tool.

8. Report Back

Print the issue URL.

Writing Style

Terse: every sentence conveys new information; no preamble or editorializing; no restating code a link covers; annotate code links, don't narrate them.

Rules

  1. Never credit yourself in the issue.
  2. Always add the agent-generated label.
  3. Confirm with the user before filing only when the agent surfaced the issue (not when the user explicitly asked to file).
  4. If the conversation does not contain a clear bug or actionable improvement, say so and ask the user what they want to file.
  5. Use the smallest matching body structure. Omit optional context and headings that add no information.

© open-thoughts, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/file-issue of open-thoughts/OpenThoughts-Agent.

Open the folder on GitHubat commit 3bd1917

Compare with similar skills

File 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.

File Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
File Issue this skillopen-thoughts/OpenThoughts-Agent301—~1.6kAutomated safety check: PassApache-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers296k3 repos~1.7kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow83k5 repos~1.3kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    296k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    83k GitHub starsUsed in 5 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed

More from open-thoughts/OpenThoughts-Agent

All 44 skills in this repo

  • Analyze Dataset Token Length

    open-thoughts/OpenThoughts-Agent

    Analyze the token length of an OT-Agent conversation-format (ShareGPT-style) dataset — the per-trace distribution (median/p90/max) and/or counts under a token threshold + a metadata predicate (e.g.

    301 GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check passed

  • Analyze Id Eval Ranking

    open-thoughts/OpenThoughts-Agent

    Given a list of models (HF name stubs) that have valid agentic ID eval scores in Supabase, build a ranking table: raw per-benchmark accuracy on the 3 ID benchmarks (SWE-Bench-100…

    301 GitHub stars~3.1k tokensUpdated 9 days ago
    Auto-check passed

  • Analyze Job History Iris

    open-thoughts/OpenThoughts-Agent

    Run the Iris harbor job-history analyzer (scripts/iris/analyzeirisharborjob.py) on a datagen/eval job and read its JSON sidecar for trustworthy throughput / preemption / productive-trial stats.

    301 GitHub stars~2.9k tokensUpdated 9 days ago
    Auto-check passed

  • Analyze Rl Behavior

    open-thoughts/OpenThoughts-Agent

    Run the full RL behavioral-analysis pipeline (scripts/analysis/analyzerlbehavior.py) on a trained RL model to understand WHAT changed vs its pre-RL baseline, WHY, whether it PERSISTS, and its EVAL…

    301 GitHub stars~4.2k tokensUpdated 9 days ago
    Auto-check passed

  • Analyze Training Run Iris

    open-thoughts/OpenThoughts-Agent

    Detailed health check for a Levanter/executor TRAINING run on the marin Iris cluster (e.g.

    301 GitHub stars~2k tokensUpdated 9 days ago
    Auto-check passed

  • Code Create Staged Plan

    open-thoughts/OpenThoughts-Agent

    DESIGN a non-trivial codebase change (Harbor / MarinSkyRL / vLLM / OT-Agent / LLaMA-Factory) as a dependency-ordered STAGED PLAN before writing code — a feature port, a multi-step fix with parity…

    301 GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check passed

Works with

Questions about File Issue

What does File Issue do?

File a GitHub issue for a bug or improvement found this session. File Issue is an agent skill from open-thoughts/OpenThoughts-Agent. File a GitHub issue for a bug or improvement found this session.

How do I install File Issue in Claude Code?

Run `npx skills add open-thoughts/OpenThoughts-Agent --skill file-issue -a claude-code`. Or copy the skill folder (.agents/skills/file-issue in open-thoughts/OpenThoughts-Agent) into .claude/skills/file-issue in your project. Claude Code loads it when a task matches its description.

How do I install File Issue in Codex?

Run `npx skills add open-thoughts/OpenThoughts-Agent --skill file-issue -a codex`. Or copy the skill folder (.agents/skills/file-issue in open-thoughts/OpenThoughts-Agent) into .agents/skills/file-issue in your project. Codex loads it when a task matches its description.

Can I use File 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 open-thoughts/OpenThoughts-Agent --skill file-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/file-issue, .gemini/skills/file-issue, .github/skills/file-issue and .opencode/skills/file-issue in your project.

What does File Issue need to run?

Going by SKILL.md and its folder, File Issue needs the command-line tools its instructions call (gh).

Does File Issue access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is File 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 File Issue use?

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

How many tokens does File Issue use?

About 1.6k tokens (SKILL.md is roughly 6.6k 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 File Issue?

Skills that share tags, products or a category with File Issue: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains File Issue?

open-thoughts (a GitHub organization) maintains it in open-thoughts/OpenThoughts-Agent, which has 301 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on September 28, 2026.

Source: open-thoughts/OpenThoughts-Agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.