SKILLEMALL.ai

AD weekly-report

把"只讲事的流水账周报"升级成"领导 30 秒读懂全局"的结构化周报。用户提供碎碎念式的本周工作流水账(或直接给出本周做了什么),此 skill 通过四步流程(建项目库 → 拆事归位 → 追问补缺 → 六要素组装)输出可直接发出的领导版周报。适用于:写周报/月报/工作汇报、周会材料、向上管理。关键设计:AI 只补缺的、不编没的,风险/下周计划/思考三样缺了必须追问用户,绝不编造。

ClawHub Agent Skills author: HandsoMeng v1.0.0 MIT-0 6 files body ≈ 451 tokens Open the sourceclawhub.ai analyzed 3 d ago

把"只讲事的流水账周报"升级成"领导 30 秒读懂全局"的结构化周报。用户提供碎碎念式的本周工作流水账(或直接给出本周做了什么),此 skill 通过四步流程(建项目库 → 拆事归位 → 追问补缺 → 六要素组装)输出可直接发出的领导版周报。适用于:写周报/月报/工作汇报、周会材料、向上管理。关键设计:AI…

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
80
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 · 0

✓ No critical or high findings

Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"

Process rating: all ten parameters 49/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
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (weekly-report) differs from the folder (hs-weekly-report)
  • 100Tools and files. No external tools needed
  • 100Steps. 12 steps
  • 100Execution cost. Instruction body is 451 tokens
  • 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

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 2 example trigger phrases
  • +3Description length 191: enough signal without eating the budget
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 12 items
  • +4Has examples (3 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.

External checks

ClawHub: clean
This is a prompt-only weekly report writing skill with no hidden code execution, data access, or installation behavior beyond user-provided work status details.
LLM: benign (high) · VirusTotal: · 9 Aug 2026