deploy

Render RMarkdown documents and publish them to GitHub Pages via git push to main.

5|1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/mgaldino/agents-workflow --skill deploy-mgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/mgaldino/agents-workflow/tree/main/skills-docs/deploy
Command: npx skills add https://github.com/mgaldino/agents-workflow --skill deploy-mgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Render RMarkdown documents and publish them to GitHub Pages, streamlining the end-to-end publishing workflow.

Core Features & Use Cases

  • Render a single .Rmd file to HTML or render an entire site/bookdown project.
  • Prepare output for GitHub Pages by ensuring docs/ is present, creating docs/.nojekyll if needed, and verifying docs/index.html.
  • Deploy by committing the generated docs/ content and pushing to main, with guidance to configure Pages settings.

Quick Start

Provide the path to your Rmd file or project and run the skill to render it to HTML and deploy the result to GitHub Pages.

Frequently Asked Questions about deploy

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

FAQPage Schema
How do I render RMarkdown and deploy to GitHub Pages?

To render RMarkdown and deploy to GitHub Pages, the skill renders your .Rmd files to HTML, ensures the docs/ directory is present with a .nojekyll file, and commits the output to your main branch for automated publishing.

Can I deploy an entire Bookdown or Distill project to GitHub Pages?

Yes, you can deploy Bookdown or Distill projects to GitHub Pages. The skill handles automated rendering and deployment for entire site projects, not just individual RMarkdown reports.

Do I need R and rmarkdown installed to publish RMarkdown documents?

Yes, you need R and rmarkdown installed to publish RMarkdown documents. A configured GitHub Pages repository with the output directory set to docs/ is also required for the deployment workflow to function correctly.

Why does my RMarkdown site need a .nojekyll file in the docs directory?

Your RMarkdown site needs a .nojekyll file in the docs directory to bypass Jekyll processing on GitHub Pages, ensuring your generated HTML files are served directly without being ignored by default site generation rules.

What is the best way to automate RMarkdown report publishing?

The best way to automate RMarkdown report publishing is using a deployment workflow that renders documents, verifies docs/index.html, and commits the generated content directly to your main branch for GitHub Pages hosting.