BF hekouwang-typora-theme-skill
会勇禾口王 · Typora 主题工程 Skill。维护「hekouwang」主题(中文长文浅色 + 深色), 并提供一套可复用的主题工程方法:CSS 由 tokens.json 生成而非手写、构建时强制零 !important / 零 px 字号、从参照截图采样真实色值(而不是猜 配色)、用 fallback 基准探针验证字体是否真的上屏。 当需要:① 改 Typora 主题的配色/字号/行高/紧凑度/纸感;② 装主题或排查「改了 CSS 但 Typora 里没变化 / 字体没生效 / 主题菜单多出奇怪条目」;③ 按某个 App 或网站的观感做 一套新主题(采样它的真实色值);④ 加深色版或新变体;⑤ 把主题发布到 theme.typora.io 时使用。 触发词:Typora 主题 / typora theme / 改主题配色 / 主题不生效 / 换肤 / Markdown 编辑器主题 / hekouwang 主题 / 主题字体没上屏 / 采样配色 / 做一套主题 / 提交 Typora 主题库。
会勇禾口王 · Typora 主题工程 Skill。维护「hekouwang」主题(中文长文浅色 + 深色), 并提供一套可复用的主题工程方法:CSS 由 tokens.json 生成而非手写、构建时强制零 !important / 零 px 字号、从参照截图采样真实色值(而不是猜 配色)、用 fallback…
As a process F 40/100 · Will not run — References files that are not bundled: scripts/tokens.json, scripts/build.py
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Write Edit Glob Grep
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/tokens.json - warning
missing-refreference to a missing file: scripts/build.py - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 40/100
- 0Tools and files. 2 referenced file(s) missing: scripts/tokens.json, scripts/build.py
- 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
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 847 tokens
- 100Running it twice. No mutating operations
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 457: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.