Run any Skill in Manus with one click

copilot-scheduler-agent-merge

Stars20

Forks2

UpdatedApril 21, 2026 at 09:30

Use when you need to compare the staged bundled starter-agent mirror against an existing richer repo-local agent system and selectively merge approved ideas into the live workspace files.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

goodguy1963

goodguy1963/Copilot-Cockpit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	copilot-scheduler-agent-merge
description	Use when you need to compare the staged bundled starter-agent mirror against an existing richer repo-local agent system and selectively merge approved ideas into the live workspace files.
copilotCockpitSkillType	support
copilotCockpitToolNamespaces	[]
copilotCockpitWorkflowIntents	[]
copilotCockpitApprovalSensitive	true
copilotCockpitPromptSummary	Compare the staged starter-agent mirror with the live repo-local system, propose selective merges, and implement only approved changes without swapping whole trees.
copilotCockpitReadyWorkflowFlags	[]
copilotCockpitCloseoutWorkflowFlags	[]

Staged Agent Merge Skill

You have been invoked to help a user adopt ideas from the bundled starter-agent pack without replacing their existing repo-local agent system.

Instructions

Treat the live repo-local agent system as user-owned and as the source of truth. Never replace the entire live .github/agents tree with the starter pack.
Inspect the live agent-system surfaces first: .github/agents/, .github/skills/, .github/prompts/, .agents/, AGENTS.md, and any nearby *.agent.md or *.instructions.md files.
Inspect the staged starter bundle under .vscode/copilot-cockpit-support/bundled-agents/, starting with .vscode/copilot-cockpit-support/bundled-agents/manifest.json.
If the staged bundle or manifest is missing, stop and tell the user to run the Settings action Stage Bundled Agents first. Do not fall back to direct sync as part of this merge workflow.
Summarize the comparison in terms of merge candidates, not file replacement:
- role ideas worth adopting
- routing or escalation rules worth copying
- reusable skills or knowledge files worth adding
- overlapping files where only selected sections should be merged
Ask the user which changes they want to adopt. If they already indicated their selection, restate the chosen merge set before editing.
Implement only the approved live-system edits. Prefer targeted section merges, new additive files, or small refactors over broad rewrites.
Keep the staged bundle as reference material only. Do not edit the staged files unless the user explicitly asks to regenerate them through the plugin action.
After implementation, report:
- what was merged into the live system
- what stayed only in the staged reference tree
- any follow-up manual decisions still needed

When in doubt, prefer additive changes and explicit user confirmation over aggressive normalization.

More from this repository

same repository

copilot-scheduler-intro

goodguy1963/Copilot-Cockpit

Act as a detailed onboarding guide for the Copilot Cockpit plugin. Walk the user through installation, the core workflow, optional MCP/skills/agent setup, and help them decide which optional layers fit their repo.

2026-06-0220

copilot-scheduler-intro

goodguy1963/Copilot-Cockpit

2026-05-2920

copilot-scheduler-setup

goodguy1963/Copilot-Cockpit

Act as an integration planner to evaluate the workspace and plan a structured agent ecosystem. Use this skill when the user asks to integrate or set up the scheduler orchestrator.

2026-05-0720

prefab-mcp

goodguy1963/Copilot-Cockpit

Use when an agent needs to work with Prefab dynamic config or feature flags through the Prefab MCP server, including onboarding, listing configs, reading config values, creating flags, updating rollouts, toggling a feature, or debugging a feature flag.

2026-04-2820

cockpit-scheduler-agent

goodguy1963/Copilot-Cockpit

Use when an agent needs to manage scheduler tasks, Jobs workflows, job folders, pause checkpoints, compile-to-task, or research profiles through the scheduler MCP tools.

2026-04-2720

prefab-ui

goodguy1963/Copilot-Cockpit

Generate structured Prefab UI JSON with the Prefab wire format. Use when building dashboards, forms, charts, settings panels, structured JSON UI output, or API-backed Prefab views that call MCP tools or fetch data at runtime. Covers the Prefab v0.2 protocol, components, actions, reactive state, expressions, and theming.

2026-04-2720

name	copilot-scheduler-agent-merge
description	Use when you need to compare the staged bundled starter-agent mirror against an existing richer repo-local agent system and selectively merge approved ideas into the live workspace files.
copilotCockpitSkillType	support
copilotCockpitToolNamespaces	[]
copilotCockpitWorkflowIntents	[]
copilotCockpitApprovalSensitive	true
copilotCockpitPromptSummary	Compare the staged starter-agent mirror with the live repo-local system, propose selective merges, and implement only approved changes without swapping whole trees.
copilotCockpitReadyWorkflowFlags	[]
copilotCockpitCloseoutWorkflowFlags	[]

Staged Agent Merge Skill

You have been invoked to help a user adopt ideas from the bundled starter-agent pack without replacing their existing repo-local agent system.

Instructions

Treat the live repo-local agent system as user-owned and as the source of truth. Never replace the entire live .github/agents tree with the starter pack.
Inspect the live agent-system surfaces first: .github/agents/, .github/skills/, .github/prompts/, .agents/, AGENTS.md, and any nearby *.agent.md or *.instructions.md files.
Inspect the staged starter bundle under .vscode/copilot-cockpit-support/bundled-agents/, starting with .vscode/copilot-cockpit-support/bundled-agents/manifest.json.
If the staged bundle or manifest is missing, stop and tell the user to run the Settings action Stage Bundled Agents first. Do not fall back to direct sync as part of this merge workflow.
Summarize the comparison in terms of merge candidates, not file replacement:
- role ideas worth adopting
- routing or escalation rules worth copying
- reusable skills or knowledge files worth adding
- overlapping files where only selected sections should be merged
Ask the user which changes they want to adopt. If they already indicated their selection, restate the chosen merge set before editing.
Implement only the approved live-system edits. Prefer targeted section merges, new additive files, or small refactors over broad rewrites.
Keep the staged bundle as reference material only. Do not edit the staged files unless the user explicitly asks to regenerate them through the plugin action.
After implementation, report:
- what was merged into the live system
- what stayed only in the staged reference tree
- any follow-up manual decisions still needed

When in doubt, prefer additive changes and explicit user confirmation over aggressive normalization.