CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatto-frontend-review

Review Chatto frontend implementation quality, including Svelte reactivity and lifecycle, component boundaries, design-system reuse, and unnecessary complexity. Use for every review that includes apps/frontend, including self-review, branch or PR review, and frontend architecture review.

Quality

87%

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

82%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-crafted review skill body: rules are concrete and project-specific rather than generic, findings output is precisely specified, and scope boundaries against the general code review are explicit. The main improvement opportunities are tightening the slight overlap between the effect-avoidance rules and making the review process sequence more explicit.

DimensionReasoningScore

Conciseness

The body is dense, project-specific directive text with no explanation of concepts Claude already knows (no Svelte primer, no library boilerplate), e.g. "Derive values; do not synchronize copies. Use `$derived` for computed state." Minor trimming is possible: rules 2 and 3 overlap on `$effect` avoidance, and rules 4 and 6 carry wordy exception clauses, which keeps it just below the 5 anchor's "every token earns its place."

4 / 5

Actionability

For an instruction-only review skill the guidance is fully actionable: named APIs (`$effect`, `$derived`, `untrack`, `onMount`), a concrete worked example ("handle a new notification in the notification-update handler, rather than watching notification state with `$effect`"), specific verification behaviors (Back/Forward/reload, wide and narrow viewport checks), and a defined findings format ("file and line, the rule, the concrete consequence"). Per the rubric's scoring note, absence of code is not penalized when instruction-only guidance is this concrete.

5 / 5

Workflow Clarity

A clear sequence is present in prose — review scope, read the frontend instructions, trace changed behavior through callers, apply the rules, then "Report findings in severity order, followed by checks run and remaining gaps" — with an explicit completion gate ("Apply these rules before declaring the review complete"). It sits below the 5 anchor because the process sequence is embedded in prose rather than laid out as an explicit ordered workflow with checkpoints, though it is not a destructive/batch skill so no cap applies.

4 / 5

Progressive Disclosure

The single-file body is well organized (intro, numbered Rules, Findings) with clearly signaled one-level-deep links to sibling skills ([chatto-code-review](../chatto-code-review/SKILL.md), [chatto-client-placement](../chatto-client-placement/SKILL.md)) and the project's AGENTS.md; no bundle files exist. This matches the 4 anchor's "good structure; references mostly clear; minor organization gaps" — the 12 rules are cohesive in one file but the intro paragraph and long rule list could be organized more tightly.

4 / 5

Total

17

/

20

Passed

Description

87%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: it concisely names concrete review capabilities and provides an explicit, multi-condition 'Use for' trigger clause tightly scoped to apps/frontend. The only minor weakness is that trigger vocabulary could include a few more natural synonyms users might say.

DimensionReasoningScore

Specificity

The description lists several specific capabilities — "Svelte reactivity and lifecycle, component boundaries, design-system reuse, and unnecessary complexity" — naming concrete review focus areas. It falls short of the 5 anchor's comprehensive multi-action coverage (it describes aspects of one action, reviewing, rather than multiple distinct actions).

4 / 5

Completeness

Both what and when are explicit: the first sentence states what the skill does, and "Use for every review that includes apps/frontend, including self-review, branch or PR review, and frontend architecture review" gives a concrete, explicit trigger clause. It clearly matches the 5 anchor and exceeds the 4 anchor, whose 'when' is less specific.

5 / 5

Trigger Term Quality

Natural trigger phrases are present: "review", "apps/frontend", "self-review", "branch or PR review", "frontend architecture review", plus the domain terms "Svelte" and "design-system". A few natural synonyms users might say (e.g., "UI", "web", "component review") are missing, so it does not reach the comprehensive synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The scope is tightly niched to Chatto's apps/frontend with distinct triggers, and it explicitly delegates broader correctness to a separate general code review, minimizing overlap. It is clearly distinguishable from generic review or document skills, matching the 5 anchor's "clear niche with distinct triggers".

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

chattocorp/chatto

Path

.agents/skills/chatto-frontend-review/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.