CtrlK
BlogDocsLog inGet started
Tessl Logo

auditing

Audit a Studio-backed WordPress site for performance, accessibility, and visible frontend quality issues, then recommend or validate improvements.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/auditing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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.

The content is a well-structured, actionable audit playbook with concrete thresholds, named tools, and clear sequencing including validation checkpoints; it earns consistent 4s with only minor tightening opportunities.

Suggestions

Add a short error-recovery note in the Performance/Audit steps (e.g. what to do when need_for_speed returns no data) to push workflow_clarity toward 5.

Trim meta-commentary sentences that restate the obvious (e.g. "Keep this section focused on visible problems that materially affect the site.") to tighten conciseness.

Consider extracting the metrics threshold tables into a references file if the skill grows, so SKILL.md stays a concise overview.

DimensionReasoningScore

Conciseness

The body is lean — tables and bullet lists carry the detail with no padding about what WordPress or Core Web Vitals are — though a few meta sentences ("Keep this section focused on visible problems that materially affect the site.") could be trimmed.

4 / 5

Actionability

Names specific MCP tools (need_for_speed, take_screenshot, inspect_design) and concrete thresholds (TTFB < 800 ms, DOM > 1500, page weight > 3 MB) with WordPress-specific remediation; minor gap is that exact tool-call syntax is delegated to the studio skill.

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit started/completed record_workflow_event checkpoints and a re-test before/after loop; just short of 5 because there is no error-recovery feedback loop within the audit steps.

4 / 5

Progressive Disclosure

Well-organized into Ownership, Principle, Workflow, and Important notes with clear subsections; no bundle files exist to split, and the >50-line body keeps it just below the simple-skill 5 exception.

4 / 5

Total

16

/

20

Passed

Description

66%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.

The description is specific and well-scoped to a distinct niche, but it omits an explicit trigger clause, leaving the "when to use" guidance implicit and capping completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to review, optimize, or verify an existing WordPress site's speed, accessibility, or frontend quality."

Surface common synonyms users say ("speed", "QA", "Core Web Vitals", "polish") directly in the description to improve trigger term coverage.

Name one or two concrete checks (e.g. Core Web Vitals thresholds, contrast review) to lift specificity from abstract verbs to concrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete action areas ("performance, accessibility, and visible frontend quality issues, then recommend or validate improvements"), but the verbs audit/recommend/validate stay somewhat abstract rather than enumerating specific checks.

4 / 5

Completeness

Clearly states what the skill does, but the description has no explicit "Use when…" trigger clause; the trigger guidance lives only in the body, so completeness caps at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("performance", "accessibility", "WordPress site", "frontend quality") but omits common synonyms like "speed", "QA", or "Core Web Vitals" that appear only in the body.

4 / 5

Distinctiveness Conflict Risk

"Studio-backed WordPress site" carves a clear niche, though the generic performance/accessibility triggers create minor overlap risk with broader web-quality skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Automattic/build-with-wordpress
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.