Sensei Agent Skill
Iteratively improve skill frontmatter to achieve good routing test coverage. WHEN: run sensei, sensei help, improve skill routing
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/microsoft/GitHub-Copilot-for-Azure --skill senseiWhat comes with it
2 114 bytes besides the instructionThe instruction itself
4 sections, as written by the authorHelp
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 inevals/{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 invally-evalskill 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-evalskill 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
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take microsoft/sensei from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.