Tessl • The package manager for agent skills

SkillPublic

signals-scout-csp-violations

Signals scout for Content Security Policy violations. Watches `$csp_violation` events for blocked-URL clusters, per-directive bursts, post-deploy regressions, and suspicious third- party domains.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./products/signals/skills/signals-scout-csp-violations/SKILL.md

Quality

Content

81%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 highly actionable, well-sequenced operational skill body with executable SQL and clear validation checkpoints. Its main weakness is repetition of the push-path and standing-enforced points across sections, which inflates length without adding guidance.

Suggestions

Consolidate the push-path / source_product explanation into one section and cross-reference it elsewhere instead of restating it in Get oriented, Decide, and How this relates.

State the standing-enforced blind spot once in its dedicated section and reference it from the baseline close-out rather than re-explaining the rationale each time.

Consider extracting the four SQL queries and the scratchpad key catalog into a references file to slim the SKILL.md body, now that the structure already supports one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is rich in genuinely CSP-scout-specific guidance Claude would not know, but the push-path / source_product distinction and the standing-enforced blind spot are restated three to four times across sections and could be tightened without losing clarity.	3 / 5
Actionability	Provides multiple complete, executable ClickHouse SQL queries, concrete scratchpad key formats, copy-paste gh commands, and triage tables — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Clear sequence (Orient → Explore → Save memory → Decide → Close out) with explicit validation checkpoints, feedback loops (re-validate against code, check in-flight PRs), and checklists (Disqualifiers, When to stop); the batch reporting operation is well-guarded.	5 / 5
Progressive Disclosure	Well-sectioned with clearly signaled one-level-deep references to report-contract.md; no bundle files exist so bulk content is inline, but organization is strong with minor gaps.	4 / 5
	Total	17 / 20 Passed

Description

75%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 specific, distinctive description that clearly states what the scout does, but it omits an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when…' sentence referencing CSP violations or blocked-URL reports would raise it.

Suggestions

Add an explicit 'Use when …' trigger clause (e.g. 'Use when investigating Content Security Policy violations, blocked-URL clusters, or per-directive CSP bursts') to satisfy the completeness dimension.

Include a couple more natural synonyms users might say — 'CSP reports', 'CSP headers', 'blocked scripts' — to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (CSP violations) and multiple concrete actions — 'blocked-URL clusters, per-directive bursts, post-deploy regressions, and suspicious third-party domains' — giving comprehensive coverage of what the scout watches for.	5 / 5
Completeness	The 'what' is clearly stated, but there is no explicit 'Use when…' trigger clause; per the rubric guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes both the full term 'Content Security Policy violations' and the natural acronym 'CSP', plus violation-type phrases; a few common synonyms (e.g. 'CSP reports', 'CSP headers') are absent, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A narrowly scoped CSP-violations scout with distinctive triggers and minimal overlap risk against any other skill.	5 / 5
	Total	17 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: PostHog/posthog
Path: products/signals/skills/signals-scout-csp-violations/SKILL.md
Revision: 130f3a1

Reviewed: 29 days ago

Discovery Implementation Validation

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.

signals-scout-csp-violations

Table of Contents

Is this your skill?