CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

permissions-policy

Use when reviewing HTTP response headers for defense-in-depth security hardening on any web application.

Quality

73%

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

Quality

Content

85%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 content is well-structured for a simple single-purpose skill: lean quick-reference guidance, an unambiguous check-fix-verify flow, and a clean one-level pointer to a substantive reference file. The only notable gaps are a duplicated XSS rationale and the absence of a concrete header-inspection command in the body.

DimensionReasoningScore

Conciseness

The body is lean and includes genuinely useful non-obvious facts ('Previously called Feature-Policy — the old syntax is deprecated', iframe inheritance). However, the XSS blast-radius rationale is stated twice — in the intro paragraph ('reducing attacker capabilities even after a successful injection') and again in a Quick Reference bullet ('Restricting unused features limits the blast radius if your site is compromised by XSS') — which is a minor redundancy that could be trimmed, matching anchor 4 rather than 5.

4 / 5

Actionability

Provides copy-paste-ready syntax ('Permissions-Policy: camera=(), microphone=(), geolocation=()') and a concrete starting set in the Fix section ('Start with camera=(), microphone=(), geolocation=()'). Minor gap: no command for inspecting the live header (e.g. curl -I), and 'verify them against the effective production-like response' gives no method, so it falls short of anchor 5's fully executable coverage.

4 / 5

Workflow Clarity

This is a simple, non-destructive, single-purpose skill and the single action is unambiguous: deny unused features starting from the given set and expand based on application need. The Check → Fix → Explain → Code Review sequence is coherent, and a verification checkpoint is present ('verify them against the effective production-like response'), so the simple-skill exception applies for a score of 5.

5 / 5

Progressive Disclosure

The body is a clear overview (quick-reference facts inline) that points once, clearly signaled, to references/rule.md — verified to exist with real implementation content (allowlist syntax table, restricted-features table, code examples). One level deep, appropriately split, easy navigation — matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

50%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 has a clear, explicit trigger clause but never states what the skill does — the Permissions-Policy header itself is absent from the description. This weakens completeness, trigger-term quality, and distinctiveness against sibling security-header skills. All dimensions land at the middle anchor as a result.

Suggestions

State the 'what' explicitly, e.g. 'Checks and sets the Permissions-Policy HTTP response header to deny unused browser features (camera, microphone, geolocation). Use when reviewing security headers on a web application.'

Include the header names 'Permissions-Policy' and the deprecated 'Feature-Policy' as trigger terms — they are the natural phrases a user would say for this exact task.

Narrow the scope from 'any web application' / all 'HTTP response headers' to the Permissions-Policy header specifically to reduce conflict risk with sibling header-hardening skills (CSP, HSTS, X-Frame-Options).

DimensionReasoningScore

Specificity

Names the domain ('HTTP response headers', 'security hardening') and one concrete action ('reviewing'), but never states what the skill actually does — set or verify a Permissions-Policy header. Only one action verb is present, so it does not reach anchor 4's 'several specific actions'.

3 / 5

Completeness

The 'when' is explicit ('Use when reviewing HTTP response headers... on any web application'), but the 'what' is only weakly implied by the embedded gerund phrase — the skill's actual deliverable is never stated. This sits between anchor 2 ('only when present without what') and anchor 3, and does not reach 4 because there is no distinct what-statement.

3 / 5

Trigger Term Quality

'HTTP response headers', 'security hardening', and 'web application' are relevant keywords, but the most natural trigger a user would say — 'Permissions-Policy' or 'Feature-Policy' — plus common variants like 'security headers' are missing. Some relevant keywords without the key synonyms matches anchor 3.

3 / 5

Distinctiveness Conflict Risk

'Reviewing HTTP response headers for defense-in-depth security hardening on any web application' is somewhat specific but broadly overlaps sibling header-hardening skills (CSP, HSTS, X-Frame-Options, CORS). Because the description never names Permissions-Policy, a header-security query for a different header could trigger this skill, so it does not reach anchor 4's 'minor overlap risk'.

3 / 5

Total

12

/

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/permissions-policy/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.