autonomous-render

Renders R Markdown and Python reports with a self-correcting retry-and-validate loop.

Updated May 28, 2026
One-click install
npx skills add https://github.com/cpanse/skills --skill autonomous-render-cpanse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous-render
Source: https://github.com/cpanse/skills/tree/main/fgcz-infrastructure/skills/autonomous-render
Command: npx skills add https://github.com/cpanse/skills --skill autonomous-render-cpanse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Rendering R Markdown or Python analysis reports often fails repeatedly due to missing packages, S4 object API changes, wrong paths, or memory limits, forcing tedious multi-round debugging sessions. This Skill collapses that cycle into a single autonomous invocation that diagnoses errors, applies fixes, and re-renders without asking the user for guidance. ## Core Features & Use Cases - Pre-flight validation: Verifies input files, required R/Python packages, and disk space before rendering to avoid wasted runs. - Error pattern matching and auto-fix: Maps common failures (Seurat v5 Assay5 coercion, missing metadata columns, duplicate chunk labels, out-of-memory) to concrete fixes, then re-renders up to 5 times. - Local and SBATCH rendering: Chooses between direct rmarkdown::render for small reports and SLURM SBATCH job submission for large reports exceeding 16GB RAM. - Output validation: Checks HTML size, embedded plot counts, and NA/NULL artifacts, then optionally delivers results to gStore. - Use Case: A bioinformatician asks to render a Seurat single-cell report on the FGCZ cluster; the Skill detects a missing JoinLayers() call causing an Assay5 coercion error, patches the Rmd, submits an SBATCH job, validates the HTML, and reports the result. ## Quick Start Render the report.Rmd file in the current analysis directory, automatically fixing any errors and validating the HTML output.

Frequently Asked Questions about autonomous-render

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

FAQPage Schema
How do I render an R Markdown report on a SLURM cluster?

Submit an SBATCH job that loads the R module and runs rmarkdown::render on your Rmd file. Allocate sufficient memory with --mem-per-cpu and monitor the job with squeue and sacct until completion.

How to fix 'cannot coerce class Assay5' errors in Seurat v5?

This error occurs when code written for Seurat v4 meets the v5 layered assay structure. Add JoinLayers() before the failing operation, or use modern accessors after inspecting the object with class() and str().

When should I use SBATCH instead of local rendering?

Use SBATCH when a report takes more than 10 minutes or needs more than 16GB of RAM. Small reports can be rendered locally with a direct Rscript call to rmarkdown::render.

Why does my R Markdown render fail with 'object not found'?

This usually means a variable was defined in a chunk that has not executed yet or is hidden with include=FALSE. Check chunk execution order and ensure all dependencies are defined before use.

What are the limitations of autonomous report rendering?

The retry loop stops after 5 attempts and only fixes technical rendering issues, not analytical conclusions. If the same error persists after 2 attempts with different fixes, it reports all errors to the user for manual diagnosis.