← Search

R package development with devtools, testthat and roxygen2
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit e20b71b
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: an R package project and an R environment with…

R package development with devtools, testthat and roxygen2

Posit-endorsed R package workflow — devtools test/document/check commands, air formatting, base-pipe style, testthat snapshot conventions, roxygen2 + pkgdown docs, and NEWS.md discipline

At a glance
What
Posit-endorsed R package workflow — devtools test/document/check commands, air formatting, base-pipe style, testthat snapshot conventions, roxygen2 + pkgdown docs, and NEWS.md discipline
Cost
Free
Needs
an R package project and an R environment with devtools, testthat and roxygen2 installed — the skill is guidance the agent follows, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

R package development with devtools, testthat and roxygen2 is a free Muse skill that teaches the Posit-endorsed R package workflow, with devtools test, document, and check commands, air formatting, base-pipe style, testthat snapshot conventions, roxygen2 and pkgdown docs, and NEWS.md discipline for packages that stay maintainable.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit e20b71b

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an R package project and an R environment with devtools, testthat and roxygen2 installed — the skill is guidance the agent follows, not software Install "R package development with devtools, testthat and roxygen2" for me. It gives my agent Simon P. Couch's R package workflow from Posit's official repo: devtools command lines (load_all, test with filters, document, check), code style (air format, base pipe |>, \() one-liners), testing conventions (snapshot tests for errors/warnings, no bare expect_true), roxygen2 docs (80-char wrap, pkgdown index sync), and NEWS.md discipline (user-facing bullets, alphabetical by function, issue references). MIT-licensed. Repository: https://raw.githubusercontent.com/posit-dev/skills/e20b71b2ab527b7c480f4f60dcce2b18df1a99ae/r-lib/r-package-development/SKILL.md Pinned version: install the code at commit e20b71b2ab527b7c480f4f60dcce2b18df1a99ae exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "r-package-development". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my R package directory; nothing else — it's a methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit e20b71b · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
e20b71b · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.