SKILLEMALL.ai

BC long-text-tracker

长文本追踪系统 - 让分段内容保持连贯。 触发条件(必须全部满足):分段数≥3 且 总字数≥3000 且 段落间需逻辑连贯。 适用:推文系列、教程系列、报告系列、连载内容。 触发词:写系列推文、写教程系列、写报告系列、连载创作、分段创作长文本 不触发: - 单篇文章(分段数<3) - 独立短文(总字数<3000) - 无连贯性要求的合集 - 讨论"如何写系列"但无具体创作需求 歧义处理:无法判断时询问"是要创作系列内容(≥3段),还是单篇内容?"

ClawHub Agent Skills author: sjj2026 v3.0.0 MIT-0 4 files body ≈ 1 900 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

ProcedureInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
100
Quality 40%
60
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. 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: 4. 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 "tools"

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. 30 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1900 tokens
  • 100Running it twice. No mutating operations
  • low 13 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
  • -5TODO / placeholder text left in the skill
  • -232 emoji in the instructions: noise for the model
  • -42 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 228: enough signal without eating the budget
  • +4Structure: 48 headings
  • +3Step-by-step instructions: 30 items
  • +4Has examples (38 code blocks)

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

External checks

ClawHub: clean
This is a coherent long-form writing tracker that saves project files locally, with user guidance needed around draft retention and the optional email delivery step.
LLM: benign (high) · VirusTotal: · 29 May 2026