CtrlK
BlogDocsLog inGet started
Tessl Logo

algorithm

用于算法面试出题;重点评估复杂度分析、边界处理和优化能力,区分背题与真实理解。

60

Quality

68%

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 ./app/src/main/resources/skills/algorithm/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a concise, actionable interview playbook with a clear step sequence, and it organizes content into well-labeled sections. Its main weakness is a dangling reference to a bundle file that does not exist, which undermines the progressive-disclosure structure.

Suggestions

Add the missing references/algorithm-data-structures.md bundle file so the categorized reference mapping actually resolves.

Include one or two concrete example interview exchanges or sample questions to move actionability from mostly-executable to copy-paste ready.

Add a brief checkpoint between steps (e.g., confirm the candidate's baseline answer is correct before escalating to edge cases) to make the workflow transitions explicit.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line is actionable instruction and every token earns its place.

5 / 5

Actionability

Each instruction gives concrete, specific guidance with examples ("剪枝、单调结构、预处理、空间换时间"; "不变式/归纳/反证任一即可"), but it lacks full example questions or interview-exchange templates that would make it copy-paste ready.

4 / 5

Workflow Clarity

The five numbered instructions form a clear, well-sequenced interview flow (articulate → diversify → probe edges → push optimization → require proof), with only minor implicitness in the transitions between steps.

4 / 5

Progressive Disclosure

Sections (Overview/Instructions/Additional Resources) and a clearly signaled one-level reference mapping exist, but the referenced file algorithm-data-structures.md is not present in the bundle, breaking navigation.

3 / 5

Total

16

/

20

Passed

Description

58%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 concrete and clearly niched to algorithm-interview question setting, but it lacks an explicit "when to use" trigger clause, leaving its activation guidance implicit. Trigger terms are present but not surfaced as natural phrases.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing algorithm interview questions or assessing a candidate's complexity analysis and optimization thinking."

Surface natural user phrases such as "算法面试题", "复杂度分析", "优化思路" as explicit trigger keywords rather than burying them in a purpose statement.

Include a brief mention of deliverable form (e.g., oral/written questions) so the "what" covers both the task and its output.

DimensionReasoningScore

Specificity

Lists several concrete evaluation focuses — "复杂度分析、边界处理和优化能力" and "区分背题与真实理解" — naming the domain with multiple specific actions, though it stops short of exhaustive coverage.

4 / 5

Completeness

The "what" is clear (algorithm interview question setting that evaluates complexity, boundary handling, and optimization), but there is no "Use when..." or equivalent explicit trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Contains natural terms a user might say ("算法面试", "复杂度分析", "优化") but they are embedded in a purpose statement rather than surfaced as explicit trigger phrases, and common synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

"算法面试出题" is a clear niche with distinct triggers and minimal conflict risk, though it could still overlap slightly with general interviewing or coding skills.

4 / 5

Total

14

/

20

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
Snailclimb/interview-guide
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.