github-list-issues

Lists a repo's issues, chains straight off github-search-repos or github-get-repo. Resolves in a single bridge call: the extractor fetches what it needs itself, so the params actually drive the request and no page is opened.

The extractor lives as text in the site's localStorage (key github-list-issues) and is rebuilt on each call with synchronous eval. It is stored once and then persists across navigation and browser restarts, so on every run except the first it is already there.

Default action: just call (step 1). The call itself reports NEEDS_STORE when the extractor is missing or out of date, only then do you store it (step 2) and call again.

Versioning. The stored extractor is gated by VER (must match the version in the frontmatter above). Both snippets carry VER = "1", keep them in sync with the frontmatter. When evaluate.js changes, bump version and VER in both snippets: the next call sees the mismatch, returns NEEDS_STORE, and re-stores automatically. Storage stays at two keys (github-list-issues and github-list-issues:ver), overwritten each store, versions never accumulate.

1. Call (do this every run, params only, single bridge call)

await (() => {
  const KEY = "github-list-issues", VER = "1";
  const s = localStorage.getItem(KEY);
  if (!s || localStorage.getItem(KEY + ":ver") !== VER) return 'NEEDS_STORE';
  const fn = eval('(' + s + ')');
  return fn(document, { full_name: "facebook/react", state: "open" });
})()

Returns the repo's issues. If it returns the string 'NEEDS_STORE', the extractor is missing or stale in this browser → do step 2 once, then run this exact call again.

Run this snippet verbatim. Never add an await before the eval, only the outer await is allowed.

A github.com tab is what holds the stored extractor (localStorage is per-origin). The data itself comes from the public api.github.com REST API, which is CORS-open, so no session and no page are involved.

2. Store (only when step 1 returned NEEDS_STORE; persists until localStorage is cleared)

From a github.com tab, evaluate the following with the bridge, replacing <FN> with the contents of evaluate.js (the ( async (root, params) => { ... } ) function). Keep VER equal to the call snippet's:

(() => {
  const KEY = "github-list-issues", VER = "1";
  const fn = (<FN>);
  localStorage.setItem(KEY, String(fn));
  localStorage.setItem(KEY + ":ver", VER);
  return 'stored';
})()

Returns "stored". The extractor passes through the model only here, once. Then go back to step 1.

Rate limit

api.github.com allows 60 requests per hour per IP unauthenticated (verified: x-ratelimit-limit: 60). That budget is shared by every github-* skill and by anything else on your IP hitting the API. On exhaustion the call returns the rate-limit error, wait, do not retry in a loop.

Pull requests

GitHub's issues endpoint returns pull requests too, the API treats a PR as an issue. If you want issues only, drop the entries that carry a PR marker.

Errors

• NEEDS_STORE → extractor missing or version-mismatched in this browser; run step 2 once, then retry step 1.
• repo not found → wrong owner/repo, or private.
• rate limited → see Rate limit.
• request_failed → the fetch could not run from this tab.

Success assertion

{ "type": "json", "jsonPath": "count" }