CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

subresource-integrity

Use when reviewing templates, rendered HTML, or shared components related to Add Subresource Integrity to external scripts. Validate the final browser-facing markup, not just the source framework abstraction.

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/subresource-integrity/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 review-style skill body with a clean Check/Fix/Explain/Code Review sequence and exemplary one-level progressive disclosure to references/rule.md. Its weaknesses are the duplicated 'why it matters' explanation of a concept Claude already knows, and the lack of any executable command or example inline — the hash-generation command and markup examples all live in the reference file.

Suggestions

Trim or remove the opening 'CDN compromise' paragraph — it explains a concept Claude already knows and is duplicated in references/rule.md's 'Why It Matters' section.

Inline the one-line hash-generation command (e.g. `curl -s <url> | openssl dgst -sha384 -binary | openssl base64 -A`) in the Fix section so it is executable without opening the reference.

Add a short verify step after Fix (re-check the rendered markup / re-inspect shared components) mirroring rule.md's Verification section, closing the workflow loop in the body itself.

DimensionReasoningScore

Conciseness

The opening paragraph ('When you load JavaScript from a CDN, you're trusting that CDN completely — if it's compromised, attackers can serve malicious JavaScript to all your users...') explains a concept Claude already knows, is duplicated nearly verbatim in references/rule.md's 'Why It Matters', and is repeated a third time by the Quick Reference bullet 'SRI blocks execution if the file hash doesn't match, preventing CDN compromise attacks'. Not 2 because the rest of the body is tight; not 4 because the same rationale appears in three places.

3 / 5

Actionability

Concrete attribute-level guidance is present ('Add integrity="sha384-..." to <script> and <link> tags', 'Always pair integrity with crossorigin="anonymous"', 'Find all external <script> and <link rel=stylesheet> tags... that load from CDNs and don't have integrity attributes'), but the body contains no executable code or command — 'Generate hashes with openssl or online tools' defers the actual command to references/rule.md. Not 4 because there is no inline code block or command; not 2 because the attribute guidance is specific and directly usable.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give an unambiguous sequence, with a concrete discovery step ('Find all external <script> and <link rel=stylesheet> tags in this HTML that load from CDNs and don't have integrity attributes. List each one.') and a targeted code-review step ('Flag exact elements, attributes, and routes where the rendered HTML violates the rule'). Not 5 because there is no explicit verify-after-fix step in the body — the verification steps live only in references/rule.md and are not linked into the workflow.

4 / 5

Progressive Disclosure

The body is a lean, well-sectioned overview with a clearly signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`'. The referenced file exists, holds all code examples and detail, and does not nest further references, so navigation is easy and the split is appropriate.

5 / 5

Total

15

/

20

Passed

Description

70%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 solid description with an explicit 'Use when' trigger clause, third-person voice, and a distinctive SRI niche. Its main weakness is that the 'what' is expressed only as a scoping directive ('validate the final markup') rather than concrete capabilities, and it omits the most natural trigger terms ('CDN', 'SRI').

Suggestions

State the concrete actions in the description, e.g. 'Adds integrity and crossorigin attributes to CDN-loaded script/link tags and generates SHA-384 hashes' — this would raise both specificity and completeness.

Include the natural trigger terms users would say for this need: 'CDN', 'SRI', 'integrity hash', 'script tags'.

DimensionReasoningScore

Specificity

Names the domain ('Add Subresource Integrity to external scripts') and 1-2 concrete actions ('reviewing templates, rendered HTML, or shared components', 'Validate the final browser-facing markup, not just the source framework abstraction'), but does not enumerate the specific capabilities of the skill (adding integrity attributes, generating SHA-384 hashes, pairing crossorigin). Not 4 because coverage of concrete actions stops at 'review' and 'validate'.

3 / 5

Completeness

Explicitly answers 'when' with a 'Use when reviewing templates, rendered HTML, or shared components...' trigger clause, and gives a 'what' directive ('Validate the final browser-facing markup, not just the source framework abstraction'). Not 5 because the 'what' is a scoping directive rather than a concrete statement of what the skill does (e.g., add integrity/crossorigin attributes and generate hashes); not 3 because both what and when are explicitly present.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'templates', 'rendered HTML', 'shared components', 'Subresource Integrity', 'external scripts', 'browser-facing markup'. Not 5 because very natural terms users would say for this need — 'CDN', 'SRI', 'script tags', 'integrity hash' — are absent.

4 / 5

Distinctiveness Conflict Risk

'related to Add Subresource Integrity to external scripts' pins a clear niche, but the broad opening trigger 'reviewing templates, rendered HTML, or shared components' is shared phrasing that could overlap with sibling HTML-review skills before the SRI qualifier applies. Not 5 due to this minor overlap risk; clearly above 3 because the SRI domain qualifier is distinctive.

4 / 5

Total

15

/

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/subresource-integrity/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.