{
  "schemaVersion": "1.0",
  "item": {
    "slug": "render-deploy",
    "name": "Render Deploy",
    "source": "tencent",
    "type": "skill",
    "category": "开发工具",
    "sourceUrl": "https://clawhub.ai/ivangdavila/render-deploy",
    "canonicalUrl": "https://clawhub.ai/ivangdavila/render-deploy",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/render-deploy",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=render-deploy",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "SKILL.md",
      "blueprint-workflow.md",
      "codebase-analysis.md",
      "direct-creation.md",
      "memory-template.md",
      "setup.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-05-07T17:22:31.273Z",
      "expiresAt": "2026-05-14T17:22:31.273Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report",
        "contentDisposition": "attachment; filename=\"afrexai-annual-report-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/render-deploy"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/render-deploy",
    "agentPageUrl": "https://openagent3.xyz/skills/render-deploy/agent",
    "manifestUrl": "https://openagent3.xyz/skills/render-deploy/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/render-deploy/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Setup",
        "body": "On first use, read setup.md for integration guidelines.\nIf local memory is needed, ask for consent before creating ~/render-deploy/."
      },
      {
        "title": "When to Use",
        "body": "Use this skill when the user wants to deploy, publish, or host an application on Render and needs reliable deployment execution instead of generic advice. Activate for render.yaml Blueprint generation, MCP direct service creation, runtime configuration checks, and post-deploy triage."
      },
      {
        "title": "Architecture",
        "body": "Memory lives in ~/render-deploy/. See memory-template.md for setup.\n\n~/render-deploy/\n|- memory.md                  # Stable preferences and integration choices\n|- deployment-notes.md        # Project-level deployment decisions\n|- env-inventory.md           # Required env vars and source of truth\n`- incident-log.md            # Deploy failures and resolved fixes"
      },
      {
        "title": "Quick Reference",
        "body": "Load only the minimum file needed for the current request.\n\nTopicFileSetup processsetup.mdMemory templatememory-template.mdCodebase detection and commandscodebase-analysis.mdBlueprint workflow and render.yaml rulesblueprint-workflow.mdAuthentication and MCP execution mappingdirect-creation.mdStartup and healthcheck troubleshootingtroubleshooting.md"
      },
      {
        "title": "Authentication Model",
        "body": "Before any provisioning command, confirm one of these is active:\n\nRENDER_API_KEY is exported in the shell, or\nRender CLI is authenticated (render whoami -o json)\n\nFor git-backed flows, require git and a valid remote URL. Do not attempt opaque credential discovery or unrelated environment inspection."
      },
      {
        "title": "1. Classify the Deployment Path First",
        "body": "Before proposing commands, decide which path applies:\n\nGit-backed deploy (Blueprint or Direct Creation)\nPrebuilt Docker image deploy via Dashboard/API\n\nIf the repository has no remote, stop and ask the user to push a remote or switch to dashboard image deploy."
      },
      {
        "title": "2. Choose Method by Complexity, Not Preference",
        "body": "Default decision:\n\nDirect Creation when it is one simple service and no extra infra\nBlueprint when there are multiple services, datastores, cron, workers, or reproducibility requirements\n\nIf uncertainty remains, ask one clarifying question and continue."
      },
      {
        "title": "3. Verify Prerequisites Before Any Deploy Action",
        "body": "Run checks in this order:\n\ngit remote -v for source availability\nMCP availability (list_services())\nCLI fallback readiness (render --version, render whoami -o json)\nActive workspace context (MCP or CLI)\nAuthentication presence (RENDER_API_KEY or authenticated CLI session)\n\nDo not proceed to deployment steps when prerequisites are missing."
      },
      {
        "title": "4. Treat render.yaml as Executable Infrastructure",
        "body": "When using Blueprint:\n\nDeclare all required env vars\nMark user-provided secrets with sync: false\nPrefer plan: free unless user requests another plan\nMatch service type and runtime to the actual app behavior\n\nAfter creating the file, validate before push."
      },
      {
        "title": "5. Require Push Before Deeplink Handoff",
        "body": "Before sharing a Render Blueprint deeplink, confirm render.yaml is committed and pushed to the remote branch. If not pushed, the Dashboard flow will fail to discover the configuration."
      },
      {
        "title": "6. Verify the Deployment and Close With Evidence",
        "body": "After deployment:\n\nConfirm latest deploy status is live\nCheck health endpoint response\nReview recent error logs\nValidate required env vars and port binding (0.0.0.0:$PORT)\n\nIf failures exist, run one-fix-at-a-time triage from troubleshooting.md."
      },
      {
        "title": "Common Traps",
        "body": "Starting deploy without a git remote -> Blueprint and MCP git-backed flows fail immediately.\nPicking Direct Creation for multi-service systems -> Missing workers/datastores and fragmented setup.\nForgetting sync: false on secrets -> Broken deploys or accidental secret exposure in config.\nUsing localhost binding instead of 0.0.0.0:$PORT -> Health checks fail even when process is running.\nRedeploying repeatedly without root-cause fix -> Noisy failures and delayed resolution."
      },
      {
        "title": "External Endpoints",
        "body": "EndpointData SentPurposehttps://dashboard.render.comRepository URL, service config, env key namesBlueprint apply flow and dashboard provisioninghttps://mcp.render.comService creation/config requests and workspace-scoped metadataMCP direct provisioninghttps://api.render.comDeployment metadata, logs, service status (via CLI/API)Validation and operational checks\n\nNo other endpoints should be used unless the user requests an explicit integration."
      },
      {
        "title": "Security & Privacy",
        "body": "Data that leaves your machine:\n\nRepository URL and deployment metadata sent to Render services.\nEnvironment variable names and provided values when the user explicitly sets them.\n\nData that stays local:\n\nPreferences and deployment history in ~/render-deploy/ if the user accepts memory.\nLocal codebase inspection outputs and interim analysis notes.\n\nThis skill does NOT:\n\nRead unrelated credentials outside the deployment context.\nScrape credentials from shell history, dotfiles, or unrelated config paths.\nSend project files to undeclared third-party endpoints.\nRun destructive infrastructure changes without explicit confirmation."
      },
      {
        "title": "Trust",
        "body": "By using this skill, deployment metadata and selected configuration are sent to Render services. Only use it if you trust Render with this operational data."
      },
      {
        "title": "Related Skills",
        "body": "Install with clawhub install <slug> if user confirms:\n\ndeploy - General deployment planning and release execution.\ndevops - CI/CD, infrastructure workflows, and ops coordination.\ndocker - Container packaging and runtime configuration.\nci-cd - Pipeline automation and release validation stages.\nnodejs - Runtime-specific app configuration and startup tuning."
      },
      {
        "title": "Feedback",
        "body": "If useful: clawhub star render-deploy\nStay updated: clawhub sync"
      }
    ],
    "body": "Setup\n\nOn first use, read setup.md for integration guidelines. If local memory is needed, ask for consent before creating ~/render-deploy/.\n\nWhen to Use\n\nUse this skill when the user wants to deploy, publish, or host an application on Render and needs reliable deployment execution instead of generic advice. Activate for render.yaml Blueprint generation, MCP direct service creation, runtime configuration checks, and post-deploy triage.\n\nArchitecture\n\nMemory lives in ~/render-deploy/. See memory-template.md for setup.\n\n~/render-deploy/\n|- memory.md                  # Stable preferences and integration choices\n|- deployment-notes.md        # Project-level deployment decisions\n|- env-inventory.md           # Required env vars and source of truth\n`- incident-log.md            # Deploy failures and resolved fixes\n\nQuick Reference\n\nLoad only the minimum file needed for the current request.\n\nTopic\tFile\nSetup process\tsetup.md\nMemory template\tmemory-template.md\nCodebase detection and commands\tcodebase-analysis.md\nBlueprint workflow and render.yaml rules\tblueprint-workflow.md\nAuthentication and MCP execution mapping\tdirect-creation.md\nStartup and healthcheck troubleshooting\ttroubleshooting.md\nAuthentication Model\n\nBefore any provisioning command, confirm one of these is active:\n\nRENDER_API_KEY is exported in the shell, or\nRender CLI is authenticated (render whoami -o json)\n\nFor git-backed flows, require git and a valid remote URL. Do not attempt opaque credential discovery or unrelated environment inspection.\n\nCore Rules\n1. Classify the Deployment Path First\n\nBefore proposing commands, decide which path applies:\n\nGit-backed deploy (Blueprint or Direct Creation)\nPrebuilt Docker image deploy via Dashboard/API\n\nIf the repository has no remote, stop and ask the user to push a remote or switch to dashboard image deploy.\n\n2. Choose Method by Complexity, Not Preference\n\nDefault decision:\n\nDirect Creation when it is one simple service and no extra infra\nBlueprint when there are multiple services, datastores, cron, workers, or reproducibility requirements\n\nIf uncertainty remains, ask one clarifying question and continue.\n\n3. Verify Prerequisites Before Any Deploy Action\n\nRun checks in this order:\n\ngit remote -v for source availability\nMCP availability (list_services())\nCLI fallback readiness (render --version, render whoami -o json)\nActive workspace context (MCP or CLI)\nAuthentication presence (RENDER_API_KEY or authenticated CLI session)\n\nDo not proceed to deployment steps when prerequisites are missing.\n\n4. Treat render.yaml as Executable Infrastructure\n\nWhen using Blueprint:\n\nDeclare all required env vars\nMark user-provided secrets with sync: false\nPrefer plan: free unless user requests another plan\nMatch service type and runtime to the actual app behavior\n\nAfter creating the file, validate before push.\n\n5. Require Push Before Deeplink Handoff\n\nBefore sharing a Render Blueprint deeplink, confirm render.yaml is committed and pushed to the remote branch. If not pushed, the Dashboard flow will fail to discover the configuration.\n\n6. Verify the Deployment and Close With Evidence\n\nAfter deployment:\n\nConfirm latest deploy status is live\nCheck health endpoint response\nReview recent error logs\nValidate required env vars and port binding (0.0.0.0:$PORT)\n\nIf failures exist, run one-fix-at-a-time triage from troubleshooting.md.\n\nCommon Traps\nStarting deploy without a git remote -> Blueprint and MCP git-backed flows fail immediately.\nPicking Direct Creation for multi-service systems -> Missing workers/datastores and fragmented setup.\nForgetting sync: false on secrets -> Broken deploys or accidental secret exposure in config.\nUsing localhost binding instead of 0.0.0.0:$PORT -> Health checks fail even when process is running.\nRedeploying repeatedly without root-cause fix -> Noisy failures and delayed resolution.\nExternal Endpoints\nEndpoint\tData Sent\tPurpose\nhttps://dashboard.render.com\tRepository URL, service config, env key names\tBlueprint apply flow and dashboard provisioning\nhttps://mcp.render.com\tService creation/config requests and workspace-scoped metadata\tMCP direct provisioning\nhttps://api.render.com\tDeployment metadata, logs, service status (via CLI/API)\tValidation and operational checks\n\nNo other endpoints should be used unless the user requests an explicit integration.\n\nSecurity & Privacy\n\nData that leaves your machine:\n\nRepository URL and deployment metadata sent to Render services.\nEnvironment variable names and provided values when the user explicitly sets them.\n\nData that stays local:\n\nPreferences and deployment history in ~/render-deploy/ if the user accepts memory.\nLocal codebase inspection outputs and interim analysis notes.\n\nThis skill does NOT:\n\nRead unrelated credentials outside the deployment context.\nScrape credentials from shell history, dotfiles, or unrelated config paths.\nSend project files to undeclared third-party endpoints.\nRun destructive infrastructure changes without explicit confirmation.\nTrust\n\nBy using this skill, deployment metadata and selected configuration are sent to Render services. Only use it if you trust Render with this operational data.\n\nRelated Skills\n\nInstall with clawhub install <slug> if user confirms:\n\ndeploy - General deployment planning and release execution.\ndevops - CI/CD, infrastructure workflows, and ops coordination.\ndocker - Container packaging and runtime configuration.\nci-cd - Pipeline automation and release validation stages.\nnodejs - Runtime-specific app configuration and startup tuning.\nFeedback\nIf useful: clawhub star render-deploy\nStay updated: clawhub sync"
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/ivangdavila/render-deploy",
    "publisherUrl": "https://clawhub.ai/ivangdavila/render-deploy",
    "owner": "ivangdavila",
    "version": "1.0.0",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/render-deploy",
    "downloadUrl": "https://openagent3.xyz/downloads/render-deploy",
    "agentUrl": "https://openagent3.xyz/skills/render-deploy/agent",
    "manifestUrl": "https://openagent3.xyz/skills/render-deploy/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/render-deploy/agent.md"
  }
}