CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

http-requests

Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize HTTP requests. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

76%

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

Quality

Content

63%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-structured overview that defers implementation detail appropriately to a real one-level-deep reference, with a clear Check/Fix flow. Weakest points are duplicated latency exposition and a Check step that names the goal but not how to measure it, plus no post-fix verification.

Suggestions

Remove the duplicated DNS/TCP/TLS latency explanation — keep it in either the intro paragraph or the Quick Reference bullet, not both, since Claude already knows this concept.

Make the Check step executable: state how to count requests (e.g., DevTools Network tab filtered by request count, or a one-line performance.getEntriesByType('resource') snippet) rather than just "Count the number of HTTP requests".

Add a post-fix verification checkpoint to the Fix section (e.g., re-measure request count and compare against the under-50 target) to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The DNS/TCP/TLS latency point appears twice — "Each HTTP request incurs network overhead—DNS lookup, TCP connection, and TLS handshake add latency" in the intro and again as the first Quick Reference bullet — and the intro re-explains basic networking concepts Claude already knows. Otherwise lean, so not 2; the duplication and known-concept padding keep it below 4.

3 / 5

Actionability

Provides a concrete threshold ("Target under 50 requests for initial page load") and named techniques ("Bundle critical CSS/JS, use SVG sprites for icons"), but the body contains no executable code or commands — "Count the number of HTTP requests this page makes" states the goal without any method for counting. Not 2 because techniques and target are concrete; not 4 because specifics are deferred entirely to the reference file.

3 / 5

Workflow Clarity

A clear Check-then-Fix flow with measurement-oriented steps, and Code Review requires "describe the measurement method used to confirm the issue", giving a validation checkpoint. Falls short of 5 because there is no post-fix re-verification step (e.g., re-measure request count after applying fixes). Not 3: checkpoints for confirming the issue before changes are explicitly present.

4 / 5

Progressive Disclosure

The body is a concise overview (under 50 lines) with 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 with exactly that content. Content is appropriately split between summary and reference with easy navigation.

5 / 5

Total

15

/

20

Passed

Description

80%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 with an explicit trigger clause and concrete verification actions backed by named tools. Its main weakness is distinctiveness: the broad performance trigger terms could pull in sibling performance-audit skills rather than this HTTP-request-specific one.

Suggestions

Narrow the trigger terms to HTTP-request-specific phrases (e.g., "too many requests", "network waterfall", "request count") and drop or qualify "rendering delays", which belongs to main-thread/rendering skills rather than request minimization.

Briefly state the full capability set (audit, verify, fix recommendations, code review) so the 'what' matches what the skill body actually offers.

DimensionReasoningScore

Specificity

Lists several concrete actions with named tools ("auditing slow page loads", "Verify the actual bottleneck in DevTools, Lighthouse, or field data") but omits the fix and code-review capabilities the body actually covers, leaving minor gaps in coverage. Not 5 because coverage is incomplete; not 3 because it goes beyond 1-2 generic actions by naming specific tools.

4 / 5

Completeness

Explicitly answers both questions: "Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize HTTP requests" states when with concrete trigger phrases, and "Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes" states what it does. Anchor 4's deficiency ('when' could be more explicit) does not apply here.

5 / 5

Trigger Term Quality

Contains natural user phrases ("slow page loads", "heavy assets", "rendering delays", "DevTools", "Lighthouse") that map well to real user language. Missing common variations like "too many requests", "page speed", or "network waterfall", so it falls short of comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"heavy assets" and "rendering delays" are trigger territory of sibling performance skills (image optimization, main-thread/rendering work), creating real overlap risk in a performance-rule skill suite. The scoping phrase "related to Minimize HTTP requests" helps but doesn't fully separate it from closely related skills.

3 / 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/http-requests/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.