BF telegram-contract-ops
Telegram-based internal contract generation and eID intake workflow for Vietnamese operations. Use when setting up, migrating, or operating a bot that: (1) receives structured contract input in Telegram, (2) generates `.docx` contracts from a fixed company template, (3) receives Vietnamese electronic ID screenshots, OCRs key fields, and converts them into contract-ready input, and (4) routes behavior by Telegram group for contract workflows.
As a process F 33/100 · Will not run — References files that are not bundled: assets/windows/
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
read-dotenvreferences/deployment.md:106Reads a .env filesource ./.env.telegram
-
low Exfiltration
exfil-webhook-urlscripts/telegram-planb-bot.js:8Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)const API = TOKEN ? `https://api.telegram.org/bot${TOKEN}` : '';placeholder -
low Exfiltration
net-credential-usescripts/telegram-planb-bot.js:60Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)const res = await fetch(`https://api.telegram.org/file/bot${TOKEN}/${info.file_path}`);vendor-host
Files scanned: 14. 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: Telegram-based internal contract generation and eID intake workflo… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: assets/windows/
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: assets/windows/
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 428 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
- +4No input/output examples
- -34 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 445: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 34 items
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.