BD gov-disclosure-check
gov-disclosure-check — LGD 三律在政务 / 信息公开披露域的纵深合规工具（零依赖）：强制披露字段校验（决策依据/责任部门/时限/救济渠道/数据来源），对 AI 系统/数据做可执行合规校验。
gov-disclosure-check — LGD 三律在政务 / 信息公开披露域的纵深合规工具（零依赖）：强制披露字段校验（决策依据/责任部门/时限/救济渠道/数据来源），对 AI 系统/数据做可执行合规校验。
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 107 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "copyright" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 46/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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 469 tokens
- 100Running it twice. No mutating operations
- low 10 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)
- +3Description length 107: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Structure: 11 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.
External checks
ClawHub: suspicious
The skill itself is a small local disclosure-checking script, but its documented install path asks users to run an unpinned global installer that can execute mutable third-party code.
LLM: suspicious (medium) · 11 Sept 2026