control-center

Coordinate multi-skill orchestration and manage context across mission workflows.

2|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/skytiger6724/qwen-skills --skill control-center
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: control-center
Source: https://github.com/skytiger6724/qwen-skills/tree/main/control-center
Command: npx skills add https://github.com/skytiger6724/qwen-skills --skill control-center

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents context pollution and manual juggling of AI tools by acting as centralized mission control whenever projects span multiple specialist skills. It keeps the conversation focused and ensures only the relevant knowledge and documentation load for each phase, so no single agent overwhelms the shared history.

Core Features & Use Cases

  • Capability Mapping: Scans .gemini/skills/ and .agents/skills/ to catalog available tools and decide which specialties match the mission requirements.
  • Workflow Design: Chains research, verification, execution, and documentation phases into a cohesive plan so each activated skill contributes at the right time.
  • Context Governance: Summarizes completed steps, primes the next skill, and clears irrelevant information to keep sessions efficient even during long-running efforts.

Quick Start

Ask control-center to map the needed capabilities, activate the indicated skills, and summarize the mission status before moving forward.

Frequently Asked Questions about control-center

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

FAQPage Schema
How do I prevent context pollution when orchestrating multiple AI skills?

To prevent context pollution during multi-skill orchestration, use centralized mission control to summarize completed steps and clear irrelevant information. This context governance keeps sessions efficient by ensuring only relevant knowledge loads for each workflow phase.

How does capability mapping work for multi-skill AI workflows?

Capability mapping for multi-skill workflows scans `.gemini/skills/` and `.agents/skills/` directories to catalog available tools. It indexes SKILL.md files to decide which specialist capabilities match your mission requirements.

Do I need specific directory structures to use context management for agent governance?

Context management for agent governance requires `.gemini/skills/` and `.agents/skills/` directories. These directories must contain SKILL.md files to enable capability mapping and tool selection.

What's the best way to maintain concise context during long-running AI missions?

The best way to maintain concise context during long-running AI missions is to apply context governance. This summarizes completed steps, primes the next skill, and clears irrelevant information to keep sessions efficient.

Can I chain research and execution phases without overwhelming the shared agent history?

You can chain research and execution phases without overwhelming shared agent history by using centralized mission control. It coordinates multi-skill orchestration to prevent manual juggling of AI tools and keeps conversation focused.