mozillamozilla/media-skills/list-reports/SKILL.md

list-reports

Skill1 starsChanged 8 months agoMITView on GitHub

Launch a local web server and open a browser page listing all bug triage reports in ./reports, with live JS text filtering.

In this repository10 other files it gives its agents.
- bug-filing-proSkill
- bugzilla-wranglerSkill
- media-bug-triageSkill
- mozconfigSkill
- s2-validationSkill
- sec-approvalSkill
- source-permalinksSkill
- tech-docSkill
- s2Skill
- uplift-requestSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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

Distinctive:
Run the following command from the repository root:
line 34
Distinctive:
Do not do anything else. Just run the command.
line 47
Very specific:
Use the include_fields query parameter to limit response size when only a subset of fields is needed.
line 60

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

List Bug Triage Reports

Launch a local python web server that displays media-bug-triage reports from your ./reports/ folder, in a filterable and sortable browser UI.

UI

Individual rows, each dedicated to summaryzing one report - In each row, display entries with the following information from the report:

What	Color	Notes
Bug ID	Green	format: 'Bug NNNNN', linked to the bug in Bugzilla
Report generated date	Gray	Date when the report was generated
Component	Red	The component to which the bug belongs
Severity/Priority	Gray	The severity and priority of the bug
Reporter	Black	The user who reported the bug

Additionally, the browser fetches the following live properties from Bugzilla asynchronously after the page loads, and updates each row as results arrive:

What	Color	Notes
Status	Green unless RESOLVED, then Black.	The current status of the bug
Severity	Red if S1/S2, Green otherwise	The current severity of the bug
Priority	Red if P1/P2, Green otherwise	The current priority of the bug

Finally, display the report's research summary text, up to 500 characters.

Instructions

Run the following command from the repository root:

python3 .claude/skills/list-reports/server.py

The script picks a free port automatically and opens the browser. Tell the user:

The server is running and their browser should have opened automatically.
Print the url with port number (e.g. http://localhost:12345) in case the browser did not open.
Users can type in the filter box to search across bug IDs, summaries, components, severity, and report text
Users can use the Sort dropdown to sort by Bug ID, Date, Component, Reporter, Status, Severity, or Priority, and toggle ascending/descending with the arrow button
Press Ctrl+C in the terminal to stop the server when done

Do not do anything else. Just run the command.

REST API Quick Reference

Endpoint	Purpose
`GET https://bugzilla.mozilla.org/rest/bug/{id}?include_fields=id,summary,status`	Fetch id,summary, and status
`GET https://bugzilla.mozilla.org/rest/bug/{id}`	Fetch all bug fields
`GET https://bugzilla.mozilla.org/rest/bug/{id}/comment`	Fetch all comments
`GET https://bugzilla.mozilla.org/rest/bug/{id}/history`	Fetch change history
`GET https://bugzilla.mozilla.org/rest/bug/{id}/attachment`	Fetch attachment metadata
`GET https://bugzilla.mozilla.org/rest/bug?product=...&component=...&creation_time=...&summary=...`	Search bugs

Use the include_fields query parameter to limit response size when only a subset of fields is needed.

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