source-command-security-report-triage
Skill989 starsChanged 6 days agoMITView on GitHub
Migrated source command `security-report-triage`
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- churchcrmSkill
- source-command-church-reviewSkill
- source-command-pr-reviewSkill
- source-command-prune-branchesSkill
- source-command-push-prSkill
- source-command-repo-healthSkill
- source-command-security-advisorySkill
The file
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
- Very specific: line 8
Use this skill when the user asks to run the migrated source command security-report-triage.
- Very specific: line 14
Run the vulnerability-report read defined in .agents/skills/churchcrm/security-report-triage.md: does the claimed code path exist, what are …
- Distinctive: line 16
Read that skill file now and follow it exactly, in order.
≈ “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.
Files
source-command-security-report-triage
Use this skill when the user asks to run the migrated source command security-report-triage.
Command Template
Security Report Triage
Run the vulnerability-report read defined in .agents/skills/churchcrm/security-report-triage.md: does the claimed code path exist, what are the real preconditions, is there a reproducible proof of concept, and does the stated severity match the evidence.
Read that skill file now and follow it exactly, in order. The output is a maintainer-only triage read (grounded / plausible-unverified / inflated / not-a-vulnerability) — never a reply to the reporter, and nothing here gets posted publicly.
Paste or point at the report to triage when invoking this.
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.

