CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

performance-monitor

Use when the user asks to "generate an SEO report", "出月报", "set SEO alerts", or "排名掉了提醒我"; two modes — report builds multi-metric traffic/ranking/authority/content dashboards, and alert configures threshold notifications for future ranking, traffic, technical, backlink, competitor, and AI-visibility changes. Not for raw position-by-position deltas — use rank-tracker. SEO报告/绩效仪表盘/SEO预警/排名监控

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered dual-mode skill body: complete sequenced workflows with decision gates and validation checkpoints, concrete commands and a copy-ready threshold table, and clean one-level reference splitting. The gaps are executional rather than structural — placeholder data payloads, a referenced ledger.py script missing from the bundle, and cross-bundle paths that don't resolve from this directory.

Suggestions

Bundle scripts/connectors/ledger.py (or inline the minimal record/diff/trend usage) and replace the '"sessions": ...' ellipsis payload with one complete example JSON so the zero-dependency measurement loop is copy-paste executable.

Make the out-of-bundle paths resolvable: either vendor the referenced sections of ../../../references/measurement-protocol.md and skill-contract.md into the skill's own references/, or summarize their required content inline so the readback protocol is self-contained.

State the Measured / User-provided / Estimated labeling rule once (e.g., in the Shared discipline section) and reference it from the alert and steep-decline sections instead of repeating the full rule four times.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no 'what SEO is' padding) and the threshold table packs concrete values densely, but the Measured/User-provided/Estimated labeling discipline is repeated four times (Data Sources, Instructions, alert step 2, steep-decline trigger) and protocol phrasing like 'bind the current non-forked page/content/change head' could be tightened. Efficient with minor trimmable repetition — the 4 anchor, not 5.

4 / 5

Actionability

Concrete executable commands are present ("python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/ledger.py" record <domain> --source monitor --data '...'", "ledger.py diff", "ledger.py trend") plus exact thresholds (-15% WoW, >3 position drop) and Quick Start invocations. Falls short of the 5 anchor because the data payload uses ellipsis placeholders ("{"sessions": ..., ...}") and the ledger.py script is not actually present in the bundle's scripts/ directory, leaving minor execution gaps.

4 / 5

Workflow Clarity

Step 0 mode selection feeds two fully numbered procedures (report steps 1-11, alert steps 1-5) with explicit stop-gates ("Mode ambiguous", missing period, missing baseline) and continue-silently rules, done-when checklists, and validation discipline ("confirm the drop holds before declaring an incident", "corroborate before stating a cause"). Clear sequence with explicit checkpoints and error-recovery options — matches the 5 anchor; this is not a destructive/batch skill so no cap applies.

5 / 5

Progressive Disclosure

Good structure: all six references/*.md files exist, are one level deep, cited at point of use, and indexed with one-line descriptions in a Reference Materials section. Falls short of 5 because several load-bearing paths point outside the bundle and do not resolve — ../../../references/skill-contract.md, ../../../references/measurement-protocol.md (which the readback section depends on), ../../../CONNECTORS.md, and the absent scripts/connectors/ — creating navigation gaps.

4 / 5

Total

17

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete two-mode capability statement, quoted bilingual trigger phrases, an explicit use-when clause, and a negative boundary redirecting to rank-tracker. Only minor levers remain — the authority/content scopes could be disambiguated from the auditor skills, and the two summary-mode verbs could be expanded.

DimensionReasoningScore

Specificity

Two concrete mode-actions are named with enumerated scopes — "report builds multi-metric traffic/ranking/authority/content dashboards" and "alert configures threshold notifications for future ranking, traffic, technical, backlink, competitor, and AI-visibility changes". This is more detailed than the 3 anchor's '1-2 concrete actions, not comprehensive', but stops short of the 5 anchor's multiple distinct concrete verbs (builds/configures are the only two), so 4 fits best.

4 / 5

Completeness

Explicitly answers both: what ("two modes — report builds ... dashboards, and alert configures threshold notifications") and when ("Use when the user asks to ..." with concrete quoted phrases), and adds a negative boundary ("Not for raw position-by-position deltas — use rank-tracker"). Matches the 5 anchor exactly; the 4 anchor's 'when could be more explicit' does not apply since trigger phrases are quoted verbatim.

5 / 5

Trigger Term Quality

Quoted natural trigger phrases users would actually say — "generate an SEO report", "出月报", "set SEO alerts", "排名掉了提醒我" — plus a trailing synonym list "SEO报告/绩效仪表盘/SEO预警/排名监控" covering dashboards and rank monitoring. Coverage includes bilingual synonyms and variations; not the 4 anchor because no common natural terms are missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear and it explicitly disambiguates from the closest sibling ("Not for raw position-by-position deltas — use rank-tracker"), supporting 5. However it claims "authority/content" reporting without disambiguating from sibling auditor skills that own those scores, so minor overlap risk remains — the 4 anchor's 'mostly distinct; minor overlap risk with closely related skills' is the better fit.

4 / 5

Total

18

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 14 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/evaluate/performance-monitor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.