java-backend

用于 Java 后端面试出题；优先围绕 Java 核心、MySQL、Redis、Spring 与项目实战，追问设计取舍、故障处理和性能优化。

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./app/src/main/resources/skills/java-backend/SKILL.md

Quality

Content

78%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 content is concise, well-structured, and gives actionable interviewer guidance with a clear questioning sequence, but it references resource files that are not present in the bundle, breaking progressive disclosure, and it lacks example questions to make the guidance fully concrete.

Suggestions

Create the referenced bundle files (java.md, mysql.md, redis.md, spring.md, system-design-scenarios.md) under a references/ directory, or remove the references if the detail is not yet available.

Add 2-3 example interview questions per category to make the probing guidance concrete and copy-paste ready.

Include a brief feedback checkpoint in the workflow, e.g. when a candidate answer is vague, escalate probing per instruction 4 before moving on.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — short Overview, five tight numbered instructions, and a compact resource map — with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Concrete, specific guidance is provided (question ordering '使用经验 -> 原理机制 -> 边界条件 -> 优化与故障' and concrete probing targets like '实现细节、失败场景、回滚方案'), but no example questions or question templates are included, leaving minor gaps.	4 / 5
Workflow Clarity	A clear sequenced workflow is present (the question-progression order and numbered instructions), and no destructive/batch validation cap applies to an interview skill; it falls short of 5 only because there are no explicit feedback loops or checkpoints.	4 / 5
Progressive Disclosure	The in-body structure is good with clearly signaled one-level-deep references by category, but the referenced files (java.md, mysql.md, redis.md, spring.md, system-design-scenarios.md) do not exist in any bundle directory, so the navigation promise is broken.	3 / 5
	Total	16 / 20 Passed

Description

66%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.

The description is specific and uses natural trigger terms within a clear Java-backend-interview niche, but it omits an explicit 'Use when...' trigger clause, which caps completeness and leaves the activation context only weakly implied.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when preparing or conducting a Java backend interview.'

Include natural synonyms or variations users might say (e.g. 'Java 后端面试题', 'Spring 面试', '后端校招/社招出题') to broaden trigger coverage.

Tighten the 'when' context by naming the triggering scenarios (interview prep, mock interview, question bank generation) rather than only the '用于' purpose.

Dimension	Reasoning	Score
Specificity	Names the domain (Java backend interview question generation) and lists several concrete topic areas and probing directions (Java core, MySQL, Redis, Spring, design tradeoffs, failure handling, performance optimization); minor gaps in coverage rather than minimal, so above the '1-2 concrete actions' anchor.	4 / 5
Completeness	The 'what' is clear (interview question generation with topic focus), but there is no explicit 'Use when...' clause — '用于...出题' only weakly implies the trigger, capping completeness at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('Java 后端面试', 'Java', 'MySQL', 'Redis', 'Spring') with good coverage, but lacks synonyms or file-extension variants that would push it to comprehensive.	4 / 5
Distinctiveness Conflict Risk	The interview-question-generation niche is mostly distinct with clear triggers, though broad terms like 'Java', 'MySQL', 'Spring' carry minor overlap risk with general Java development skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Snailclimb/interview-guide
Path: app/src/main/resources/skills/java-backend/SKILL.md
Commit: b2d1ca0

Reviewed: 19 days ago

Table of Contents

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.