CNOE
Official@cnoe-io
CNOE GitHub org
Agent Skills by CNOE
Showing 12 vetted skills indexed across 1 GitHub repositories.
cnoe-iolocal-integration-testing
Run end-to-end CAIPE integration tests across a local Docker Compose multi-agent stack.
cnoe-ioincident-investigation
Correlate PagerDuty incidents with Jira tickets and ArgoCD deployments into a timeline.
cnoe-ioreview-specific-pr
Analyze GitHub pull requests for security and code quality issues.
cnoe-iocluster-resource-health
Query EKS clusters via kubectl and report pod, node, and resource health.
cnoe-iooncall-handoff
Aggregate PagerDuty incidents, Jira issues, and ArgoCD deployments into a structured handoff document.
cnoe-ioreview-open-pull-requests
Aggregate open pull requests with reviewers, CI results, and age across repositories.
cnoe-iodocumentation-search
Retrieve internal documentation using Retrieval-Augmented Generation across ADRs and runbooks.
cnoe-iosprint-progress-report
Generate a structured Markdown sprint progress report from Jira data.
cnoe-iosecurity-vulnerability-report
Aggregate GitHub Dependabot, code scanning, and secret scanning alerts into prioritized vulnerability reports.
cnoe-iocheck-deployment-status
Analyze ArgoCD application sync and health statuses across clusters.
cnoe-iorelease-readiness-check
Aggregate GitHub, ArgoCD, and Jira data into a Go/No-Go release verdict.
cnoe-ioaws-cost-analysis
Analyze AWS costs by service, account, and time period.
Frequently Asked Questions About CNOE
FAQPage SchemaWhat specific operational tasks does CNOE enable?▼
CNOE enables centralized visibility into infrastructure health, cloud expenditure, and release governance. It aggregates data from ArgoCD, PagerDuty, Jira, and GitHub to produce actionable reports on cluster resource status, security vulnerability prioritization, sprint progress, and incident timelines, streamlining cross-functional engineering oversight.
Which engineering personas benefit from these capabilities?▼
Platform engineers, site reliability engineers, and engineering managers utilize these capabilities. These personas leverage the aggregated data to maintain cluster stability, manage cloud budgets, ensure release readiness, and conduct post-incident investigations without manually querying disparate systems.
What are the prerequisites for implementing these capabilities?▼
Implementation requires active connectivity to your organization's GitHub, ArgoCD, Jira, PagerDuty, and AWS environments. Users must configure the respective integrations to allow data aggregation across these platforms, ensuring the necessary read-access permissions are granted for the specific reporting modules.