CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ttfb

Use when auditing slow first responses on SSR pages, APIs, or cacheable HTML. Distinguish origin compute time from network latency and CDN cache misses before proposing a fix.

Quality

72%

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/ttfb/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 skill is short and well-split, with an exemplary progressive-disclosure structure pointing to a real one-level-deep reference. However, the inline guidance leans generic: the Check and Fix sections duplicate the Quick Reference without adding measurement commands, concrete steps, or a verify-after-fix loop.

Suggestions

Make the Check section concrete: add actual measurement steps or commands (e.g. "Measure with `curl -w '%{time_starttransfer}\n' -o /dev/null <url>` or Lighthouse's server-response-time audit") instead of "identify any bottlenecks".

Add a post-fix validation step ("Re-measure TTFB and confirm it drops below the ~800ms threshold before considering the route fixed") to close the Check→Fix loop.

Cut the conceptual intro sentence and the Quick-Reference/Fix duplication — keep one list of the three remedies and remove the restated version in Fix.

DimensionReasoningScore

Conciseness

The body opens with a concept explanation Claude already knows ("TTFB is the foundation of page performance; if the server is slow to respond, all subsequent loading stages are delayed"), and the Fix section restates the three Quick Reference bullets almost verbatim ("improving database queries, caching responses, and using a CDN"). This is more than the 'minor instances' of the 4 anchor, but not the pervasive padding of the 2 anchor.

3 / 5

Actionability

The Code Review section offers some concrete guidance — "Flag uncached HTML, slow synchronous work before the first byte, repeated upstream fetches, or expensive queries that keep TTFB above roughly 800ms" — but Check and Fix are high-level direction ("identify any bottlenecks in the server-side processing") with no measurement commands or specific steps. It sits between the vague-hints of the 2 anchor and executable guidance of the 4 anchor, since no commands or code appear inline.

3 / 5

Workflow Clarity

Check → Fix → Explain → Code Review provides a recognizable sequence, but the Check step never says how to measure TTFB and there is no post-fix validation checkpoint (e.g. re-measure TTFB to confirm the fix). This matches the 3 anchor 'sequence present but checkpoints missing or implicit', and is above the 2 anchor because the sectioned phases are clearly delineated and named.

3 / 5

Progressive Disclosure

The body is a concise overview that delegates implementation detail via a clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists and contains real content with no nested references. This matches the 5 anchor: appropriate split, easy navigation, well-signaled single reference level.

5 / 5

Total

14

/

20

Passed

Description

76%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 well-structured description that explicitly covers both what the skill does and when to use it, with concrete technical framing. Its main gap is omitting the metric's own natural trigger names (TTFB / time to first byte / server response time), relying instead on a paraphrase of the symptom.

Suggestions

Include the natural trigger terms "TTFB", "time to first byte", and "server response time" in the description, e.g. "Use when auditing slow TTFB (time to first byte) on SSR pages, APIs, or cacheable HTML."

Name one or two concrete fix-side actions (e.g. "add edge caching, tune database queries") so the 'what' covers the full audit-to-fix scope it hints at with "before proposing a fix".

DimensionReasoningScore

Specificity

The description lists several specific actions — "auditing slow first responses", "Distinguish origin compute time from network latency and CDN cache misses", "before proposing a fix" — anchored in concrete technical artifacts (SSR pages, APIs, cacheable HTML, CDN). It falls short of the 5 anchor because coverage is diagnostic-centric and does not enumerate the fix-side actions it alludes to.

4 / 5

Completeness

It explicitly answers 'when' with a concrete "Use when auditing slow first responses on SSR pages, APIs, or cacheable HTML" clause covering three scenarios, and answers 'what' with the clear diagnostic action "Distinguish origin compute time from network latency and CDN cache misses before proposing a fix". Both elements are explicit and concrete, matching the 5 anchor rather than the 4 anchor where 'when' would be less specific.

5 / 5

Trigger Term Quality

Relevant domain keywords are present ("SSR pages", "APIs", "cacheable HTML", "CDN cache misses", "network latency"), but the metric's own natural names — "TTFB", "time to first byte", "server response time" — are absent, which are exactly the phrases a user would say when they need this skill. This matches the anchor 'Some relevant keywords but missing common variations or synonyms', and it is not a 4 because more than just 'a few' natural terms are missing — the primary trigger phrase itself is omitted.

3 / 5

Distinctiveness Conflict Risk

TTFB auditing framed as separating origin compute from network latency and CDN cache misses is a clear niche with mostly distinct triggers. It is not a 5 because it can plausibly overlap with broader web-performance or caching optimization skills covering similar trigger contexts.

4 / 5

Total

16

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/ttfb/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.