BD daily-report-generator
When the user asks to generate a daily work report, or says "生成日报", "今日工作汇报", "daily report", "工作日报", or wants to summarize today's work. This skill collects data from multiple sources, intelligently analyzes and categorizes work items, and produces a structured daily report in Markdown, HTML, or PDF format.
When the user asks to generate a daily work report, or says "生成日报", "今日工作汇报", "daily report", "工作日报", or wants to summarize today's work.
As a process D 45/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
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
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Obfuscation
obf-base64-blobREADME.md:6Long base64-looking blobRese…e1: ktAz…lOt/EzjB43G+XfPRSmB+3P/aXfX…lpG+FKj9…HA5/vitg…sul/fyns…z7Y+mUuoz//w6
-
medium Obfuscation
obf-base64-blobREADME.md:9Long base64-looking blobRese…e2: ktAz…lOt/EzjB43G+XfPRSmB+3P/aXfX…lpG+FKj9…HA5/vitg…sul/fyns…z7Y+mUuoz//w6
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 45/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. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (daily-report-generator) differs from the folder (enterprise-daily-report)
- 60Tools and files. Uses tools (git, python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 208 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 309: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 16 items
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.