How do I install the Manage Scout Copilot Skill Bridge skill?

Run npx skillmds@latest add fabioc-aloha/manage-scout-copilot-skill-bridge in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Manage Scout Copilot Skill Bridge safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Manage Scout Copilot Skill Bridge?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Manage Scout Copilot Skill Bridge free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Manage Scout Copilot Skill Bridge?

fabioc-aloha (@fabioc-aloha) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Manage Scout Copilot Skill Bridge by fabioc-aloha

Name: Manage Scout Copilot Skill Bridge
Author: fabioc-aloha

Manage Scout Copilot Skill Bridge

Preview, apply, or validate the curated read-in-place bridge from the global Copilot plugin store into Scout. Use after a Copilot plugin update, when Scout cannot resolve a bridged skill, or before adding a skill to the Scout allowlist.

fabioc-aloha Updated Sep 17, 2026

File contents

Manage the Scout-Copilot Skill Bridge

Keep one canonical copy of a selected skill in the global Copilot plugin store and expose it to Scout through ~/.copilot/skills. The bridge uses directory junctions on Windows and directory symlinks elsewhere. It never copies a skill body into Scout-local storage.

Preview First

Run the bundled doctor without --apply:

node <this-skill>/scripts/scout-copilot-skill-bridge.cjs

The preview reads Core's bridge manifest, resolves every declared plugin skill, reports missing sources, existing link actions, duplicate names, and whether Scout still has an excluded plugin installed. It writes nothing.

The command deliberately defaults to ~/.copilot, not COPILOT_HOME. A Scout hosted shell can set COPILOT_HOME to Scout's private runtime directory; using that value as the bridge source would create a second lifecycle path.

Apply After Review

After reviewing the exact plan, create or repair only manifest-owned links:

node <this-skill>/scripts/scout-copilot-skill-bridge.cjs --apply --canary

--apply creates missing links and repoints only an existing junction or symlink that the manifest owns. It refuses to replace a normal user directory or file. It never deletes unlisted entries in the bridge library and never installs or uninstalls a plugin.

--canary verifies representative Core, Document Tools, Illustrator, and AI Operations planning skills through the completed bridge. Start a fresh Scout conversation and resolve the reported canary names before treating a host update as complete.

Update Workflow

Review and run the appropriate copilot plugin update command in the global Copilot store.
Run this doctor in preview mode.
Review missing sources, link actions, and excluded Scout-plugin findings.
Apply only when the plan is clean.
Run the canary and confirm Scout's native browser, Flint, WorkIQ, filesystem, shell, and YouTube tools remain available.

Ownership Boundary

Core's sixteen instructions remain Scout-native and receipt-owned. They are never bridged as skills.
Scout owns its native MCP servers. Do not install Illustrator only to obtain Flint or Playwright in Scout.
Enterprise and MSFT are Copilot-only. Scout's native Microsoft 365 and WorkIQ capabilities are not a reason to bridge their setup skills or Agency agents.
model-router plans provider work but does not authorize or execute it. Provider execution, credentials, and provider MCP servers stay Copilot-only until a separate consented Scout adapter exists.

Adding a Skill

Add a skill only after documenting its source plugin, host-neutral behavior, required Scout capabilities, and fallback in Core's bridge manifest. Then add a deterministic test and a disposable Scout-session canary. Do not infer eligibility from a plugin directory alone.

Would Revise If

Revise by 2026-11-25 if normal Copilot updates cannot preserve valid link targets, a clean Scout session cannot resolve an allowlisted skill, an excluded plugin is necessary for a safe Scout workload, or the doctor cannot distinguish its own links from user-owned content.

---name: manage-scout-copilot-skill-bridgedescription: Preview, apply, or validate the curated read-in-place bridge from the global Copilot plugin store into Scout. Use after a Copilot plugin update, when Scout cannot resolve a bridged skill, or before adding a skill to the Scout allowlist.---# Manage the Scout-Copilot Skill BridgeKeep one canonical copy of a selected skill in the global Copilot plugin storeand expose it to Scout through `~/.copilot/skills`. The bridge uses directoryjunctions on Windows and directory symlinks elsewhere. It never copies a skillbody into Scout-local storage.## Preview FirstRun the bundled doctor without `--apply`:```textnode <this-skill>/scripts/scout-copilot-skill-bridge.cjs```The preview reads Core's bridge manifest, resolves every declared plugin skill,reports missing sources, existing link actions, duplicate names, and whetherScout still has an excluded plugin installed. It writes nothing.The command deliberately defaults to `~/.copilot`, not `COPILOT_HOME`. A Scouthosted shell can set `COPILOT_HOME` to Scout's private runtime directory; usingthat value as the bridge source would create a second lifecycle path.## Apply After ReviewAfter reviewing the exact plan, create or repair only manifest-owned links:```textnode <this-skill>/scripts/scout-copilot-skill-bridge.cjs --apply --canary````--apply` creates missing links and repoints only an existing junction orsymlink that the manifest owns. It refuses to replace a normal user directoryor file. It never deletes unlisted entries in the bridge library and neverinstalls or uninstalls a plugin.`--canary` verifies representative Core, Document Tools, Illustrator, and AIOperations planning skills through the completed bridge. Start a fresh Scoutconversation and resolve the reported canary names before treating a host updateas complete.## Update Workflow1. Review and run the appropriate `copilot plugin update` command in the global Copilot store.2. Run this doctor in preview mode.3. Review missing sources, link actions, and excluded Scout-plugin findings.4. Apply only when the plan is clean.5. Run the canary and confirm Scout's native browser, Flint, WorkIQ, filesystem, shell, and YouTube tools remain available.## Ownership Boundary- Core's sixteen instructions remain Scout-native and receipt-owned. They are never bridged as skills.- Scout owns its native MCP servers. Do not install Illustrator only to obtain Flint or Playwright in Scout.- Enterprise and MSFT are Copilot-only. Scout's native Microsoft 365 and WorkIQ capabilities are not a reason to bridge their setup skills or Agency agents.- `model-router` plans provider work but does not authorize or execute it. Provider execution, credentials, and provider MCP servers stay Copilot-only until a separate consented Scout adapter exists.## Adding a SkillAdd a skill only after documenting its source plugin, host-neutral behavior,required Scout capabilities, and fallback in Core's bridge manifest. Then add adeterministic test and a disposable Scout-session canary. Do not infereligibility from a plugin directory alone.## Would Revise IfRevise by **2026-11-25** if normal Copilot updates cannot preserve valid linktargets, a clean Scout session cannot resolve an allowlisted skill, an excludedplugin is necessary for a safe Scout workload, or the doctor cannot distinguishits own links from user-owned content.

Frequently asked questions