CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend

用于前端工程面试出题;覆盖 JavaScript、React/Vue、浏览器原理和性能优化,强调业务实战与工程化能力。

52

Quality

57%

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/frontend/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is commendably concise and offers specific interview directives, but it functions as a guideline list rather than a sequenced workflow, and its referenced resource files do not exist in the bundle.

Suggestions

Provide the referenced files (javascript.md, react-vue.md, browser.md) or remove the dead references so progressive disclosure resolves correctly.

Add 1–2 concrete example questions or a question template to make the guidance copy-paste ready and raise actionability.

Reframe the numbered guidelines into a sequenced interview flow with checkpoints (e.g. warm-up → deep-dive → metrics → edge cases) to improve workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean (~20 lines) with no padding and no explanation of concepts Claude already knows; every line is direct guidance, fitting 'lean and efficient; every token earns its place'.

3 / 3

Actionability

Guidance is specific and includes concrete metrics (FCP/LCP、错误率、包体积) and topics, but it directs the interviewer's behavior without providing ready-to-use example questions or templates, fitting 'some concrete guidance but incomplete'.

2 / 3

Workflow Clarity

The five numbered items are guidelines rather than a sequenced workflow, and there are no validation checkpoints or feedback loops; this fits 'steps listed but validation gaps; checkpoints missing'.

2 / 3

Progressive Disclosure

It signals one-level-deep categorized references (javascript.md, react-vue.md, browser.md), but those referenced files are not present in the bundle, so navigation is broken; this fits 'references present but not clearly signaled / could be better organized'.

2 / 3

Total

9

/

12

Passed

Description

50%

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 conveys a clear domain and scope but reads as a capability summary rather than a trigger-rich invocation guide; it lacks an explicit 'Use when' clause and concrete action verbs.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g. 'Use when conducting or preparing frontend engineering interviews') to raise completeness.

Replace the generic '覆盖' with concrete actions (e.g. '生成、追问、评估前端面试题') to improve specificity.

Include natural trigger variations users would say (e.g. '前端面试', 'React/Vue 面试题', '性能优化提问') to strengthen trigger-term quality.

DimensionReasoningScore

Specificity

Names the domain (前端工程面试出题) and several covered areas (JavaScript、React/Vue、浏览器原理、性能优化), but uses a generic 'covers' verb rather than listing multiple concrete actions like 'extract/fill/merge', matching the 'names domain and some actions' anchor.

2 / 3

Completeness

It states what the skill does (interview question generation across frontend topics) but provides no explicit 'Use when...' trigger clause; per guidelines a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant natural keywords a user might say (JavaScript、React/Vue、浏览器、性能优化), but lacks common trigger phrasing and variations, fitting 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The frontend-interview niche is fairly specific, but without explicit trigger terms it could still overlap with general interview or coding skills, fitting 'somewhat specific but could still overlap'.

2 / 3

Total

8

/

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