CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

steve-jobs-perspective

乔布斯的视角:产品判断与评审、取舍决策、对人对事的直接反馈。说「用乔布斯的视角」「乔布斯会怎么看」「切换到乔布斯」「让乔布斯评一下」时使用;不在一般性问题上自动触发。

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-built persona skill: highly actionable behavioral guidance, explicit ordered workflows with entry gates and fallback routing, and a genuine one-level-deep reference structure with a navigable case index. Weaknesses are a body that could be tightened (repeated caveats and long meta-sections) and a dangling FIDELITY.md reference plus one unreferenced bundle file.

Suggestions

Tighten the 「怎么用我」 rules and the 局限/申报 sections: the 'not in this material' disclaimer rules are spelled out multiple times and several nested caveats could be collapsed into single statements.

Fix the dangling `FIDELITY.md` reference: either add the file or point the citation at its actual location, references/research/validation-2026-11-09/.

Either reference references/demo-conversation-2026-04-05.md from the body (e.g., as a usage example) or remove it from the bundle.

DimensionReasoningScore

Conciseness

The body is dense with material Claude does not already know (sourced case facts, verified quotes, boundary tables) rather than padded explanations of known concepts, but the ~245-line body could be tightened: the 「怎么用我」 rules carry nested caveats, the 'not in this material' disclaimers are stated in multiple places, and the 局限/申报 meta-sections are lengthy. This fits 'mostly efficient but could be tightened' — not 2 (no padding of known concepts), not 4 (several sections have redundant caveat repetition).

3 / 5

Actionability

As an instruction-only skill the guidance is fully concrete: a 6-step review procedure with an explicit output contract (一句话判断 up front, three-column plans specified down to 「改哪一屏、哪个元素、改成什么」, top-3 actions, per-column percentage deductions), 招式 entries each with 什么时候/我会做/例子, and a 21-case index mapped to situation types. This matches 'specific examples cover the common cases'.

5 / 5

Workflow Clarity

Sequences are explicit and ordered (「按这个顺序走。评审时不要跳步」) with gating checkpoints (「没看到之前只问问题」, case-lookup fallback routing in rule 3, exit/recovery commands in rule 1). It falls short of 5 because there are no explicit feedback/error-recovery loops and some checkpoints (e.g., when to stop asking for materials) remain implicit.

4 / 5

Progressive Disclosure

Good structure: the body is an overview, a case-index table routes to the one-level-deep references/casebook.md, voice samples route to references/voice.md, and research底稿 live in references/research/ — all real files. Not 5 because the cited `FIDELITY.md` does not exist in the bundle (a dead navigation link; the validation material actually lives under references/research/validation-2026-11-09/), and references/demo-conversation-2026-04-05.md is present but never referenced.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description: it states concrete capability areas, gives four explicit natural-language trigger phrases, adds a negative trigger to prevent misfiring, and occupies a clearly distinct niche. The only gap is missing common trigger variations such as 「扮演乔布斯」 or English phrasings.

DimensionReasoningScore

Specificity

Names the domain (乔布斯的视角) and three concrete capability areas — 「产品判断与评审、取舍决策、对人对事的直接反馈」— which meets 'several specific actions; minor gaps'. It is not 5 because the actions are broad categories rather than a comprehensive list of concrete behaviors, and not 3 because more than two specific actions are stated.

4 / 5

Completeness

Explicitly answers both what (「产品判断与评审、取舍决策、对人对事的直接反馈」) and when (「说…时使用」 with four concrete trigger phrases, plus a when-not clause 「不在一般性问题上自动触发」), matching the top anchor of concrete trigger phrases for both.

5 / 5

Trigger Term Quality

Four natural quoted trigger phrases (「用乔布斯的视角」「乔布斯会怎么看」「切换到乔布斯」「让乔布斯评一下」) plus an explicit non-trigger clause give good coverage a user would actually say. It falls short of 5 because common variations such as 「扮演乔布斯」 and English-language triggers (e.g. 'as Steve Jobs') are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Jobs-perspective persona) with distinct, quoted triggers and an explicit anti-misfire clause (「不在一般性问题上自动触发」), so overlap with other skills is minimal.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alchaincyf/nuwa-skill

Path

examples/steve-jobs-perspective/SKILL.md

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.