polylane
v1.0.0Investigate production, assess change impact, and automate operations with Polylane.
By Coreplane LabsLicense: MIT1 GitHub starsUpdated 6 days ago
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 17, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install polylane for Codex and Claude Code
codex plugin marketplace add coreplanelabs/skills
codex plugin marketplace upgrade polylane
codex plugin add polylane@polylanePaste and run these commands in a terminal with Codex. They add and refresh the polylane catalog, then install this plugin.
Compatibility: the page URL and API slug “polylane” remain stable.
- Codex:
polylane@agent-plugin-marketplace→polylane@polylane
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/coreplanelabs/skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/polylane/SKILL.md├── skills/polylane-automations/SKILL.md├── skills/polylane-cli/SKILL.md└── .mcp.json
Included Skills3
Investigate production and assess production impact with the Polylane platform. Use when debugging anything live — a production issue, outage, error spike, latency regression, or failing deploy; root-causing from logs, metrics, traces, or alerts; answering "what broke", "what changed", or "is prod affected"; exploring cloud infrastructure, services, or dependency topology; and for on-call triage, postmortems, rollbacks, and remediation. Also use BEFORE making or shipping any code or infrastructure change, to check its blast radius against what is actually running. Covers the full platform — context graph (clouds, integrations, topology, repositories, memories), detection (issues, change intelligence, advisories, scans), investigation (threads, feed, escalations), and remediation (autofix, automations, skills) — plus connecting a stack and querying it. Retrieve from Polylane docs — never guess commands or schemas.
Author, scope, and operate Polylane automations — unattended agent runs wired as trigger → instructions → tools → actions → destinations. Use when the user wants something to happen without them — "whenever X happens", "on every deploy", "every morning", "auto-rollback if it breaks" — including reacting to alerts, incidents, deploys, pushes, cron schedules, or webhooks; rolling back bad deployments automatically; auto-triaging alerts into issues; scheduled reports and recurring production health checks; incident-response automation; and routing results to Slack, email, or webhooks. Retrieve from Polylane docs — never guess commands or schemas.
Drive Polylane from the terminal with the `polylane` CLI — investigate production issues, incidents, and alerts; search logs and query metrics; explore cloud resources, services, and dependency graphs; check what's deployed; search code; save memories; run automations from a catalog; connect observability tools and cloud accounts; and drive threads with the Polylane agent. Use when the work happens in a shell or script, when the user asks for the CLI, or when the Polylane MCP tools are not connected — to debug prod, look up a service or resource, search the codebase, manage integrations, connect a cloud provider, or talk to the Polylane agent. Retrieve (`--help`, `polylane api describe`) — never guess commands or flags.
MCP servers2
- url
- https://mcp.polylane.com/mcp
- url
- https://docs.polylane.com/mcp
Plugin manifests2
{
"name": "polylane",
"version": "1.0.0",
"description": "Investigate production, assess change impact, and automate operations with Polylane.",
"author": {
"name": "Coreplane Labs",
"email": "[email protected]",
"url": "https://polylane.com"
},
"homepage": "https://docs.polylane.com/coding-agents/plugins",
"repository": "https://github.com/coreplanelabs/skills",
"keywords": [
"polylane",
"observability",
"incidents",
"sre",
"devops",
"automations",
"context-graph"
],
"skills": "./skills/",
"mcpServers": "./.mcp.json",
"interface": {
"displayName": "Polylane",
"shortDescription": "Investigate production issues",
"longDescription": "Connect Codex to Polylane's production context graph, telemetry, code, incidents, and automations. Investigate live issues, assess blast radius before changes, and build reviewed operational workflows.",
"developerName": "Coreplane Labs",
"category": "Developer Tools",
"capabilities": [
"Read",
"Write"
],
"websiteURL": "https://polylane.com",
"privacyPolicyURL": "https://polylane.com/privacy/",
"termsOfServiceURL": "https://polylane.com/terms/",
"defaultPrompt": [
"Set up Polylane for this project and connect the production stack.",
"Investigate this production issue with Polylane and summarize the evidence.",
"Build a scoped Polylane automation for this recurring operational task."
],
"brandColor": "#15151A",
"composerIcon": "./assets/icon.png",
"logo": "./assets/logo.png"
}
}{
"name": "polylane",
"displayName": "Polylane",
"version": "1.0.0",
"description": "Investigate production issues and assess change impact with Polylane: live logs, metrics, traces, deployments, the cloud infrastructure context graph, automations, and the polylane CLI",
"author": {
"name": "Coreplane Labs",
"email": "[email protected]",
"url": "https://polylane.com"
},
"homepage": "https://docs.polylane.com/coding-agents/plugins",
"repository": "https://github.com/coreplanelabs/skills",
"license": "MIT",
"keywords": [
"polylane",
"observability",
"incidents",
"investigations",
"automations",
"sre",
"devops",
"context-graph",
"mcp",
"cli"
]
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[polylane on Agent Plugins Marketplace](https://pluginsmp.com/plugins/polylane)