DC startup-verifier
(no description)
Этот скилл используется для проверки кандидатов на адаптацию стартапов для российского рынка.
As a process C 59/100 · Has gaps — 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
- Add a description to the frontmatter: without it the skill never triggers.
- 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:29Word mixing Latin and Cyrillic letters (homoglyph obfuscation) (2 occurrences)| 8 | **CRDT-viability** | Доступные способы приёма платежей в России: ЮKassa, СБП, USDT, Telegram Stars, ЮMoney. | ✅ = 3+ способа доступны; ⚠️ = 1-2 способа; ❌…
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1722 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -251 emoji in the instructions: noise for the model
- +1No license
- +4Structure: 10 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (1 code blocks)
- +2Bilingual instructions (RU + EN)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.