render-static-sites Skill
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or Published by openai in plugins.
What is render-static-sites Skill?
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Deployment
- Documentation
- Deployment use cases
- Documentation use cases
Technical details
- Install or run with Copy skill directory
When to use render-static-sites Skill
- Use it for deployment.
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/render/skills/render-static-sites/SKILL.md
What it does
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or
Skill instructions
Render Static Sites Deploys static frontends (React, Vue, Hugo, Gatsby, Docusaurus, Jekyll, etc.) to Render's global CDN with automatic TLS, Brotli compression, HTTP/2, and DDoS protection. Free tier available. When to Use - Deploying a static site or SPA (no server-side rendering) - Choosing between a Static Site and a Web Service for a frontend - Configuring SPA fallback routing, redirects/rewrites, or custom headers - Setting up PR preview environments for a static site - Troubleshooting build failures or stale content on a CDN-hosted site For SSR frameworks (Next.js, Nuxt, SvelteKit) that need a running server, use render-web-services instead. For Blueprint authoring, see render-blueprints. Static Site vs Web Service | Need | Use | Why | |------|-----|-----| | Pure HTML/CSS/JS, SPA, docs, blog | Static Site | Free, global CDN, instant cache invalidation | | SSR (Next.js next start, Nuxt server) | Web Service | Needs a running Node/Python/etc. process | | Static export from SSR fram
Explore related resources
Frequently asked questions
What is render-static-sites?
render-static-sites is a open-source AI agent skill with Copy skill directory. Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews.
Who is render-static-sites best for?
render-static-sites is best for reusing agent instructions, scripts, and references, deployment workflows, documentation workflows.
How do I install render-static-sites?
Install or run render-static-sites using Copy skill directory. Check render-static-sites for the latest setup command.
Is render-static-sites actively maintained?
render-static-sites may need a closer maintenance check before production use.
Auto-fetched from GitHub.
