BC ms-forms-auto
Automate Microsoft Forms submission with dual-calendar integration and M365 MFA support. Use when: automating daily productivity log submissions, submitting Microsoft Forms with calendar-based auto-fill, setting up scheduled form submissions with training/content-dev/learning hour calculations, or working with org MS Forms that require M365 number-matching MFA. Triggers on phrases like "fill out MS form", "automate form submission", "daily form report", "submit Microsoft form", "daily productivity log", "training hours form".
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 7
✓ No critical or high findings
Medium and low: 7
-
low Secrets in code
secret-high-entropy-tokenconfig/form-structure.json:13High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"questionId": "Ques…8a5",
quoted -
low Secrets in code
secret-high-entropy-tokenconfig/form-structure.json:20High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"questionId": "Ques…ec0",
quoted -
low Secrets in code
secret-high-entropy-tokenconfig/form-structure.json:27High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"questionId": "Ques…2a0",
quoted -
low Secrets in code
secret-high-entropy-tokenconfig/form-structure.json:34High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"questionId": "Ques…8bd",
quoted -
low Secrets in code
secret-high-entropy-tokenconfig/form-structure.json:41High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"questionId": "Ques…940",
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:20High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…uWm+fFRcIOgKBMiOBP+eXiy…9ab+DDKA==",
detector -
low Dangerous commands
cmd-privilegescripts/submit.js:341Privilege escalation / world-writable permissions (detector / deny-list definition; string literal in code, not executed)args: ['--no-sandbox', '--disable-setuid-sandbox'],
detectorcode literal
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Automate Microsoft Forms submission with dual-calendar integration… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 21 steps, 1 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1503 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -36 of 12 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 531: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.