AF rank-tracker
Use when the user asks to "track rankings" or "查排名"; measures keyword and SERP-position deltas over time from provided exports or connected tools, including AI-response checks. Not for multi-metric stakeholder reports or setting alerts — use performance-monitor (report or alert mode). 排名追踪/SERP监控
As a process F 59/100 · Will not run — References files that are not bundled: ../performance-monitor/SKILL.md, ../../../references/skill-contract.md, ../../../CONNECTORS.md
How to improve
- 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.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 297 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
missing-refreference to a missing file: ../performance-monitor/SKILL.md - warning
missing-refreference to a missing file: ../../../references/skill-contract.md - warning
missing-refreference to a missing file: ../../../CONNECTORS.md - warning
missing-refreference to a missing file: ../../../references/measurement-protocol.md - warning
missing-refreference to a missing file: ../../../scripts/connectors/README.md - 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 59/100
- 0Tools and files. 5 referenced file(s) missing: ../performance-monitor/SKILL.md, ../../../references/skill-contract.md, ../../../CONNECTORS.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 60Failures and branches. 2 branches
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 16 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1497 tokens
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 297: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 16 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.