SKILLEMALL.ai
GitHub ↗ RU Sign in

BC go-to-market

构建产品上市或进入新市场的GTM策略:目标客户画像、定位陈述、 销售运动模式选择、渠道筛选、90天执行计划、定价与优惠、度量 迭代与常见错误规避，可处理提升工作效率。Use。Use when 需要提升效率、自动化流程、批量处理、工作流优化时使用。不适用于需要人工创意判断的任务。适用于独立开发者、企业团队和自动化工作流场景。 功能涵盖: market。

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

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

ReferenceInfrastructuretype 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%
66
Run on models
none yet
Process rating
C
53/100
Has gaps
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. 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 frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 8, column 14: description: 构建产品上市或进入新市场的GTM策略:目标客户画像、定位陈述、 销售运动模式选择、渠道筛选、90天执行计划、定价与优惠、度量 迭代与… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
  • warning description-long-hermes description is 176 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • 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 "summary_zh"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "homepage"

Process rating: all ten parameters 53/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
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 55 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2135 tokens
  • 100Running it twice. No mutating operations
  • low 17 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 176: enough signal without eating the budget
  • +4Structure: 50 headings
  • +3Step-by-step instructions: 55 items
  • +4Has examples (6 code blocks)
  • +1License stated

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

External checks

ClawHub: suspicious
This GTM planning skill is mostly advisory, but it asks for broad read/write/command authority and describes API, file, and command operations that are not clearly scoped to its business-strategy purpose.
LLM: suspicious (high) · 10 Aug 2026