CtrlK
BlogDocsLog inGet started
Tessl Logo

security

MUST be used whenever fixing security issues in a Flows app, or before shipping any feature that handles credentials, user input, or external data. This skill finds AND fixes security problems — it does not just report them. Do NOT skip this when the user asks for a security fix, security hardening, or vulnerability remediation — run every step in order. Triggers: security, security fix, security hardening, vulnerability, XSS, injection, credentials, secrets, auth, authentication, authorization, token, sensitive data, input validation, CORS, CSP, dependency audit.

69

1.07x
Quality

77%

Does it follow best practices?

Impact

97%

1.07x

Average score across 1 eval scenario

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/security/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

97%

7%

Harden the Asset Explorer App

Vite security config and URL param validation

Criteria
Without this skill
With this skill

X-Frame-Options header

100%

100%

X-Content-Type-Options header

100%

100%

CSP header present

100%

100%

CSP cognitedata.com allowlist

0%

100%

define block removed

100%

100%

Zod in package.json

100%

100%

Zod schema defined

100%

70%

safeParse used

100%

100%

as-casts on searchParams removed

100%

100%

Nullish fallback handling

100%

100%

Repository
cognitedata/builder-skills
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

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.