BD microsoft-excel
Read and edit live Excel workbooks stored in OneDrive / SharePoint via the Microsoft Graph workbook API. Use when the user mentions an Excel file, a spreadsheet on OneDrive, reading a range or table, appending rows, updating cells, or listing worksheets in a cloud .xlsx.
Read and edit live Excel workbooks stored in OneDrive / SharePoint via the Microsoft Graph workbook API.
As a process D 46/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-useSKILL.md:19Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)`curl + jq`. The user's OAuth bearer token is in `$MICROSOFT_EXCEL_TOKEN`; every
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "connections" - note
frontmatter-keyunknown frontmatter key "allowed_tools"
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 572 tokens
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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 271: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.