BD foreman-pro
Digital construction foreman: crew management, work acceptance, work logs, hidden works acts, safety, schedules and executive documentation.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Obfuscation
uni-mixed-script-wordSKILL.md:405Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (1 occurrence)| Работа с эпоксидом/ЛКМ | ДА | ДА | ДА | А1P2 | ДА | — |
Files scanned: 36. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 17073 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "price" - note
frontmatter-keyunknown frontmatter key "price_currency"
Process rating: all ten parameters 43/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
- 10Execution cost. Instruction body is 17073 tokens: crowds the task out of the window
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (foreman-pro) differs from the folder (raai-foreman-pro)
- 100Tools and files. No external tools needed
- 100Steps. 196 steps
- 100Running it twice. No mutating operations
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)
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- -5Long text without headings
- -43 reference files, but SKILL.md never points to them: the model will not open them
- +3Description length 140: enough signal without eating the budget
- +3Step-by-step instructions: 196 items
- +4Has examples (22 code blocks)
- +1License stated
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.