Update README and plugin configuration for clarity and improved user guidance; enhance installation instructions and descriptions for Render plugin features.

Author: R4ph-t

.codex-plugin/plugin.json

@@ -1,14 +1,14 @@
 {
   "name": "render",
   "version": "0.1.0",
-  "description": "Deploy, debug, monitor, and troubleshoot Render services from Codex. Works with the Render CLI, with optional MCP for advanced workflows.",
+  "description": "Build, deploy, and troubleshoot apps on Render from Codex.",
   "author": {
     "name": "Render",
     "email": "support@render.com",
     "url": "https://render.com"
   },
-  "homepage": "https://render.com",
-  "repository": "https://github.com/render-oss/skills",
+  "homepage": "https://github.com/renderinc/render-codex-plugin",
+  "repository": "https://github.com/renderinc/render-codex-plugin",
   "license": "MIT",
   "keywords": [
     "render",
@@ -23,20 +23,22 @@
   "mcpServers": "./.mcp.json",
   "interface": {
     "displayName": "Render",
-    "shortDescription": "Deploy, debug, and monitor Render services with the Render CLI. Add MCP later for advanced workflows.",
-    "longDescription": "Deploy, debug, and monitor Render services from Codex with bundled Render skills. Start with the Render CLI for Blueprint generation, validation, logs, and troubleshooting. Add the bundled MCP server later if you want direct creation, richer monitoring, and structured queries.",
+    "shortDescription": "Build, deploy, and troubleshoot apps on Render.",
+    "longDescription": "Use Render in Codex to deploy apps, validate infrastructure, debug failures, monitor services, and work through common platform workflows.",
     "developerName": "Render",
     "category": "Developer Tools",
     "capabilities": [
       "Interactive",
       "Write"
     ],
     "websiteURL": "https://render.com/",
+    "privacyPolicyURL": "https://render.com/privacy",
+    "termsOfServiceURL": "https://render.com/terms",
     "brandColor": "#8a05ff",
     "defaultPrompt": [
-      "Help me install and authenticate the Render CLI for Render.",
-      "Debug my Render deployment with the Render CLI.",
-      "Help me deploy this project to Render."
+      "Help me deploy this project to Render.",
+      "Help me validate my render.yaml for Render.",
+      "Debug a failed Render deployment."
     ],
     "logo": "./assets/logo.svg"
   }

.github/workflows/sync-skills.yml

@@ -22,14 +22,22 @@ jobs:
           GIT_TERMINAL_PROMPT: "0"
 
       - name: Create pull request
+        id: cpr
         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).
+            Automated update of bundled skills 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.
+            Review the synced skill changes before merging.
           branch: sync-skills
           labels: skills-sync
           delete-branch: true
+
+      - name: Enable auto-merge
+        if: steps.cpr.outputs.pull-request-operation == 'created' || steps.cpr.outputs.pull-request-operation == 'updated'
+        uses: peter-evans/enable-pull-request-automerge@v3
+        with:
+          pull-request-number: ${{ steps.cpr.outputs.pull-request-number }}
+          merge-method: squash

README.md

@@ -1,109 +1,119 @@
 # Render Codex Plugin
 
-Deploy, debug, monitor, and troubleshoot applications on [Render](https://render.com) from Codex. Start with the Render CLI for the core workflows. Add MCP later for advanced workflows.
+Use Render from Codex to deploy apps, validate `render.yaml`, debug failed deploys, monitor services, and work through common platform workflows.
 
-## What it includes
+## What you get
 
-- `skills/`: Render skills derived from [render-oss/skills](https://github.com/render-oss/skills)
-- `scripts/validate-render-yaml.sh`: hook script that runs `render blueprints validate`
-- `scripts/sync-skills.sh`: manual skill sync script
-- `.mcp.json`: Render MCP server configuration using `RENDER_API_KEY`
-- `.codex-plugin/plugin.json`: Codex plugin manifest
-- `.github/workflows/sync-skills.yml`: daily skill sync workflow
-- `assets/logo.svg`: plugin logo
+- Bundled Render skills for deployment, debugging, monitoring, migrations, and workflows
+- A bundled `.mcp.json` file for the hosted Render MCP server
+- A helper script at `scripts/validate-render-yaml.sh` for `render blueprints validate`
+- Plugin metadata and assets for Codex installation
 
-## Reused from the Cursor plugin
+## Install the plugin locally
 
-This repository intentionally reuses content from the existing local Cursor Render plugin where the formats align cleanly:
+1. Copy the plugin into `~/.codex/plugins/render`:
 
-- skills
-- MCP configuration
-- validation script
-- logo asset
+```bash
+mkdir -p ~/.codex/plugins
+rsync -a ./ ~/.codex/plugins/render/
+```
 
-Cursor-specific concepts such as Cursor commands, rules, and agents are not included here because they do not map directly to Codex plugin packaging.
+2. Add the plugin to `~/.agents/plugins/marketplace.json`.
+
+If the file already exists, add the `render` entry to the existing `plugins` array.
+
+```json
+{
+  "name": "local-plugins",
+  "interface": {
+    "displayName": "Local Plugins"
+  },
+  "plugins": [
+    {
+      "name": "render",
+      "source": {
+        "source": "local",
+        "path": "./.codex/plugins/render"
+      },
+      "policy": {
+        "installation": "AVAILABLE",
+        "authentication": "ON_INSTALL"
+      },
+      "category": "Developer Tools"
+    }
+  ]
+}
+```
 
-## Use it locally in Codex
+3. Restart Codex.
+4. Open the plugin directory in Codex and install `Render` from your marketplace.
 
-This repository is the source of truth for the plugin. For local Codex use, install the plugin into the standard local plugin path at `~/plugins/render` and register it in `~/.agents/plugins/marketplace.json`.
+## Get started
 
-To refresh the local plugin after you edit this repository, run:
+Use the plugin to:
 
-```bash
-rsync -a ./ ~/plugins/render/
-```
+- Deploy a project to Render
+- Validate and troubleshoot `render.yaml`
+- Debug failed deploys and check service status
+- Work through common setup and migration tasks
 
-## Get started with the Render CLI
+Good first prompts:
+
+- `Help me deploy this project to Render.`
+- `Help me validate my render.yaml for Render.`
+- `Debug a failed Render deployment.`
 
-The plugin is useful without MCP. Start with the Render CLI for Blueprint generation, `render.yaml` validation, workflow setup, logs, deploy status, and CLI-guided troubleshooting.
+## Set up the Render CLI
+
+Many Render workflows depend on the Render CLI.
 
 1. Install the Render CLI:
 
 ```bash
 brew install render
 ```
 
-2. Authenticate the CLI:
+2. Authenticate:
 
 ```bash
 render login
 ```
 
-3. Verify the CLI is ready:
+3. Verify access:
 
 ```bash
 render whoami -o json
 ```
 
-If `render whoami -o json` fails, do not assume the CLI is usable yet. Fix authentication first.
-
-If you previously set `RENDER_API_KEY` in your shell profile, make sure it is a real key or unset it. A placeholder value can break CLI auth in misleading ways.
+If `render whoami -o json` fails, fix authentication before you rely on Render workflows in Codex.
 
-4. Start using the plugin from Codex.
+## Use the optional MCP server
 
-Good first prompts:
-
-- `Help me install and authenticate the Render CLI for Render.`
-- `Validate my render.yaml for Render.`
-- `Debug my Render deployment with the Render CLI.`
-
-## Add MCP for advanced workflows
-
-The bundled MCP server is optional. Add it if you want direct service creation, structured service enumeration, richer monitoring, or structured database queries.
-
-The plugin does not provide an API key input in the Codex plugin UI. Codex reads the bearer token for the bundled MCP server from the environment that launches Codex.
+The plugin bundles `.mcp.json` for the hosted Render MCP server. To use it, set `RENDER_API_KEY` before you start Codex.
 
-To enable MCP:
-
-1. Create a Render API key in the [Render Dashboard](https://dashboard.render.com/u/*/settings#api-keys).
-2. Quit Codex if it is already open.
-3. Launch Codex from Terminal with the key set:
+1. Create a Render API key in the [Render Dashboard](https://dashboard.render.com/).
+2. Open Account settings > API Keys.
+3. Start Codex from Terminal with the key set:
 
 ```bash
 export RENDER_API_KEY="rnd_..."
 open -a Codex
 ```
 
-4. Keep using that Terminal-launched Codex session. If you reopen Codex later from the Dock or Spotlight, it might not inherit `RENDER_API_KEY`.
-5. If you want this to persist for future launches, add the export line to your shell profile such as `~/.zshrc`, then launch Codex from a new Terminal session.
-
-Never save a placeholder like `your_render_api_key` as the value of `RENDER_API_KEY`. A bad value is worse than an unset variable because it can make auth failures look unrelated.
+4. Keep using that Terminal-launched session. If you start Codex from the Dock or Spotlight, it might not inherit `RENDER_API_KEY`.
+5. If you want the variable to persist, add it to your shell profile such as `~/.zshrc`, then start a new Terminal session.
 
-The bundled MCP server is configured in `.mcp.json` and reads `RENDER_API_KEY` through `bearer_token_env_var`.
+Never set `RENDER_API_KEY` to a placeholder value such as `your_render_api_key`. Use a real key or leave the variable unset.
 
-## Keep skills up to date
+## For maintainers
 
-Run the manual sync script to refresh `skills/` from [render-oss/skills](https://github.com/render-oss/skills):
+Run the sync script to refresh `skills/` from [render-oss/skills](https://github.com/render-oss/skills):
 
 ```bash
 ./scripts/sync-skills.sh
 ```
 
-GitHub Actions also runs `.github/workflows/sync-skills.yml` every day and opens a pull request when upstream skills change.
-
-## Publish it
-
-Push this repository to GitHub and publish it as the plugin source repository. The plugin payload lives at the repository root, not under a nested `plugins/` directory.
+GitHub Actions also runs `.github/workflows/sync-skills.yml` each day and opens a pull request when upstream skills change.
 
 ## License