BA chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting session data.
The skill analyzes Copilot session history in VS Code to extract data for standups, search by keywords or files, PR tracking, and session reindexing. Promises daily reports and workflow recommendations.
Tests show grade B: quality 77, process 83. No critical findings, safety at 100. Single file, runs across all major platforms from Claude to DeepSeek. No broken links or lint errors.
Catch: the skill only works if you already have session history in Copilot, and usefulness depends on how consistently you maintain it. Good for standups and lookups. Install if you work in Copilot regularly and want to preserve session context.
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing.
As a process A 83/100 · Runs to the end — no weak spots found
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6930 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 83/100
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6930 tokens
- 85Steps. 102 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (5 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 328: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 102 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.