CtrlK
BlogDocsLog inGet started
Tessl Logo

receiving-code-review

收到代码审查反馈后、实施建议之前使用,尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证,而非敷衍附和或盲目执行

64

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 ./skills/receiving-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced behavioral skill with strong validation checkpoints and concrete examples. The main weakness is repetition of the same forbidden-phrase examples across multiple sections, which inflates the token budget without adding guidance.

Suggestions

Consolidate the '你说得太对了/好观点/感谢' forbidden-phrase examples into one canonical list and reference it from 确认正确的反馈 and 真实案例 instead of repeating them.

The 真实案例 section reuses the 不明确项 example already shown in 处理不明确的反馈; drop the duplicate or replace it with a distinct case.

Merge '禁止的回应' into '响应模式' or '确认正确的反馈' to reduce section count and cross-section redundancy.

DimensionReasoningScore

Conciseness

The body avoids explaining basic concepts Claude already knows, but the forbidden '你说得太对了/好观点' examples recur across 禁止的回应, 确认正确的反馈, and 真实案例, which is unnecessary redundancy that could be tightened.

3 / 5

Actionability

Concrete ✅/❌ dialogue examples, a copy-paste GitHub replies command, a YAGNI grep procedure, and specific push-back conditions give fully actionable, ready-to-use guidance for an instruction-only skill.

5 / 5

Workflow Clarity

The 6-step response model, implementation order with per-item testing and regression verification, the 5-check external-reviewer list, and the self-correction feedback loop provide explicit validation checkpoints and error-recovery loops.

5 / 5

Progressive Disclosure

Sections are clearly headed and logically ordered in a self-contained file with no need for external references, but the skill exceeds 50 lines and has minor redundancy between sections, so it is not a clean 5.

4 / 5

Total

17

/

20

Passed

Description

73%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 has a strong, explicit trigger condition and a clear niche, but the 'what it does' is expressed as an approach/attitude rather than concrete actions. It is well-targeted and distinctive, with good natural trigger terms.

Suggestions

Add one or two concrete actions to the 'what' (e.g. '对照代码库验证反馈、有理有据地反驳、逐项测试修复') so capabilities are explicit rather than implied by '技术严谨性和验证'.

Include a common synonym such as '审查意见' or 'review comments' alongside '代码审查反馈' to broaden natural trigger coverage.

Consider adding the English term 'code review' to the description to improve trigger matching for bilingual users.

DimensionReasoningScore

Specificity

Names the domain ('代码审查反馈') and 1-2 actions ('技术严谨性和验证') but the actions are abstract attitudes rather than concrete capabilities, so coverage is not comprehensive.

3 / 5

Completeness

An explicit and specific 'when' clause is present ('收到代码审查反馈后、实施建议之前…尤其当反馈不明确或技术上有疑问时'), and a 'what' is given ('技术严谨性和验证,而非敷衍附和或盲目执行'), but the 'what' is attitude-focused rather than listing concrete actions.

4 / 5

Trigger Term Quality

Natural trigger terms ('代码审查反馈', '反馈不明确', '技术上有疑问') match what a user would say, though a few common synonyms like '审查意见' are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (responding to code review feedback before implementation) with distinct situational triggers, giving minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
jnMetaCode/superpowers-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.