CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

angular-security

Harden Angular apps against XSS, CSP violations, and unauthorized access. Use when implementing XSS protection, Content Security Policy, or auth guards in Angular.

Quality

80%

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/angular/angular-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 delivers specific, actionable Angular security guidance with concrete API names and a sensible split of detail into a real one-level-deep reference file. Its main weaknesses are redundancy — the Anti-Patterns and checklist sections restate the Guidelines — plus a dangling "common/security-standards" reference and an orphaned P0 heading that slightly muddy navigation and structure.

Suggestions

Remove the redundancy between Guidelines, Anti-Patterns, and the CSP/secret checklist: the localStorage/HttpOnly advice and the no-secrets advice each appear twice; consolidate them into one place.

Fix or remove the dangling "common/security-standards" reference — it is not a file in the bundle; either link an actual path with a one-line description of what it contains or drop it.

Fix the heading hierarchy: the standalone "## **Priority: P0 (CRITICAL)**" heading is immediately followed by another H2 (Principles), which reads as a stray label; fold it into the title or the Principles section, and consider extending the checklist to cover XSS and route-guard verification.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Angular knowledge, but the Anti-Patterns section ("No localStorage for tokens: Use HttpOnly cookies", "No secrets in source... Never embed API keys") and the CSP/secret checklist ("Do not put API keys or other secrets in the compiled bundle") repeat the Guidelines section nearly verbatim, and the trust-marking checklist item restates the Principles bullet. This matches the mostly-efficient-but-could-be-tightened anchor at 3 rather than 4, where only minor instances of over-explanation would remain after trimming.

3 / 5

Actionability

The guidance names specific executable APIs and directives — "DomSanitizer.sanitize(SecurityContext.HTML, content)", "inject(Router).createUrlTree(['/login'])", "canActivate: [authGuard]", "script-src 'nonce-{nonce}'" — which is mostly concrete, actionable direction with minor gaps. It falls short of 5 because interceptor token attachment and CSP header configuration are described but not shown, and the body itself contains no complete copy-paste code example (full code lives in the reference file).

4 / 5

Workflow Clarity

The topical organization (Principles → Guidelines → Anti-Patterns → checklist) gives a clear structure for applying the guidance, and the closing "CSP and secret checklist" provides explicit checkpoints. It is not a 5 because the checklist covers only CSP and secrets (no XSS or guard verification), the orphaned "## **Priority: P0 (CRITICAL)**" heading sits confusingly between the title and Principles, and there is no sequence for how to apply the three areas together; it is clearly above 3 because the per-topic direction is unambiguous and checkpoints are present.

4 / 5

Progressive Disclosure

The body is a short overview with a well-signaled, one-level-deep reference that resolves to a real bundle file ([Security Best Practices](references/security-best-practices.md)), and the detailed code examples are appropriately split into that file. It misses 5 because the second reference, "common/security-standards", is a bare unlinked path that does not exist in the bundle (references/ contains only security-best-practices.md), leaving a dangling navigation entry; this is a minor organization gap consistent with the 4 anchor rather than the buried/unclear-references pattern at 3.

4 / 5

Total

15

/

20

Passed

Description

87%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 strong description: it clearly states what the skill does and when to use it, with concrete trigger phrases and explicit Angular scoping that keeps conflict risk low. The only weakness is that the capability side is compressed into a single general verb plus threat names rather than multiple distinct concrete actions, and a few natural synonyms (sanitizer, route guard) are absent.

DimensionReasoningScore

Specificity

The description names the domain ("Angular apps") and three concrete security concerns ("XSS, CSP violations, and unauthorized access") plus concrete implementation targets ("auth guards"), matching the several-specific-actions anchor with minor gaps. It falls short of 5 because the actions are framed as one general verb ("Harden") rather than multiple distinct concrete operations, and above 3 because the coverage of three named threat areas is more comprehensive than 1-2 actions.

4 / 5

Completeness

It explicitly answers both questions: the "what" ("Harden Angular apps against XSS, CSP violations, and unauthorized access") and the "when" with concrete trigger phrases ("Use when implementing XSS protection, Content Security Policy, or auth guards in Angular"). This matches the 5 anchor's pattern of what + explicit when with concrete triggers; a 4 would require the when clause to be less explicit or specific than it is.

5 / 5

Trigger Term Quality

"XSS protection", "Content Security Policy", and "auth guards" are natural phrases a developer would say when needing this skill, giving good keyword coverage. A few natural terms are missing (e.g., "sanitizer", "route guard", "innerHTML"), so it does not reach the comprehensive-synonyms anchor at 5, but it is clearly above the some-keywords-missing-variants anchor at 3.

4 / 5

Distinctiveness Conflict Risk

The explicit "Angular" scoping in both halves establishes a clear niche with distinct triggers, so it is unlikely to fire for generic security or non-Angular skills. The trigger phrases (XSS, CSP, auth guards) are specific enough that conflict risk is minimal, matching the 5 anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

skills/angular/angular-security/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.