Refactor check-render-status and deploy-to-render commands to simplify descriptions and streamline usage instructions.

Author: R4ph-t

plugins/render/commands/check-render-status.md

@@ -1,13 +1,8 @@
 ---
 name: check-render-status
-description: Check the health and status of Render services using MCP tools.
+description: Check the health and status of Render services.
 ---
 
 # Check Render status
 
-1. List services with `list_services()` and identify the target service.
-2. Check the latest deploy with `list_deploys(serviceId, limit: 1)` — confirm status is `live`.
-3. Scan recent error logs with `list_logs(resource: [serviceId], level: ["error"], limit: 20)`.
-4. Check resource usage with `get_metrics(resourceId, metricTypes: ["cpu_usage", "memory_usage"])`.
-5. Check response times with `get_metrics(resourceId, metricTypes: ["http_latency"], httpLatencyQuantile: 0.95)`.
-6. Report findings: deploy status, error count, CPU/memory utilization, and p95 latency.
+Follow the **render-monitor** skill to check service health, metrics, and logs.

plugins/render/commands/deploy-to-render.md

@@ -1,13 +1,8 @@
 ---
 name: deploy-to-render
-description: Deploy the current project to Render by analyzing the codebase, generating a render.yaml Blueprint, and providing a Dashboard deeplink.
+description: Deploy the current project to Render.
 ---
 
 # Deploy to Render
 
-1. Analyze the codebase to determine framework, runtime, build/start commands, environment variables, and datastores.
-2. Generate a `render.yaml` Blueprint with the appropriate services and databases.
-3. Validate the Blueprint with `render blueprints validate` if the CLI is installed.
-4. Commit and push the `render.yaml` to the repository.
-5. Provide a Dashboard deeplink: `https://dashboard.render.com/blueprint/new?repo=<REPO_URL>`.
-6. Remind the user to fill in secret environment variables marked with `sync: false`.
+Follow the **render-deploy** skill to deploy this project.