BF designer-intelligence-station
Designer intelligence collection tool. Monitors 46 public sources (AI/hardware/mobile/design), dynamic quality-based filtering v2.1.8, generates structured daily/weekly reports. All data stored locally.
As a process F 33/100 · Will not run — References files that are not bundled: 链接
GeneratorGitHubData and analyticsSoftware developmentDesigntype and topics are labelled automatically from the skill text
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.
- The text references files that are not there: add them or drop the references.
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Dangerous commands
cmd-cron-mentionINSTALL.md:123Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionSKILL.md:152Mentions editing / listing crontabcrontab -e
Files scanned: 80. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 202 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 - warning
missing-refreference to a missing file: 链接 - note
frontmatter-keyunknown frontmatter key "models" - note
frontmatter-keyunknown frontmatter key "capabilities" - note
frontmatter-keyunknown frontmatter key "languages" - note
frontmatter-keyunknown frontmatter key "related_skills"
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: 链接
- 0Tools and files. 1 referenced file(s) missing: 链接
- 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. 107 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2056 tokens
- low 14 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
- -267 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 202: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 107 items
- +4Has examples (16 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.
External checks
ClawHub: suspicious
The skill mostly matches a news/reporting tool, but its local-only and no-login claims are undercut by optional social-media setup that uses browser cookies/logins and by report-sending examples with a fixed recipient.
LLM: suspicious (high) · VirusTotal: · 29 May 2026