CtrlK
BlogDocsLog inGet started
Tessl Logo

springboot-security

Java Spring Boot 服务中认证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全性的 Spring Security 最佳实践。

82

1.08x
Quality

56%

Does it follow best practices?

Impact

100%

1.08x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-CN/skills/springboot-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%

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

This is a solid, comprehensive Spring Security reference skill with excellent actionability — nearly every section has executable Java code with good/bad comparisons. Its main weaknesses are moderate verbosity (some obvious security advice that Claude already knows) and lack of explicit workflow sequencing or verification steps between security implementation phases. The checklist at the end partially compensates but doesn't constitute a true feedback loop.

Suggestions

Add verification/testing steps after key sections (e.g., 'Test with: curl -H "Authorization: Bearer invalid" to verify 401 response') to create feedback loops for security configurations.

Trim obvious security advice Claude already knows (e.g., 'never store plaintext passwords', 'never concatenate strings in SQL') and focus on Spring-specific implementation patterns only.

Consider splitting detailed topics (rate limiting with Bucket4j, Vault integration, dependency scanning CI setup) into separate referenced files to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The skill is mostly efficient with good code examples, but includes some unnecessary explanations (e.g., 'When to activate' section largely restates obvious triggers, and some bullet points explain concepts Claude already knows like 'never store plaintext passwords'). The content could be tightened by removing obvious security advice and focusing purely on Spring-specific patterns.

2 / 3

Actionability

Excellent actionability throughout — nearly every section includes fully executable, copy-paste-ready Java code examples with clear good/bad comparisons. The code covers JWT filters, authorization annotations, Bean Validation DTOs, parameterized queries, password encoding, CSRF config, CORS config, rate limiting filters, and YAML configuration examples.

3 / 3

Workflow Clarity

The skill covers many security topics but presents them as independent sections rather than a sequenced workflow. The 'Release Checklist' at the end provides a useful validation checkpoint, but there's no explicit workflow for how to apply these security measures in sequence, and no feedback loops for verifying security configurations are correct (e.g., testing that auth filters work, validating security headers).

2 / 3

Progressive Disclosure

The content is well-organized with clear section headers, but it's a long monolithic file (~200+ lines) with no references to external files for detailed topics like Vault integration, Bucket4j advanced config, or OWASP setup. Topics like rate limiting and dependency security could benefit from separate reference files. However, given no bundle files exist, the inline approach is acceptable but not ideal.

2 / 3

Total

9

/

12

Passed

Description

47%

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 effectively identifies its domain (Spring Security in Java Spring Boot) and lists relevant security subtopics with good trigger terms. However, it lacks concrete action verbs describing what the skill does and entirely omits a 'Use when...' clause, which significantly weakens its utility for skill selection. Adding explicit trigger guidance and action-oriented language would substantially improve it.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks about securing a Spring Boot application, configuring Spring Security, or implementing authentication, CSRF protection, or rate limiting.'

Replace the passive 'best practices' framing with concrete actions, e.g., 'Configures authentication/authorization, implements CSRF protection, manages secrets, sets security headers, and audits dependencies in Java Spring Boot services.'

Consider specifying the output format or deliverable, e.g., 'Provides code examples, configuration snippets, and security audit checklists for Spring Security implementations.'

DimensionReasoningScore

Specificity

The description names the domain (Java Spring Boot / Spring Security) and lists several specific areas (authentication/authorization, validation, CSRF, secrets, headers, rate limiting, dependency security), but these are topic areas rather than concrete actions. It doesn't specify what actions are performed (e.g., 'configure', 'audit', 'implement').

2 / 3

Completeness

The description answers 'what' (Spring Security best practices across several areas) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat weak (best practices rather than concrete actions), so this scores a 1.

1 / 3

Trigger Term Quality

Contains strong natural trigger terms that users would actually say: 'Spring Security', 'Spring Boot', 'authentication', 'authorization', 'CSRF', 'rate limiting', 'dependency security', 'validation', 'headers', 'secrets'. These cover a good range of terms a developer would use when seeking security guidance.

3 / 3

Distinctiveness Conflict Risk

The focus on Spring Security specifically is fairly distinctive, but 'best practices' is broad and could overlap with general Java security skills, code review skills, or other Spring-related skills. The listing of specific subtopics (CSRF, rate limiting, etc.) helps somewhat but doesn't fully eliminate overlap risk.

2 / 3

Total

8

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
affaan-m/everything-claude-code
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.