agentleFS
Jurel89Jurel89/copilot-omni/skills/setup/SKILL.md

setup

Skill0 starsChanged 7 months agoMITView on GitHub

Use first for install/update routing — sends setup, doctor, or MCP requests to the correct copilot-omni setup flow

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 165 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use /copilot-omni:setup as the unified setup/configuration entrypoint.

    line 9
  2. Very specific:

    No argument, wizard, local, global, or --force -> route to /copilot-omni:omni-setup with the same remaining args

    line 24
  3. Very specific:

    Prefer /copilot-omni:setup in new documentation and user guidance.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 165 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup

Use /copilot-omni:setup as the unified setup/configuration entrypoint.

Usage

/copilot-omni:setup                # full setup wizard
/copilot-omni:setup doctor         # installation diagnostics
/copilot-omni:setup mcp            # MCP server configuration
/copilot-omni:setup wizard --local # explicit wizard path

Routing

Process the request by the first argument only so install/setup questions land on the right flow immediately:

  • No argument, wizard, local, global, or --force -> route to /copilot-omni:omni-setup with the same remaining args
  • doctor -> route to /copilot-omni:omni-doctor with everything after the doctor token
  • mcp -> route to /copilot-omni:mcp-setup with everything after the mcp token

Examples:

/copilot-omni:setup --local          # => /copilot-omni:omni-setup --local
/copilot-omni:setup doctor --json    # => /copilot-omni:omni-doctor --json
/copilot-omni:setup mcp github       # => /copilot-omni:mcp-setup github

Notes

  • /copilot-omni:omni-setup, /copilot-omni:omni-doctor, and /copilot-omni:mcp-setup remain valid compatibility entrypoints.
  • Prefer /copilot-omni:setup in new documentation and user guidance.

Task: {{ARGUMENTS}}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.