first commit

Author: R4ph-t

.github/workflows/sync-skills.yml

@@ -0,0 +1,35 @@
+name: Sync skills from render-oss/skills
+
+on:
+  schedule:
+    - cron: "0 6 * * *"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout plugin repo
+        uses: actions/checkout@v4
+
+      - name: Sync skills
+        run: ./scripts/sync-skills.sh --repo "https://github.com/render-oss/skills"
+        env:
+          GIT_TERMINAL_PROMPT: "0"
+
+      - name: Create pull request
+        uses: peter-evans/create-pull-request@v7
+        with:
+          commit-message: "Sync skills from render-oss/skills"
+          title: "Sync skills from render-oss/skills"
+          body: |
+            Automated sync of skill files from [render-oss/skills](https://github.com/render-oss/skills).
+
+            This PR was created by the `sync-skills` workflow. Review the changes and merge when ready.
+          branch: sync-skills
+          labels: skills-sync
+          delete-branch: true

.gitignore

@@ -0,0 +1,2 @@
+/dist
+/node_modules

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Render
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -0,0 +1,152 @@
+# Render OpenCode Plugin
+
+Use Render from OpenCode to deploy apps, validate Blueprints, debug failed deploys, monitor services, and work through common platform workflows.
+
+## What you get
+
+- An npm-installable OpenCode plugin with a `render_validate_blueprint` tool
+- Automatic validation when an agent edits `render.yaml` or `render.yml`
+- Bundled Render skills for deploys, debugging, monitoring, migrations, and service configuration
+- OpenCode commands for `/deploy-to-render` and `/check-render-status`
+- A Render-focused `@render` subagent
+- Optional Render MCP server configuration
+
+## Installing the plugin
+
+Add the npm package to your OpenCode config:
+
+```json
+{
+  "$schema": "https://opencode.ai/config.json",
+  "plugin": ["@render/opencode-plugin"]
+}
+```
+
+OpenCode installs npm plugins with Bun at startup and caches them in `~/.cache/opencode/node_modules/`.
+
+## Installing skills, commands, and the agent
+
+OpenCode npm plugins can provide tools and hooks, but they don't automatically register bundled skills, commands, or agents. OpenCode discovers those files from your OpenCode config directory.
+
+Run the explicit setup command after adding the plugin:
+
+```bash
+npx @render/opencode-plugin setup
+```
+
+This opt-in step writes files to `~/.config/opencode/`:
+
+- `skills/render-*/SKILL.md`
+- `commands/deploy-to-render.md`
+- `commands/check-render-status.md`
+- `agents/render.md`
+
+The setup command doesn't overwrite existing files unless you pass `--force`.
+
+```bash
+npx @render/opencode-plugin setup --force
+```
+
+To preview changes without writing files:
+
+```bash
+npx @render/opencode-plugin setup --dry-run
+```
+
+To install into a different OpenCode config directory:
+
+```bash
+npx @render/opencode-plugin setup --config-dir ./tmp-opencode
+```
+
+## Configuring Render MCP
+
+If you want OpenCode to use Render MCP tools, run setup with `--enable-mcp`:
+
+```bash
+npx @render/opencode-plugin setup --enable-mcp
+```
+
+This merges the following server into `opencode.json`:
+
+```json
+{
+  "mcp": {
+    "render": {
+      "type": "remote",
+      "url": "https://mcp.render.com/mcp",
+      "enabled": true,
+      "oauth": false,
+      "headers": {
+        "Authorization": "Bearer {env:RENDER_API_KEY}"
+      }
+    }
+  }
+}
+```
+
+Set `RENDER_API_KEY` in your environment before using Render MCP.
+
+## Setting up the Render CLI
+
+The plugin can validate Blueprints with the Render CLI.
+
+1. Install the Render CLI:
+
+```bash
+brew install render
+```
+
+2. Authenticate:
+
+```bash
+render login
+```
+
+3. Verify access:
+
+```bash
+render whoami -o json
+```
+
+If `render whoami -o json` fails, fix authentication before relying on live Render workflows in OpenCode.
+
+## Using the plugin
+
+Good first prompts:
+
+- `Help me deploy this project to Render.`
+- `Validate my render.yaml for Render.`
+- `Debug a failed Render deployment.`
+- `How are my Render services doing?`
+
+You can also run:
+
+```text
+/deploy-to-render
+/check-render-status
+```
+
+## Maintainer workflow
+
+Refresh bundled skills from `render-oss/skills`:
+
+```bash
+./scripts/sync-skills.sh
+```
+
+Use a different source repo or subdirectory:
+
+```bash
+./scripts/sync-skills.sh --repo https://github.com/render-oss/skills --subdir skills
+```
+
+Verify the package before publishing:
+
+```bash
+npm run check
+```
+
+## License
+
+MIT. See [LICENSE](LICENSE).

assets/logo/logo.svg

@@ -0,0 +1,23 @@
+---
+description: Render deployment specialist that helps deploy, configure, debug, and monitor applications on Render.
+mode: subagent
+permission:
+  skill:
+    render-*: allow
+---
+
+# Render Assistant
+
+You are a deployment specialist for Render. Use the available Render skills for detailed workflows.
+
+Core Render constraints:
+
+- Bind HTTP servers to `0.0.0.0:$PORT`.
+- Treat the filesystem as ephemeral unless a persistent disk is explicitly configured.
+- Use `render.yaml` Blueprints for repeatable multi-resource setups.
+- Mark secrets with `sync: false` instead of committing plaintext values.
+- Prefer internal service URLs for traffic between Render services in the same environment.
+
+When live Render access is needed, prefer Render MCP tools if the user has configured them. Otherwise use the Render CLI and explain any missing setup.
+
+When no specific Render skill applies, refer to the Render docs at https://render.com/docs.

assets/opencode/agents/render.md

@@ -0,0 +1,8 @@
+---
+description: Check the health and status of Render services.
+agent: render
+---
+
+Use the `render-monitor` skill to check Render service health, deploy status, logs, and metrics.
+
+Prefer Render MCP tools when configured. Otherwise use the Render CLI and explain any missing credentials or setup steps.

assets/opencode/commands/check-render-status.md

@@ -0,0 +1,8 @@
+---
+description: Deploy the current project to Render.
+agent: render
+---
+
+Use the `render-deploy` skill to deploy this project to Render.
+
+Analyze the codebase, choose the right Render service shape, create or update `render.yaml` when repeatability matters, validate the Blueprint, and provide the next deploy steps.