CtrlK
BlogDocsLog inGet started
Tessl Logo

permissions-policy

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

60

Quality

70%

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

72%

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 well-structured, actionable overview with a real one-level-deep reference, but it has minor redundancy and an abstract verification step that prevent top marks on conciseness and workflow clarity.

Suggestions

Remove the duplicated XSS blast-radius statement, keeping it in only the intro or only the Quick Reference.

Make the verification step concrete, e.g. 'Verify with: curl -sI https://example.org | grep -i permissions-policy' in the Code Review section.

Tighten the generic Check/Explain sections to Permissions-Policy-specific guidance rather than boilerplate verbs.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the XSS blast-radius benefit is stated twice (intro and Quick Reference bullet 4) and the Check/Fix/Explain/Code Review sections read as generic boilerplate, so it could be tightened rather than earning the lean level-3 anchor.

2 / 3

Actionability

It provides concrete, copy-paste-ready header syntax ('Permissions-Policy: camera=(), microphone=(), geolocation=()') and a specific Fix directive, giving fully actionable guidance appropriate for an instruction-only skill.

3 / 3

Workflow Clarity

A Check -> Fix -> Code Review sequence is present, but the verification checkpoint ('verify them against the effective production-like response') is abstract with no concrete command (e.g. curl -I), so checkpoints are implicit rather than explicit.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview that clearly signals a single one-level-deep reference ('references/rule.md') for full implementation details, and that bundle file exists, matching the well-organized overview anchor.

3 / 3

Total

10

/

12

Passed

Description

67%

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 is concise and includes an explicit 'Use when' trigger with a clear domain, but it stays generic about 'HTTP response headers' rather than naming Permissions-Policy, which weakens specificity, trigger coverage, and distinctiveness.

Suggestions

Name the Permissions-Policy header explicitly, e.g. 'Set and review the Permissions-Policy HTTP response header to disable unused browser features.'

Add natural trigger terms users would say, such as 'Permissions-Policy', 'Feature-Policy', 'browser feature restrictions', or 'camera/microphone permissions'.

Differentiate from sibling security-header skills by scoping the trigger to Permissions-Policy/Feature-Policy rather than generic 'HTTP response headers'.

DimensionReasoningScore

Specificity

Names the domain ('HTTP response headers') and a concrete action ('reviewing ... for defense-in-depth security hardening') but offers only a single action rather than multiple specific concrete actions, so it falls short of the level-3 anchor.

2 / 3

Completeness

An explicit 'Use when ...' trigger states when to invoke it, and the same phrase conveys what it does (reviewing headers for hardening), clearly answering both what and when; not capped at 2 because the trigger clause is present.

3 / 3

Trigger Term Quality

It includes relevant natural terms ('HTTP response headers', 'security hardening', 'web application') but refers to headers generically rather than naming 'Permissions-Policy' or common variations users would say, leaving coverage incomplete.

2 / 3

Distinctiveness Conflict Risk

The niche ('HTTP response headers ... security hardening') is specific, but phrasing it as generic response headers rather than the Permissions-Policy header means it could overlap with sibling security-header skills (CSP, HSTS, X-Frame-Options).

2 / 3

Total

9

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.