SKILLEMALL.ai
GitHub ↗ RU Sign in

BC daily-report-tool-pro

核心能力: 工作汇报领域的专业化 AI 辅助工具,包含企业级高级功能兼容. 面向需要daily report tool相关能力的开发场景,提供规范流程和配置说明。PRO 版本完全包含 FREE 版本的所有功能,并在此基础上扩展了以下企业级能力: 输入日期和亮点事项生成日报。适用于独立开发者、企业团队和自动化工作流场景，提供结构化输出与错误处理机制，支持中文交互，即开即用

ClawHub Hermes author: 天轰穿 v1.0.0 MIT-0 2 files body ≈ 1 990 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

核心能力: 工作汇报领域的专业化 AI 辅助工具,包含企业级高级功能兼容.

As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAI and agentsPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
64
Run on models
none yet
Process rating
C
58/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 186 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "slug"
  • note frontmatter-key unknown frontmatter key "displayName"
  • note frontmatter-key unknown frontmatter key "summary"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "pricing_tier"

Process rating: all ten parameters 58/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 61 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1990 tokens
  • 100Running it twice. No mutating operations
  • low 18 top-level sections: this looks like several domains in one skill

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
  • +2Single-language instructions
  • +3Description length 186: enough signal without eating the budget
  • +4Structure: 42 headings
  • +3Step-by-step instructions: 61 items
  • +4Has examples (9 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This daily-report skill is not clearly malicious, but it asks for broad file, command, API, credential, and external callback capabilities without enough scoping or user-control detail.
LLM: suspicious (high) · 20 Aug 2026