Screened · automated checks passed
r-package-check
What the author says it does
Run the full R package release gate — regenerate docs, run the test suite, run R CMD check --as-cran, and triage every ERROR / WARNING / NOTE against CRAN policy before a release or submission. Use when the user says "check my R package", "R CMD check", "is this package CRAN-ready", "run devtools::check", "prepare for CRAN submission", or points at a directory containing a DESCRIPTION file. Produces a check report + CRAN-submission checklist in `quality_reports/`.
Quoted from the skill's own SKILL.md trigger description — this is what tells
Claude when to activate it. Not yet verified by us.
Automated screening
100/100 validator score
Scored by the same rules as our free SKILL.md validator: trigger description quality, body substance, structure. Automated — a human bench test is the next step in the pipeline.
Install (unverified — review first)
git clone https://github.com/pedrohcgs/claude-code-my-workflow # skill lives at: .claude/skills/r-package-check/SKILL.md
SkillProof status
This skill is in our test queue. We install every skill in a clean environment, run a trigger battery and score output against a baseline before it earns a catalog page — the full protocol is public. Until then, treat it like any unreviewed dependency: read the SKILL.md and any scripts before installing.
Already tested in Testing & QA
- Screen Reader Testing Screen reader testing playbook for VoiceOver, NVDA, and JAWS with ARIA fixes.
- Skill Security Auditor OWASP-mapped code/secrets/config audit with working bundled scan scripts
- Web Quality Audit Lighthouse-style audit across Performance, Accessibility, SEO, and Best Practices with severity tiers.
- OSINT Methodology Structured 5-stage external recon methodology with confidence levels, severity rubric, and OpSec rules.