CtrlK
BlogDocsLog inGet started
Tessl Logo

security-review

在添加身份验证、处理用户输入、操作机密信息(Secrets)、创建 API 端点以及实现支付/敏感功能时使用此技能。提供全面的安全检查清单和模式。

65

Quality

77%

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 ./docs/ja-JP/skills/security-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable code and checklists, but it is long and verbose for a context-window-conscious skill, organized as a flat reference rather than a sequenced workflow, and monolithic with no progressive file structure. Tightening explanatory prose and adding an explicit validation-feedback sequence would raise the weaker dimensions.

Suggestions

Trim tutorial-style explanations Claude already knows (e.g., why localStorage is XSS-vulnerable, why SQL concatenation is dangerous) and consolidate the per-category '验证步骤' sub-checklists that restate the code above them to improve conciseness.

Add an explicit sequenced workflow with validate→fix→retry checkpoints for destructive or batch security operations (e.g., secret rotation, dependency upgrades) so workflow clarity can reach level 3.

Split the large single-file body using progressive disclosure — keep a concise core checklist in SKILL.md and move the per-category code examples and pre-deploy checklist into referenced files under references/.

DimensionReasoningScore

Conciseness

The ~490-line body is mostly concrete code and checklists, but it includes tutorial-style explanations Claude already knows (e.g., localStorage is XSS-vulnerable, SQL string concatenation is dangerous) and redundant per-category sub-checklists that restate what the code shows, so it could be tightened rather than reaching level 3.

2 / 3

Actionability

It provides fully executable, copy-paste-ready code across categories (zod validation, parameterized queries, httpOnly cookies, DOMPurify, CSRF, rate limiting, RLS SQL, wallet verification) plus concrete bash commands and checklists, matching the level-3 anchor.

3 / 3

Workflow Clarity

The content is a categorized reference with per-category validation steps and a pre-deploy gate, but it lacks an explicit sequenced workflow with validate→fix→retry feedback loops for destructive/batch operations, which per the guideline caps workflow clarity at 2.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is a single ~490-line file with everything inline; it is well-sectioned (not a monolithic wall) but content that could be split into separate reference files is kept inline, matching level 2 rather than level 3.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 strong: it uses third-person voice, explicitly pairs a 'what' statement with concrete 'when' triggers, and lists natural trigger terms a user would say. The only soft spot is specificity, where the capability is summarized as a generic 'checklist and patterns' rather than enumerated concrete actions.

DimensionReasoningScore

Specificity

Names the security domain and several concrete trigger situations (auth, user input, secrets, API endpoints, payments), but the capability statement ('提供全面的安全检查清单和模式') is a generic summary rather than a list of multiple specific concrete actions, so it does not reach level 3.

2 / 3

Completeness

It explicitly answers both 'what' (provides a comprehensive security checklist and patterns) and 'when' (使用此技能 with explicit triggers), matching the level-3 anchor.

3 / 3

Trigger Term Quality

The description covers natural terms users would actually say — 身份验证, 用户输入, 机密信息/Secrets, API 端点, 支付/敏感功能 — giving good coverage of common trigger phrasings.

3 / 3

Distinctiveness Conflict Risk

The trigger set (auth, secrets, API endpoints, payments) defines a distinct security-review niche tied to specific high-risk coding activities, making conflict with other skills unlikely.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xu-xiang/everything-claude-code-zh
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.