cockpit

Display the ecosystem cockpit for cross-repo health, dependency graphs, and alerts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/zeyxx/CYNIC --skill cockpit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cockpit
Source: https://github.com/zeyxx/CYNIC/tree/main/.claude/skills/cockpit
Command: npx skills add https://github.com/zeyxx/CYNIC --skill cockpit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In multi-repo environments, teams struggle to gain real-time visibility into repository health, inter-project dependencies, and proactive alerts. cockpit provides a single view that aggregates health metrics, dependency graphs, and alerts for the entire ecosystem.

Core Features & Use Cases

  • Unified ecosystem visibility across all workspaces
  • Dependency graph visualization to spot breakages and cycles
  • Proactive alerts for uncommitted changes, drift, and misconfigurations
  • Quick status summaries for leadership reviews or on-call handoffs

Quick Start

Use the cockpit to view the current ecosystem status with a single invocation.

Frequently Asked Questions about cockpit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor repo health across multiple workspaces?

To monitor repo health across multiple workspaces, you can use an ecosystem cockpit that aggregates health metrics, dependency graphs, and proactive alerts into a single view for instant visibility.

How do I visualize dependency graphs to spot breakages in a multi-repo environment?

Visualizing dependency graphs in a multi-repo environment requires an ecosystem cockpit that maps inter-project dependencies to spot breakages and cycles. It provides cross-repo dependency mapping to identify structural issues.

Can I get proactive alerts for uncommitted changes and drift across repositories?

Yes, you can get proactive alerts for uncommitted changes, drift, and misconfigurations across repositories by using an ecosystem cockpit that monitors workspaces and reports status anomalies.

Does the ecosystem cockpit automatically start and store state when I begin a session?

Yes, the ecosystem cockpit ensures automatic startup at session begin and maintains persistent state storage under the ~/.cynic/cockpit/ directory, keeping cross-repo health monitoring data continuously available.

What's the best way to generate quick status summaries for on-call handoffs?

The best way to generate quick status summaries for on-call handoffs or leadership reviews is to view the current ecosystem status through a unified cockpit, providing instant visibility into overall workspace health.

Do I need a multi-repo setup to use cross-repo health monitoring?

Yes, cross-repo health monitoring is specifically applicable to multi-repo environments where operators need dependency mapping and drift detection across all workspaces, rather than single repository tracking.