agentleFS
tethertotetherto/qvac/.agents/skills/qv-devops-runner-queue/SKILL.md

qv-devops-runner-queue

Skill697 starsChanged 18 days agoApache-2.0View on GitHub

Inspect GitHub Actions self-hosted runner queues when a developer provides a run URL, job URL, runner label, or reports a blocked CI job, or invokes /qv-devops-runner-queue.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the read-only helper once and present its Markdown output directly without reformatting or a code fence:

    line 9
  2. Very specific:

    Add --json only when requested.

    line 19
  3. Very specific:

    If gh is missing or unauthenticated, report the helper error.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “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

GitHub Actions Runner Queue

Run the read-only helper once and present its Markdown output directly without reformatting or a code fence:

node .agents/skills/qv-devops-runner-queue/scripts/inspect-runner-queue.mjs \
  "<job-url|run-url|runner-label>" \
  --repo "owner/repo"

For labels, --repo defaults to tetherto/qvac; URLs supply their repository. Add --json only when requested. Prefer a job URL for its complete scheduling labels. A run URL must contain exactly one active self-hosted job; otherwise show the helper's candidates and ask for a job URL.

If gh is missing or unauthenticated, report the helper error; never start authentication. Do not repeat a query unless the user requests a refresh.

The helper only makes GitHub GET requests. Never cancel, rerun, change runner state, or mutate a repository. Cancellation affects the whole run and requires a separate inspection and confirmation.

Interpretation:

  • job URLs match the complete label set; label input matches exact membership;
  • running order is oldest-started; queued order is an estimate from created_at;
  • durations may include dependencies, gates, or concurrency delays;
  • PR and branch links use the source repository, including forks;
  • results are repository-scoped; no authoritative FIFO position or ETA exists;
  • Markdown shows ten jobs per section; --json keeps all collected jobs.

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.