Sensei

Skill microsoft/GitHub-Copilot-for-Azure/.github/skills/sensei

GitHub Copilot for Azure

Install

npx -y skills add microsoft/GitHub-Copilot-for-Azure --skill sensei

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Iteratively improve skill frontmatter to achieve good routing test coverage. WHEN: run sensei, sensei help, improve skill routing

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.8 KB, 814 tokens by cl100k_base, as published. Nobody here has run it

Help

When user says "sensei help" or asks how to use sensei, show this:

╔══════════════════════════════════════════════════════════════════╗
║  SENSEI - Skill Frontmatter Compliance Improver                  ║
╠══════════════════════════════════════════════════════════════════╣
║                                                                  ║
║  USAGE:                                                          ║
║    Run sensei on <skill-name>              # Single skill        ║
║    Run sensei on <skill1>, <skill2>, ...   # Multiple skills     ║
║    Run sensei on all skills                # All skills          ║
║                                                                  ║
║  EXAMPLES:                                                       ║
║    Run sensei on appinsights-instrumentation                     ║
║    Run sensei on azure-ai, azure-compute                         ║
║                                                                  ║
║  WHAT IT DOES:                                                   ║
║    1. READ      - Load skill's SKILL.md and tests                ║
║    2. VERIFY    - Compare skill frontmatter with convention      ║
║    3. SCAFFOLD  - Create tests from frontmatter if missing       ║
║    4. IMPROVE   - Add WHEN: triggers                             ║
║    5. TEST      - Run tests, fix if needed                       ║
║    6. SUMMARY   - Show before/after with suggestions             ║
║    7. PROMPT    - Ask: Commit, Create Issue, or Skip?            ║
║    8. REPEAT    - Until routing tests pass                       ║
╚══════════════════════════════════════════════════════════════════╝

Main Loop

For each skill, execute this loop until the frontmatter aligns with convention, have thorough routing tests AND routing tests pass:

READ - Load plugin/skills/{skill-name}/SKILL.md, and vally eval suites in evals/{skill-name}/*.yaml.
VERIFY - Compare the skill frontmatter with conventions in CONVENTIONS. If the skill's frontmatter violates any written convention, notify the user and propose a fix to align the frontmatter with the convention.
SCAFFOLD - If evals/{skill-name}/ doesn't exist, follow instructions in vally-eval skill to scaffold a set of routing tests. The routing tests test if the skill can be invoked for target user prompts. Generate user prompts that match the target scenario of the skill's description.
IMPROVE - If the skill description doesn't already have WHEN: triggers, add them.
TEST - Follow instructions in vally-eval skill to run the routing tests. If there are failed tests, suggest fixes.
SUMMARY - Display before/after comparison with unimplemented suggestions.
PROMPT - Ask user to commit the fixes or take any alternative actions.
REPEAT - Go to step 2 (max 5 iterations per skill)

Constraints

Only modify plugin/skills/ - these are the Azure skills used by Copilot
Files in .github/skills/ should be left as is
Max 5 iterations per skill before moving on

Related Skills

vally-eval - vally eval suite writing guidelines