CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

digoal-perspective

digoal/德哥的思维框架与表达方式。基于本地 digoal/blog 长文、ASK/访谈、 技术课程、公开履历、社区活动页和近年 AI skill 行动记录的调研, 提炼5个核心心智模型、8条决策启发式和表达DNA。 Use when the user explicitly asks for 德哥/digoal perspective, judgment, advice, analysis, or expression style, including requests such as 「用德哥的视角」「digoal会怎么看」「按德哥的思路拆一下」 「德哥会怎么写」「用德哥风格改写」「digoal perspective」 or 「切换到德哥」. Apply it to database practice, technical communication, open-source ecosystems, AI skillization, product opportunities, career learning, and cross-domain judgment.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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-structured persona skill: the operating rules, workflow, routing, and style guidance are concrete and non-derivable, and research material is properly offloaded to clearly labeled reference files. The main gaps are minor — some trimming opportunities, implicit rather than explicit validation gates, and slight duplication between inline model evidence and the research files.

Suggestions

Trim persona-color sections (智识谱系, 身份卡's overlapping biography with 06-timeline.md) and move the per-model 证据 bullets into the research files, keeping only one-line citations inline to cut body tokens.

Make the workflow's evidence-gap handling an explicit checkpoint: define what happens when a Step 2 fact cannot be verified (e.g., label the claim as assumption, state the missing evidence layer, and offer the minimal verification path) rather than leaving it as prose inside the Step 2 preamble.

Tighten Step 2 by replacing the four free-form research checklists with a shorter, scenario-keyed lookup so the persona can apply them without re-reading several nested bullet groups.

DimensionReasoningScore

Conciseness

The body is dense with persona-specific knowledge Claude cannot derive (mental models backed by dated article citations, expression DNA, decision heuristics) and avoids explaining generic concepts, but sections like 智识谱系 and parts of 身份卡 are decorative and could be trimmed.

4 / 5

Actionability

Gives concrete, executable persona instructions — a verbatim one-time disclaimer, first-person voice rules, a question-classification table, a copy-paste short-answer template (「诊断 -> 一个机制或检查点 -> 下一步或边界」), and a scenario routing table — though Step 2 research guidance remains high-level rather than prescriptive.

4 / 5

Workflow Clarity

The 3-step workflow (问题分类 -> 德哥式研究 -> 德哥式回答) is clearly sequenced with explicit routing conditions (纯框架问题默认直接进入 Step 3) and fallback paths for missing evidence; some validation checkpoints (e.g., 诚实边界's research-date caveat) are implicit rather than explicit gates.

4 / 5

Progressive Disclosure

The 按需加载研究材料 section clearly signals one-level-deep references (references/research/01-writings.md through 06-timeline.md, all verified to exist) with explicit load conditions; however, the per-model 证据 bullets inline in the body partially duplicate the research files, so the split is good but not optimal.

4 / 5

Total

16

/

20

Passed

Description

95%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 what the skill contains, when to use it, and captures an unusually rich set of natural user trigger phrases in both languages. Its only weakness is the opening research-provenance detail, which adds length without adding actionability.

DimensionReasoningScore

Specificity

Lists several concrete deliverables (「提炼5个核心心智模型、8条决策启发式和表达DNA」) and named application domains (database practice, technical communication, open-source ecosystems, AI skillization, product opportunities, career learning, cross-domain judgment), but the leading research-provenance clause (「基于本地 digoal/blog 长文、ASK/访谈、技术课程、公开履历、社区活动页和近年 AI skill 行动记录的调研」) pads the action statement rather than sharpening it.

4 / 5

Completeness

Explicitly answers both what (「digoal/德哥的思维框架与表达方式...提炼5个核心心智模型、8条决策启发式和表达DNA」) and when (「Use when the user explicitly asks for 德哥/digoal perspective...」) with concrete trigger phrases — matching the top completeness anchor.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural trigger phrases a user would actually say, in both Chinese and English: 「用德哥的视角」「digoal会怎么看」「按德哥的思路拆一下」「德哥会怎么写」「用德哥风格改写」「digoal perspective」「切换到德哥」, plus synonyms like judgment, advice, analysis, expression style.

5 / 5

Distinctiveness Conflict Risk

The trigger requires the user to explicitly name 德哥/digoal, carving a clear niche (persona/perspective emulation) with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 6 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

digoal/blog

Path

skills/digoal-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.