writing-r-code

Creates WCAG and BestBet compliant, reusable, accessible HTML5/CSS3/JS code with ARIA and SEO optimization.

5|1|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/wolf5996/agentic-skills --skill writing-r-code
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-r-code
Source: https://github.com/wolf5996/agentic-skills/tree/main/writing-r-code
Command: npx skills add https://github.com/wolf5996/agentic-skills --skill writing-r-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents brittle, outdated, or non-reproducible R code in scRNA-seq and Bioconductor/Seurat workflows by enforcing consistent project conventions and verifying package APIs before function calls.

Core Features & Use Cases

  • Context7-verified package API calls: Perform required lookups before calling API-sensitive functions across Seurat, Bioconductor, and related ecosystem packages.
  • Tidyverse-first, Seurat-correct coding patterns: Use dplyr pipelines for metadata operations while keeping Seurat analysis functions in Seurat-native syntax.
  • Self-contained, executable R code chunks: Structure chunks with Libraries, Inputs, Processing, and Outputs so each chunk runs independently and writes checkpoints/figures reliably.
  • Seurat v5 layer-based workflows: Apply layer conventions such as JoinLayers() and IntegrateLayers() for multi-sample integration and downstream steps.

Quick Start

Use the writing-r-code skill to write or revise an R pipeline for Seurat v5 that saves checkpoints and generates BadranSeq-based plots while verifying every API-sensitive function call via Context7.

Frequently Asked Questions about writing-r-code

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Seurat v5 R code that handles multi-sample integration correctly?▼

When writing R code for scRNA-seq workflows, use Context7 lookups to verify function signatures before calling API-sensitive functions across Seurat, Bioconductor, and related ecosystem packages to prevent brittle scripts.

Can I use tidyverse pipelines for Seurat metadata operations without breaking analysis steps?▼

Structure Quarto QMD code chunks with Libraries, Inputs, Processing, and Outputs sections so each chunk runs independently, reliably writing checkpoints and generating deterministic outputs for scRNA-seq analysis.

Why does my R script for scRNA-seq keep breaking after package updates?▼

Standardize R scripts for scRNA-seq, Seurat v5, tidyverse, and Bioconductor workflows by enforcing consistent project conventions, verifying package APIs, and structuring self-contained chunks with deterministic outputs.

Does this approach support saving checkpoints and generating Quarto reports for dataset processing?▼

This approach distinguishes itself by enforcing tidyverse-first coding patterns alongside Seurat-native syntax, ensuring API correctness through Context7 lookups for reproducible scRNA-seq workflows.