security-audit-r-package
Skill10 starsChanged 3 months agoMITView on GitHub
Perform comprehensive security audit of R/Bioconductor packages
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- instructions/claude.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- adr-authorSkill
- analyze-r-packageSkill
- bioc-howtoSkill
- bioc-pkg-devSkill
- bioc-pkg-finderSkill
- bioc-pkg-reviewSkill
- build-check-bioccheckSkill
- check-bioconductor-skillsSkill
- create-package-instructionsSkill
- create-skillSkill
- document-skillSkill
- improve-code-coverageSkill
- migrate-datapkg-to-zenodoSkill
- update-package-instructionsSkill
- update-r-newsSkill
- validate-skillSkill
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
- Very specific: line 28
Determine Audit Scope: Default is the entire package (DESCRIPTION, NAMESPACE, R/, src/).
- Distinctive: line 29
Fetch Audit Instructions: Read the standardized security audit instructions from:
- Distinctive: line 32
Read Files: Read all files within the defined scope.
≈ “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
security-audit-r-package
Perform comprehensive security audits of R/Bioconductor packages, identifying vulnerabilities, native code security issues, code quality problems, and dependency risks.
Usage
Invoke this skill to audit an R package:
- "Run security audit on this R package"
- "Check this package for security vulnerabilities"
- "Security audit only the R/ directory"
Prerequisites
- Working directory is an R package.
- Internet access to fetch audit instructions from the reference gist.
Process
- Determine Audit Scope: Default is the entire package (
DESCRIPTION,NAMESPACE,R/,src/). The user may specify a subset. - Fetch Audit Instructions: Read the standardized security audit instructions from: https://gist.github.com/lwaldron/0606c678e7d81b012a1b05901cf4b732 These instructions define the categories to check, standardized issue type labels, and required fields.
- Read Files: Read all files within the defined scope.
- Analyze for Issues: Review the code against the checklist defined in the gist. Address vulnerabilities, native code safety, code quality, and dependency risks.
- Generate Report: Produce a structured markdown report including findings with the required fields (Issue Type Label, Severity, Location, Description, Fix).
- Output Report: Display the report and confirm completion.
Output Format
Generate a security report tailored to the context (full package vs quick check). All reports must include:
- Standardized labels from the gist.
- Severity levels (Critical, High, Medium, Low).
- Clear indications if no issues are found.
# Security Audit Report: [Package Name]
**Scope**: [audited files/directories]
## Summary
[Brief summary of findings]
## Findings
### [Issue Title]
**Issue Type**: [Label]
**Severity**: [Level]
**Location**: [file:line]
**Description**: [Details]
**Fix**: [Recommendation]Examples
Example: Full Package Audit
User: "Run security audit on this R package" Agent:
- Confirms scope:
DESCRIPTION,NAMESPACE,R/,src/ - Fetches gist instructions and reads files.
- Analyzes for vulnerabilities and generates report. Output: A detailed report listing any High/Medium/Low issues, or a Clean status if no issues are found.
Reference: Security audit criteria defined at https://gist.github.com/lwaldron/0606c678e7d81b012a1b05901cf4b732
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.

