How do I install the Copilot Sdk skill?

Run npx skillmds@latest add tomevault-io/copilot-sdk 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 Copilot Sdk safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Copilot Sdk?

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 Copilot Sdk free to use?

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

Who published Copilot Sdk?

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

Copilot Sdk by tomevault-io — Agent Skill

Name: Copilot Sdk
Author: tomevault-io

Copilot Sdk

Keep TroubleScout’s GitHub Copilot SDK integration current by verifying the installed Copilot CLI + GitHub.Copilot.SDK versions, updating when needed, and following the official usage guidance. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Copilot SDK (TroubleScout)

Use this skill when you’re changing anything related to GitHub.Copilot.SDK or session/event streaming behavior.

Always keep components current

This repo depends on two moving parts:

GitHub.Copilot.SDK (NuGet): the .NET client library used by TroubleScout.
GitHub Copilot CLI: the local CLI the SDK talks to (server mode under the hood).

Check SDK version (.NET)

Check for outdated packages:
- dotnet list package --outdated
If GitHub.Copilot.SDK is behind:
- Update to the latest version and confirm it still builds:
  - dotnet add package GitHub.Copilot.SDK --version <latest>
  - dotnet build

Check Copilot CLI version

Verify the CLI is installed and working:
- copilot --version
If it’s missing or outdated, follow the official installation/update guide (Windows supports WinGet):
- https://docs.github.com/en/copilot/how-tos/set-up/install-copilot-cli

Notes:

Copilot CLI must be installed separately; the SDK communicates with it.
If the CLI requires login, complete authentication before debugging SDK behavior.

Official usage guidance (read these first)

Copilot SDK repo: https://github.com/github/copilot-sdk
Getting started guide: https://github.com/github/copilot-sdk/blob/main/docs/getting-started.md
.NET reference/README: https://github.com/github/copilot-sdk/blob/main/dotnet/README.md
.NET cookbook: https://github.com/github/copilot-sdk/tree/main/cookbook/dotnet

Implementation expectations for TroubleScout

Prefer the SDK’s event subscription model (subscribe via session.On(...) and treat SessionIdle as the completion signal).
Avoid inventing APIs; validate patterns against the official .NET README.
After any SDK-related change, run dotnet build.

Troubleshooting checklist

If sessions don’t start: verify copilot --version works and the CLI is authenticated.
If events don’t stream: confirm session config enables streaming and handlers are subscribed before sending.
If behavior differs after updates: re-check the official .NET README and the repo release notes, then make the smallest compatible change.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: copilot-sdkdescription: Keep TroubleScout’s GitHub Copilot SDK integration current by verifying the installed Copilot CLI + GitHub.Copilot.SDK versions, updating when needed, and following the official usage guidance. Use when this capability is needed.---# Copilot SDK (TroubleScout)Use this skill when you’re changing anything related to `GitHub.Copilot.SDK` or session/event streaming behavior.## Always keep components currentThis repo depends on two moving parts:- **GitHub.Copilot.SDK (NuGet)**: the .NET client library used by TroubleScout.- **GitHub Copilot CLI**: the local CLI the SDK talks to (server mode under the hood).### Check SDK version (.NET)- Check for outdated packages: - `dotnet list package --outdated`- If `GitHub.Copilot.SDK` is behind: - Update to the latest version and confirm it still builds: - `dotnet add package GitHub.Copilot.SDK --version <latest>` - `dotnet build`### Check Copilot CLI version- Verify the CLI is installed and working: - `copilot --version`- If it’s missing or outdated, follow the official installation/update guide (Windows supports WinGet): - https://docs.github.com/en/copilot/how-tos/set-up/install-copilot-cliNotes:- Copilot CLI must be installed separately; the SDK communicates with it.- If the CLI requires login, complete authentication before debugging SDK behavior.## Official usage guidance (read these first)- Copilot SDK repo: https://github.com/github/copilot-sdk- Getting started guide: https://github.com/github/copilot-sdk/blob/main/docs/getting-started.md- .NET reference/README: https://github.com/github/copilot-sdk/blob/main/dotnet/README.md- .NET cookbook: https://github.com/github/copilot-sdk/tree/main/cookbook/dotnet## Implementation expectations for TroubleScout- Prefer the SDK’s **event subscription model** (subscribe via `session.On(...)` and treat `SessionIdle` as the completion signal).- Avoid inventing APIs; validate patterns against the official .NET README.- After any SDK-related change, run `dotnet build`.## Troubleshooting checklist- If sessions don’t start: verify `copilot --version` works and the CLI is authenticated.- If events don’t stream: confirm session config enables streaming and handlers are subscribed before sending.- If behavior differs after updates: re-check the official .NET README and the repo release notes, then make the smallest compatible change.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/sasler) — claim your Tome and manage your conversions.

Frequently asked questions