CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

consent-mode

Use when auditing slow page loads, heavy assets, or rendering delays related to Implement Google Consent Mode v2. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

68%

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

Quality

Content

65%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 body is a concise, well-organized overview with a clean one-level reference to `references/rule.md`, which is its main strength. However, it stays at the level of intent — no code, no concrete verification method, and no validation checkpoints — so actionability and workflow clarity are middling.

Suggestions

Add a concrete check method inline, e.g. 'In DevTools Network tab, confirm Google pings include the `gcd` parameter carrying the current ad_storage/analytics_storage and ad_user_data/ad_personalization states.'

Include a minimal executable snippet in the Fix section, such as the gtag('consent', 'default', {...}) call for the two new consent types, instead of only naming them.

Make the Code Review section specific to consent mode (tag firing order, default consent before GTM load, ping contents) instead of the generic network/CPU/layout template, and add a post-fix verification step to close the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is short (~35 lines) and mostly lean: the Quick Reference bullets carry real specifics ("Ensure the `gcd` parameter is present in pings to Google services") and details are delegated to `references/rule.md`. Minor over-explanation could be trimmed — the opening 'Consent Mode v2 is essential for adhering to privacy regulations (like GDPR)...' background sentence, and the generic Code Review paragraph. This is anchor 4 ('efficient; minor instances of over-explanation'), not anchor 5 given that templated paragraph.

4 / 5

Actionability

Some concrete guidance exists — "Update your GTM or gtag.js implementation to support the new `ad_user_data` and `ad_personalization` consent types" and the pointer to `references/rule.md` for code — but there is no executable code, command, or concrete check method in the body ('Verify that Google Consent Mode v2 is correctly implemented' says what to do, not how). This matches anchor 3 ('some concrete guidance but incomplete; missing key details') rather than anchor 4, which requires mostly executable guidance.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a rough sequence, but there are no validation checkpoints or feedback loops: the Check section gives no method for verifying consent states, and nothing confirms a fix worked. This fits anchor 3 ('sequence present but checkpoints missing or implicit'); anchor 4 would require most checkpoints to be explicit, and the operation is not destructive/batch so no hard cap applies.

3 / 5

Progressive Disclosure

The body is a clear, well-sectioned overview that delegates all implementation detail to a single one-level-deep reference, clearly signaled: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists with that content. Per the rubric's simple-skill note, a short, well-organized skill with a single clearly signaled reference earns anchor 5.

5 / 5

Total

15

/

20

Passed

Description

58%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 explicitly answers both what and when with concrete tool names, but its framing is built around generic performance auditing while the skill body is about Consent Mode v2 compliance and implementation. Trigger terms and the 'what' statement are misaligned with the skill's actual purpose, limiting trigger quality, specificity, and distinctiveness.

Suggestions

Rewrite the description around the skill's actual purpose, e.g. 'Verify, fix, and explain Google Consent Mode v2 implementations... Use when users mention Consent Mode v2, consent states, gd pings, or GDPR-related analytics requirements.'

Include trigger terms a user would naturally say for this skill — 'consent mode', 'GDPR', 'ad_user_data', 'ad_personalization', 'GTM consent', 'gtag.js' — rather than generic performance-audit phrases that conflict with general performance skills.

State the 'what' more comprehensively by covering the skill's Check/Fix/Explain capabilities (verifying consent states, updating GTM or gtag.js, explaining the Consent Mode v2 requirement) instead of only 'verify the actual bottleneck'.

DimensionReasoningScore

Specificity

The description names the domain and a few concrete actions — "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data" — but coverage is not comprehensive: the skill's core consent-implementation capabilities (check consent states, update GTM/gtag.js, explain compliance) are absent. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') better than anchor 4, whose 'minor gaps' would require the description to reflect most of what the skill does.

3 / 5

Completeness

Both parts are explicitly present: 'when' via "Use when auditing slow page loads, heavy assets, or rendering delays related to Implement Google Consent Mode v2" and 'what' via "Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes". Not anchor 5 because the 'what' is narrow and misaligned with the skill's full Check/Fix/Explain scope, so it is not a complete, concrete statement of what the skill does.

4 / 5

Trigger Term Quality

It includes some natural performance keywords ("slow page loads", "rendering delays", "Lighthouse", "field data") but misses the phrases a user needing this skill would actually say ("implement consent mode", "GDPR analytics", "ad_user_data", "GTM consent") as well as common performance variations ("page speed", "Core Web Vitals"). Applying the guideline 'would a user naturally say this when they need this skill?', the trigger framing targets generic performance auditing rather than the skill's consent-mode purpose, fitting anchor 3 ('relevant keywords but missing common variations or synonyms') more than anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Implement Google Consent Mode v2" is a distinct niche, but the trigger phrases ("slow page loads, heavy assets, or rendering delays") are generic performance-audit language that overlaps with any general performance skill, so the description could fire for the wrong skill. This is 'somewhat specific but could still overlap with similar skills' (anchor 3); anchor 4 would require trigger terms that are mostly unique to this skill.

3 / 5

Total

13

/

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/consent-mode/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.