s2
Skill1 starsChanged 8 months agoMITView on GitHub
Analyse a Bugzilla bug and assess if S2 is the correct severity rating.
In this repository10 other files it gives its agents.
- bug-filing-proSkill
- bugzilla-wranglerSkill
- list-reportsSkill
- media-bug-triageSkill
- mozconfigSkill
- s2-validationSkill
- sec-approvalSkill
- source-permalinksSkill
- tech-docSkill
- uplift-requestSkill
The file
Files
S2 Skill
TODO: Brief description of the skill's purpose.
Run Configuration
TODO: Describe any settings or parameters resolved at invocation time (e.g. scope profile, input format, verbosity).
Tools Access
TODO: List tools and external services used by this skill.
Workflow
Step 1: TODO
TODO: Describe the first step.
Step 2: TODO
TODO: Describe the second step.
Output Format
TODO: Describe the expected output structure.
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
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.