[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BCZFY2WV55RPBYEH0PSWGX":3,"skill-same:01M7BCZFY2WV55RPBYEH0PSWGX":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7BCZFY2WV55RPBYEH0PSWGX","render-debug",null,"Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-debug\ndescription: Debug failed Render deployments by analyzing logs, metrics, and database state. Identifies errors (missing env vars, port binding, OOM, etc.) and suggests fixes. Use when deployments fail, services won't start, or users mention errors, logs, or debugging.\nlicense: MIT\ncompatibility: Requires Render MCP tools or CLI\nmetadata:\n  author: Render\n  version: \"1.1.0\"\n  category: debugging\n---\n\n# Debug Render Deployments\n\nAnalyze deployment failures using logs, metrics, and database queries. Identify root causes and apply fixes.\n\n## When to Use This Skill\n\nActivate this skill when:\n- Deployment fails on Render\n- Service won't start or keeps crashing\n- User mentions errors, logs, or debugging\n- Health checks are timing out\n- Application errors in production\n- Performance issues (slow responses)\n- Database connection problems\n\n## Prerequisites\n\n**MCP tools (preferred):** Test with `list_services()` - provides structured data\n\n**CLI (fallback):** `render --version` - use if MCP tools unavailable\n\n**Authentication:** For MCP, use an API key (set in the MCP config or via the `RENDER_API_KEY` env var, depending on tool). For CLI, verify with `render whoami -o json`.\n\n**Workspace:** `get_selected_workspace()` or `render workspace current -o json`\n\n> **Note:** MCP tools require the Render MCP server. If unavailable, use the CLI for logs and deploy status; metrics and structured database queries require MCP.\n\n## MCP Setup\n\nIf `list_services()` fails, set up the Render MCP server. For detailed per-tool walkthroughs, see **render-mcp**.\n\n**Quick setup:** Add the Render MCP server to your AI tool's MCP config:\n- **URL:** `https:\u002F\u002Fmcp.render.com\u002Fmcp`\n- **Auth header:** `Authorization: Bearer \u003CYOUR_API_KEY>`\n- **API key:** `https:\u002F\u002Fdashboard.render.com\u002Fu\u002F*\u002Fsettings#api-keys`\n\nAfter configuring, restart your tool and retry `list_services()`. Then set your workspace with `list_workspaces()` \u002F `get_selected_workspace()`.\n\n---\n\n## Debugging Workflow\n\n### Step 1: Identify Failed Service\n\n```\nlist_services()\n```\n\nIf MCP isn't configured, ask whether to set it up (preferred) or continue with CLI. Then proceed.\n\nLook for services with failed status. Get details:\n\n```\nget_service(serviceId: \"\u003Cid>\")\n```\n\n### Step 2: Retrieve Logs\n\n**Build\u002FDeploy Logs (most failures):**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], type: [\"build\"], limit: 200)\n```\n\n**Runtime Error Logs:**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], level: [\"error\"], limit: 100)\n```\n\n**Search for Specific Errors:**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], text: [\"KeyError\", \"ECONNREFUSED\"], limit: 50)\n```\n\n**HTTP Error Logs:**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], statusCode: [\"500\", \"502\", \"503\"], limit: 50)\n```\n\n### Step 3: Analyze Error Patterns\n\nMatch log errors against known patterns:\n\n| Error | Log Pattern | Common Fix |\n|-------|-------------|------------|\n| **MISSING_ENV_VAR** | `KeyError`, `not defined` | Add to render.yaml or `update_environment_variables` |\n| **PORT_BINDING** | `EADDRINUSE` | Use `0.0.0.0:$PORT` |\n| **MISSING_DEPENDENCY** | `Cannot find module` | Add to package.json\u002Frequirements.txt |\n| **DATABASE_CONNECTION** | `ECONNREFUSED :5432` | Check DATABASE_URL, DB status |\n| **HEALTH_CHECK** | `Health check timeout` | Add \u002Fhealth endpoint, check port binding |\n| **OUT_OF_MEMORY** | `heap out of memory`, exit 137 | Optimize memory or upgrade plan |\n| **BUILD_FAILURE** | `Command failed` | Fix build command or dependencies |\n\nFull error catalog: [references\u002Ferror-patterns.md](references\u002Ferror-patterns.md)\n\n**If errors repeat across deploys:** Switch from incremental fixes to a broader sweep. Scan the codebase\u002Fconfig for all likely causes in that error class (related env vars, build config, dependencies, or type errors) and address them together before the next redeploy.\n\n### Step 4: Check Metrics (Performance Issues)\n\nFor crashes, slow responses, or resource issues:\n\n```\nget_metrics(\n  resourceId: \"\u003Cservice-id>\",\n  metricTypes: [\"cpu_usage\", \"memory_usage\", \"memory_limit\"]\n)\n```\n\n```\nget_metrics(\n  resourceId: \"\u003Cservice-id>\",\n  metricTypes: [\"http_latency\"],\n  httpLatencyQuantile: 0.95\n)\n```\n\nDetailed metrics guide: [references\u002Fmetrics-debugging.md](references\u002Fmetrics-debugging.md)\n\n### Step 5: Debug Database Issues\n\nFor database-related errors:\n\n```\n# Check database status\nlist_postgres_instances()\n\n# Check connections\nget_metrics(resourceId: \"\u003Cpostgres-id>\", metricTypes: [\"active_connections\"])\n\n# Query directly\nquery_render_postgres(\n  postgresId: \"\u003Cpostgres-id>\",\n  sql: \"SELECT state, count(*) FROM pg_stat_activity GROUP BY state\"\n)\n```\n\nDetailed database guide: [references\u002Fdatabase-debugging.md](references\u002Fdatabase-debugging.md)\n\n### Step 6: Apply Fix\n\n**For environment variables:**\n```\nupdate_environment_variables(\n  serviceId: \"\u003Cservice-id>\",\n  envVars: [{\"key\": \"MISSING_VAR\", \"value\": \"value\"}]\n)\n```\n\n**For code changes:**\n1. Edit the source file\n2. Commit and push\n3. Deploy triggers automatically (if auto-deploy enabled)\n\n### Step 7: Verify Fix\n\n```\n# Check deploy status\nlist_deploys(serviceId: \"\u003Cservice-id>\", limit: 1)\n\n# Check for new errors\nlist_logs(resource: [\"\u003Cservice-id>\"], level: [\"error\"], limit: 20)\n\n# Check metrics\nget_metrics(resourceId: \"\u003Cservice-id>\", metricTypes: [\"http_request_count\"])\n```\n\n---\n\n## Quick Workflows\n\nPre-built debugging sequences for common scenarios:\n\n| Scenario | Workflow |\n|----------|----------|\n| Deploy failed | `list_deploys` → `list_logs(type: build)` → fix → redeploy |\n| App crashing | `list_logs(level: error)` → `get_metrics(memory)` → fix |\n| App slow | `get_metrics(http_latency)` → `get_metrics(cpu)` → `query_postgres` |\n| DB connection | `list_postgres` → `get_metrics(connections)` → `query_postgres` |\n| Post-deploy check | `list_deploys` → `list_logs(error)` → `get_metrics` |\n\nDetailed workflows: [references\u002Fquick-workflows.md](references\u002Fquick-workflows.md)\n\n---\n\n## Quick Reference\n\n### MCP Tools\n\n```\n# Service Discovery\nlist_services()\nget_service(serviceId: \"\u003Cid>\")\nlist_postgres_instances()\n\n# Logs\nlist_logs(resource: [\"\u003Cid>\"], level: [\"error\"], limit: 100)\nlist_logs(resource: [\"\u003Cid>\"], type: [\"build\"], limit: 200)\nlist_logs(resource: [\"\u003Cid>\"], text: [\"search\"], limit: 50)\n\n# Metrics\nget_metrics(resourceId: \"\u003Cid>\", metricTypes: [\"cpu_usage\", \"memory_usage\"])\nget_metrics(resourceId: \"\u003Cid>\", metricTypes: [\"http_latency\"], httpLatencyQuantile: 0.95)\n\n# Database\nquery_render_postgres(postgresId: \"\u003Cid>\", sql: \"SELECT ...\")\n\n# Deployments\nlist_deploys(serviceId: \"\u003Cid>\", limit: 5)\n\n# Environment Variables\nupdate_environment_variables(serviceId: \"\u003Cid>\", envVars: [{key, value}])\n```\n\n### CLI Commands (Fallback)\n\n```bash\nrender services -o json\nrender logs -r \u003Cservice-id> --level error -o json\nrender logs -r \u003Cservice-id> --tail -o text\nrender deploys create \u003Cservice-id> --wait\n```\n\n---\n\n## References\n\n- **Error patterns:** [references\u002Ferror-patterns.md](references\u002Ferror-patterns.md)\n- **Metrics debugging:** [references\u002Fmetrics-debugging.md](references\u002Fmetrics-debugging.md)\n- **Database debugging:** [references\u002Fdatabase-debugging.md](references\u002Fdatabase-debugging.md)\n- **Quick workflows:** [references\u002Fquick-workflows.md](references\u002Fquick-workflows.md)\n- **Log analysis:** [references\u002Flog-analysis.md](references\u002Flog-analysis.md)\n- **Troubleshooting:** [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md)\n\n## Related Skills\n\n- **render-deploy** — Deploy new applications to Render\n- **render-monitor** — Ongoing service health monitoring\n- **render-mcp** — MCP server setup and tool catalog\n","# Debug Render Deployments\n\nAnalyze deployment failures using logs, metrics, and database queries. Identify root causes and apply fixes.\n\n## When to Use This Skill\n\nActivate this skill when:\n- Deployment fails on Render\n- Service won't start or keeps crashing\n- User mentions errors, logs, or debugging\n- Health checks are timing out\n- Application errors in production\n- Performance issues (slow responses)\n- Database connection problems\n\n## Prerequisites\n\n**MCP tools (preferred):** Test with `list_services()` - provides structured data\n\n**CLI (fallback):** `render --version` - use if MCP tools unavailable\n\n**Authentication:** For MCP, use an API key (set in the MCP config or via the `RENDER_API_KEY` env var, depending on tool). For CLI, verify with `render whoami -o json`.\n\n**Workspace:** `get_selected_workspace()` or `render workspace current -o json`\n\n> **Note:** MCP tools require the Render MCP server. If unavailable, use the CLI for logs and deploy status; metrics and structured database queries require MCP.\n\n## MCP Setup\n\nIf `list_services()` fails, set up the Render MCP server. For detailed per-tool walkthroughs, see **render-mcp**.\n\n**Quick setup:** Add the Render MCP server to your AI tool's MCP config:\n- **URL:** `https:\u002F\u002Fmcp.render.com\u002Fmcp`\n- **Auth header:** `Authorization: Bearer \u003CYOUR_API_KEY>`\n- **API key:** `https:\u002F\u002Fdashboard.render.com\u002Fu\u002F*\u002Fsettings#api-keys`\n\nAfter configuring, restart your tool and retry `list_services()`. Then set your workspace with `list_workspaces()` \u002F `get_selected_workspace()`.\n\n---\n\n## Debugging Workflow\n\n### Step 1: Identify Failed Service\n\n```\nlist_services()\n```\n\nIf MCP isn't configured, ask whether to set it up (preferred) or continue with CLI. Then proceed.\n\nLook for services with failed status. Get details:\n\n```\nget_service(serviceId: \"\u003Cid>\")\n```\n\n### Step 2: Retrieve Logs\n\n**Build\u002FDeploy Logs (most failures):**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], type: [\"build\"], limit: 200)\n```\n\n**Runtime Error Logs:**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], level: [\"error\"], limit: 100)\n```\n\n**Search for Specific Errors:**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], text: [\"KeyError\", \"ECONNREFUSED\"], limit: 50)\n```\n\n**HTTP Error Logs:**\n```\nlist_logs(resource: [\"\u003Cservice-id>\"], statusCode: [\"500\", \"502\", \"503\"], limit: 50)\n```\n\n### Step 3: Analyze Error Patterns\n\nMatch log errors against known patterns:\n\n| Error | Log Pattern | Common Fix |\n|-------|-------------|------------|\n| **MISSING_ENV_VAR** | `KeyError`, `not defined` | Add to render.yaml or `update_environment_variables` |\n| **PORT_BINDING** | `EADDRINUSE` | Use `0.0.0.0:$PORT` |\n| **MISSING_DEPENDENCY** | `Cannot find module` | Add to package.json\u002Frequirements.txt |\n| **DATABASE_CONNECTION** | `ECONNREFUSED :5432` | Check DATABASE_URL, DB status |\n| **HEALTH_CHECK** | `Health check timeout` | Add \u002Fhealth endpoint, check port binding |\n| **OUT_OF_MEMORY** | `heap out of memory`, exit 137 | Optimize memory or upgrade plan |\n| **BUILD_FAILURE** | `Command failed` | Fix build command or dependencies |\n\nFull error catalog: [references\u002Ferror-patterns.md](references\u002Ferror-patterns.md)\n\n**If errors repeat across deploys:** Switch from incremental fixes to a broader sweep. Scan the codebase\u002Fconfig for all likely causes in that error class (related env vars, build config, dependencies, or type errors) and address them together before the next redeploy.\n\n### Step 4: Check Metrics (Performance Issues)\n\nFor crashes, slow responses, or resource issues:\n\n```\nget_metrics(\n  resourceId: \"\u003Cservice-id>\",\n  metricTypes: [\"cpu_usage\", \"memory_usage\", \"memory_limit\"]\n)\n```\n\n```\nget_metrics(\n  resourceId: \"\u003Cservice-id>\",\n  metricTypes: [\"http_latency\"],\n  httpLatencyQuantile: 0.95\n)\n```\n\nDetailed metrics guide: [references\u002Fmetrics-debugging.md](references\u002Fmetrics-debugging.md)\n\n### Step 5: Debug Database Issues\n\nFor database-related errors:\n\n```\n# Check database status\nlist_postgres_instances()\n\n# Check connections\nget_metrics(resourceId: \"\u003Cpostgres-id>\", metricTypes: [\"active_connections\"])\n\n# Query directly\nquery_render_postgres(\n  postgresId: \"\u003Cpostgres-id>\",\n  sql: \"SELECT state, count(*) FROM pg_stat_activity GROUP BY state\"\n)\n```\n\nDetailed database guide: [references\u002Fdatabase-debugging.md](references\u002Fdatabase-debugging.md)\n\n### Step 6: Apply Fix\n\n**For environment variables:**\n```\nupdate_environment_variables(\n  serviceId: \"\u003Cservice-id>\",\n  envVars: [{\"key\": \"MISSING_VAR\", \"value\": \"value\"}]\n)\n```\n\n**For code changes:**\n1. Edit the source file\n2. Commit and push\n3. Deploy triggers automatically (if auto-deploy enabled)\n\n### Step 7: Verify Fix\n\n```\n# Check deploy status\nlist_deploys(serviceId: \"\u003Cservice-id>\", limit: 1)\n\n# Check for new errors\nlist_logs(resource: [\"\u003Cservice-id>\"], level: [\"error\"], limit: 20)\n\n# Check metrics\nget_metrics(resourceId: \"\u003Cservice-id>\", metricTypes: [\"http_request_count\"])\n```\n\n---\n\n## Quick Workflows\n\nPre-built debugging sequences for common scenarios:\n\n| Scenario | Workflow |\n|----------|----------|\n| Deploy failed | `list_deploys` → `list_logs(type: build)` → fix → redeploy |\n| App crashing | `list_logs(level: error)` → `get_metrics(memory)` → fix |\n| App slow | `get_metrics(http_latency)` → `get_metrics(cpu)` → `query_postgres` |\n| DB connection | `list_postgres` → `get_metrics(connections)` → `query_postgres` |\n| Post-deploy check | `list_deploys` → `list_logs(error)` → `get_metrics` |\n\nDetailed workflows: [references\u002Fquick-workflows.md](references\u002Fquick-workflows.md)\n\n---\n\n## Quick Reference\n\n### MCP Tools\n\n```\n# Service Discovery\nlist_services()\nget_service(serviceId: \"\u003Cid>\")\nlist_postgres_instances()\n\n# Logs\nlist_logs(resource: [\"\u003Cid>\"], level: [\"error\"], limit: 100)\nlist_logs(resource: [\"\u003Cid>\"], type: [\"build\"], limit: 200)\nlist_logs(resource: [\"\u003Cid>\"], text: [\"search\"], limit: 50)\n\n# Metrics\nget_metrics(resourceId: \"\u003Cid>\", metricTypes: [\"cpu_usage\", \"memory_usage\"])\nget_metrics(resourceId: \"\u003Cid>\", metricTypes: [\"http_latency\"], httpLatencyQuantile: 0.95)\n\n# Database\nquery_render_postgres(postgresId: \"\u003Cid>\", sql: \"SELECT ...\")\n\n# Deployments\nlist_deploys(serviceId: \"\u003Cid>\", limit: 5)\n\n# Environment Variables\nupdate_environment_variables(serviceId: \"\u003Cid>\", envVars: [{key, value}])\n```\n\n### CLI Commands (Fallback)\n\n```bash\nrender services -o json\nrender logs -r \u003Cservice-id> --level error -o json\nrender logs -r \u003Cservice-id> --tail -o text\nrender deploys create \u003Cservice-id> --wait\n```\n\n---\n\n## References\n\n- **Error patterns:** [references\u002Ferror-patterns.md](references\u002Ferror-patterns.md)\n- **Metrics debugging:** [references\u002Fmetrics-debugging.md](references\u002Fmetrics-debugging.md)\n- **Database debugging:** [references\u002Fdatabase-debugging.md](references\u002Fdatabase-debugging.md)\n- **Quick workflows:** [references\u002Fquick-workflows.md](references\u002Fquick-workflows.md)\n- **Log analysis:** [references\u002Flog-analysis.md](references\u002Flog-analysis.md)\n- **Troubleshooting:** [references\u002Ftroubleshooting.md](references\u002Ftroubleshooting.md)\n\n## Related Skills\n\n- **render-deploy** — Deploy new applications to Render\n- **render-monitor** — Ongoing service health monitoring\n- **render-mcp** — MCP server setup and tool catalog\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.1.0","debugging","Requires Render MCP tools or CLI","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill render-debug",{"tool":40,"command":41},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill render-debug",{"tool":43,"command":44},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill render-debug","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002FSKILL.md",true,[48,54,60,64,68,72,76,80],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",257,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Flogo.svg","ASSET","资产文件",1894,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Fassets\u002Flogo.svg",{"path":61,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fdatabase-debugging.md",8964,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Freferences\u002Fdatabase-debugging.md",{"path":65,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Ferror-patterns.md",19399,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Freferences\u002Ferror-patterns.md",{"path":69,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Flog-analysis.md",10099,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Freferences\u002Flog-analysis.md",{"path":73,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fmetrics-debugging.md",6494,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Freferences\u002Fmetrics-debugging.md",{"path":77,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fquick-workflows.md",6235,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Freferences\u002Fquick-workflows.md",{"path":81,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Ftroubleshooting.md",12762,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fopenai\u002Fplugins\u002Frender\u002Fskills\u002Frender-debug\u002Freferences\u002Ftroubleshooting.md",[85,92,99,106,113,120],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":18},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]