[Observation]: Copilot SDK 1.0.x is less willing to load skills

Open
#1,747 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Domain
ai

Research direction

No files, tests, or entry points are named. Start by reproducing the fixed scenarios across Copilot SDK 0.3.x and 1.0.x with the MS Learn documentation tool and local skills, then determine when skill loading is bypassed. Done would require an agreed expected precedence and a concrete location for validating or changing that behavior.

Written by the indexing model from the issue text.

Description

documentation

My team has recently upgraded Copilot SDK from 0.3.x to 1.0.x for running a few fixed scenarios to track the agent behavior with our skills. We give the agent a generic documentation tool that searches in MS Learn and skills with service oriented instructions. We noticed that after upgrading to Copilot SDK 1.0.x, the agent shows a much higher likelihood to use documentation tools instead of loading a skill. This is not an ideal behavior. Local skills are usually knowledge the user creates to override the generic knowledge in the training data or public documentation. They are also usually more efficient in token usage.

Dominant language
Java
Stars
10.5k
Forks
1.5k
Avg merge
1d 12h
Merged PRs (30d)
133

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/copilot-sdk

All issues in github/copilot-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.