Agent skill

Closing Obsolete Issues

by dart-lang in dart-lang/ai

Find and close obsolete, stale, or not reproducible issues in the dart-lang/ai repository.

BSD-3-ClauseAuto-check passed

Install Closing Obsolete Issues

skills CLI
$ npx skills add dart-lang/ai --skill closing-obsolete-issues -a claude-code

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

GitHub CLI
$ gh skill install dart-lang/ai closing-obsolete-issues --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/dart-lang/ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/closing-obsolete-issues .claude/skills/closing-obsolete-issues && 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
closing-obsolete-issues
GitHub stars
286
Token cost
~794 tokens
SKILL.md length
448 words
Files
2 (incl. references)
Skills in repo
3
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Find and close obsolete, stale, or not reproducible issues in the dart-lang/ai repository.

  • Works in 5 steps: Identify Target Issues → Investigate Status → Draft and Review Closing Comments… → …
  • SKILL.md covers Instructions and Tips
  • Calls gh

What it does

Closing Obsolete Issues is an agent skill from dart-lang/ai. Find and close obsolete, stale, or not reproducible issues in the dart-lang/ai repository.

Its SKILL.md is about 790 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rationale_templates.md`).

The repository describes itself as: A general repository for AI / GenAI packages and explorations. The licence is BSD-3-Clause.

Example prompts

  • “/closing-obsolete-issues”

Workflow steps

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

  1. Identify Target Issues
  2. Investigate Status
  3. Draft and Review Closing Comments (CRITICAL MANDATE)
  4. Iterate on Skill Knowledge (Learning Loop)
  5. Execute and Summarize

What it can do on your machine

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

Closing Obsolete Issues loads about 794 tokens when it runs, and up to ~1.2k if it reads all its reference files. Until then it costs about 29 tokens; SKILL.md has 448 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~794
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.2k

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 dart-lang/ai at commit 60a4b18, republished under its BSD-3-Clause licence (© dart-lang). 448 words, ~794 tokens.

Download SKILL.mdSave it as .claude/skills/closing-obsolete-issues/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
closing-obsolete-issues
description
Find and close obsolete, stale, or not reproducible issues in the dart-lang/ai repository.
internal
true

Closing Obsolete Issues

Use this skill to find old, outdated issues in the dart-lang/ai repository that can be closed because they have been fixed, are stale, obsolete, or not reproducible.

Instructions

  1. Identify Target Issues:

    • Use the GitHub CLI (gh) to search for the oldest open issues.
    • Use any label that the user gives you, or none if the user does not specify any issue labels.
    • Sort by creation date (created-asc) or last update (updated-asc) to find the most likely candidates for being outdated.
    • Fetch at least 10-20 candidates.
    • Example command (with label): gh issue list --repo dart-lang/ai --search "label:bug is:open sort:created-asc" --limit 20 | cat
    • Example command (without label): gh issue list --repo dart-lang/ai --search "is:open sort:created-asc" --limit 20 | cat
  2. Investigate Status:

    • For each candidate, analyze its description and comments.
    • Use gh issue view <number> --repo dart-lang/ai to get details.
    • Compare the issue's request or reported bug with the current state of the codebase.
    • Refer to references/rationale_templates.md for a library of common reasons issues become outdated.
    • Safety Rule: Do not assume a bug is fixed or obsolete just because the code has been updated. Verify if the specific bug behavior is still possible. Valid bugs or feature requests should not be closed as stale just because they are old or have no activity. Inactivity alone does not invalidate a feature request or bug report.
  3. Draft and Review Closing Comments (CRITICAL MANDATE):

    • For issues identified as candidates for closing, draft a detailed comment for each explaining why it can be closed.
    • Style Constraint: DO NOT use em dashes (—) in the comments. Use hyphens (-) or colons (:) instead.
    • Template: Consult references/rationale_templates.md for wording inspiration.
    • Each comment MUST end with: "If there is more work to do here, please let us know by commenting on this issue or filing a new one with up to date information. Thanks!"
    • User Approval Required: You MUST present the identified issues (including URLs to the issues for easy navigation) and their drafted comments to the user and obtain explicit approval BEFORE running any command that closes an issue.
  4. Iterate on Skill Knowledge (Learning Loop):

    • If you discover a new, distinct category of closing rationale that is not covered in references/rationale_templates.md, update the reference file to include it.
  5. Execute and Summarize:

    • Once approved, use gh issue close with the -c flag to post the comment and close the issue.
    • Provide the user with a clean bulleted list of links to each closing comment.
Show full SKILL.md (40 more words)Show less

Tips

  • Use available file and content search tools (such as grep, ripgrep) to check the current codebase for references to the issue or relevant code.
  • Look for related PRs that might have fixed the issue but didn't close it automatically.

© dart-lang, BSD-3-Clause. 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 (references) in .agents/skills/closing-obsolete-issues of dart-lang/ai.

  • SKILL.md
  • references/rationale_templates.md

Open the folder on GitHubat commit 60a4b18

Compare with similar skills

Closing Obsolete Issues 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.

Closing Obsolete Issues compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Closing Obsolete Issues this skilldart-lang/ai286—~794Automated safety check: PassBSD-3-Clause
Closing Obsolete Issuesflutter/devtools1.7k—~949Automated safety check: PassBSD-3-Clause
Closing Checklistanthropics/claude-for-legal9.6k2 repos~2.9kAutomated safety check: PassApache-2.0
Closedavepoon/buildwithclaude3.6k—~2.5kAutomated safety check: PassMIT
Reproduce Issuenrwl/nx29k—~2.6kAutomated safety check: NotesMIT
Weather Data Reproducibilitysickn33/agentic-awesome-skills47k1 repos~2.9kAutomated safety check: PassMIT

Similar skills

  • Closing Obsolete Issues

    flutter/devtools

    Find and close obsolete, stale, or not reproducible issues in the flutter/devtools repository.

    1.7k GitHub stars~949 tokensUpdated 2 days ago
    MobileAuto-check passed
  • Closing Checklist

    anthropics/claude-for-legal

    Official

    What's blocking close — maintain the closing checklist with status, critical path, and days to close.

    9.6k GitHub starsUsed in 2 repos~2.9k tokens
    Auto-check passed
  • Close

    davepoon/buildwithclaude

    Commit the session to durable vault memory and prepare a clean resume point

    3.6k GitHub stars~2.5k tokensUpdated yesterday
    Knowledge ManagementAuto-check passed
  • The single skill for reproducing an nx issue. An agent skill from nrwl/nx.

    29k GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Weather Data Reproducibility

    sickn33/agentic-awesome-skills

    Record and verify provenance manifests for weather-data inputs and derived artifacts, including object identity, selections, software versions, transformations, and hashes.

    47k GitHub starsUsed in 1 repo~2.9k tokens
    Research & ScienceAuto-check passed
  • Reproducible Pipelines

    brycewang-stanford/Auto-Empirical-Research-Skills

    This skill covers reproducible research pipelines and replication packages.

    4.6k GitHub stars~3.3k tokensUpdated 4 days ago
    Research & ScienceAuto-check passed

More from dart-lang/ai

  • Instructions for updating the supported Model Context Protocol (MCP) specification version in the dartmcp package.

    286 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Instructions for adding new features (tools, prompts, etc.) to the dartmcpserver package.

    286 GitHub stars~687 tokensUpdated 2 days ago
    Auto-check passed

Questions about Closing Obsolete Issues

What does Closing Obsolete Issues do?

Find and close obsolete, stale, or not reproducible issues in the dart-lang/ai repository. Closing Obsolete Issues is an agent skill from dart-lang/ai. Find and close obsolete, stale, or not reproducible issues in the dart-lang/ai repository.

How do I install Closing Obsolete Issues in Claude Code?

Run `npx skills add dart-lang/ai --skill closing-obsolete-issues -a claude-code`. Or copy the skill folder (.agents/skills/closing-obsolete-issues in dart-lang/ai) into .claude/skills/closing-obsolete-issues in your project. Claude Code loads it when a task matches its description.

How do I install Closing Obsolete Issues in Codex?

Run `npx skills add dart-lang/ai --skill closing-obsolete-issues -a codex`. Or copy the skill folder (.agents/skills/closing-obsolete-issues in dart-lang/ai) into .agents/skills/closing-obsolete-issues in your project. Codex loads it when a task matches its description.

Can I use Closing Obsolete Issues 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 dart-lang/ai --skill closing-obsolete-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/closing-obsolete-issues, .gemini/skills/closing-obsolete-issues, .github/skills/closing-obsolete-issues and .opencode/skills/closing-obsolete-issues in your project.

What does Closing Obsolete Issues need to run?

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

Does Closing Obsolete Issues 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 Closing Obsolete Issues 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 Closing Obsolete Issues use?

Closing Obsolete Issues is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Closing Obsolete Issues use?

About 794 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 357 tokens, read only when the agent opens those files.

What are the alternatives to Closing Obsolete Issues?

Skills that share tags, products or a category with Closing Obsolete Issues: Closing Obsolete Issues (flutter/devtools, 1.7k stars), Closing Checklist (anthropics/claude-for-legal, 9.6k stars), Close (davepoon/buildwithclaude, 3.6k stars) and Reproduce Issue (nrwl/nx, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Closing Obsolete Issues?

dart-lang (a GitHub organization) maintains it in dart-lang/ai, which has 286 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

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