agentleFS
Sign inStart free
ecosyste-msecosyste-ms/claude-plugin/skills/issues/SKILL.md

issues

Skill3 starsChanged 6 months agoMITView on GitHub

Query issues.ecosyste.ms for issue and pull request metadata and statistics across GitHub, GitLab and other forges. Use when checking how responsive a project is, average time to close, PR merge rate, contributor counts, or listing open issues without hitting the forge API directly.

  • Sends data out

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prd, architecture and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GitHubSkill

    prd

    Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

    Also in 6 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 6 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All responses are JSON. No auth required.

    line 11
  2. Distinctive:

    If a repo isn't indexed yet, POST a job and poll it:

    line 59

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

ecosyste.ms Issues API

Base URL: https://issues.ecosyste.ms/api/v1

All responses are JSON. No auth required. Set a User-Agent header. Lookup endpoints return a 302 redirect, so use curl -L.

Full OpenAPI spec: https://issues.ecosyste.ms/docs/api/v1/openapi.yaml

Repository issue stats

curl -sL 'https://issues.ecosyste.ms/api/v1/repositories/lookup?url=https://github.com/rails/rails'

Or directly by host (repo names containing / must be URL-encoded as %2F):

curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails'

Returns aggregate stats for all time and the past year: issues_count, pull_requests_count, issues_closed_count, merged_pull_requests_count, avg_time_to_close_issue (seconds), avg_time_to_close_pull_request, issue_authors_count, pull_request_authors_count, avg_comments_per_issue, bot_issues_count, bot_pull_requests_count, plus past_year_* variants of each.

List issues and PRs

# open issues (not PRs)
curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails/issues?state=open&pull_request=false'

# PRs with a given label
curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails/issues?pull_request=true&label=activerecord'

# a single issue
curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails/issues/50000'

# label counts
curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/rails%2Frails/labels'

Filters: state (open/closed), pull_request (true/false), label, created_after, updated_after, sort, order, page, per_page.

Owners and authors

Aggregated issue stats across every repo owned by an org, and per-author activity:

curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/owners/rails'
curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/owners/rails/maintainers'
curl -s 'https://issues.ecosyste.ms/api/v1/hosts/GitHub/authors/dhh'

Trigger a sync

If a repo isn't indexed yet, POST a job and poll it:

curl -s -X POST 'https://issues.ecosyste.ms/api/v1/jobs?url=https://github.com/owner/repo'
curl -s 'https://issues.ecosyste.ms/api/v1/jobs/<job-id>'

When to use

  • Assessing project health: are issues being closed, are PRs being merged
  • Comparing maintainer responsiveness between projects
  • Counting external vs bot contributions
  • Listing issues/PRs without GitHub API rate limits

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free