CtrlK
BlogDocsLog inGet started
Tessl Logo

andres-freund-perspective

PostgreSQL 核心 committer Andres Freund 的思维框架与表达方式。基于 6 个调研维度(著作、对话、表达 DNA、他者视角、决策、时间线) 共 2957 行 / 200 KB 一手资料的深度调研,提炼 6 个核心心智模型、10 条决策启发式和完整的表达 DNA。 用途:作为思维顾问,用 Andres Freund 的视角分析 PG 性能/扩展性/AIO/构建现代化等"测量驱动+地基重写"场景, 与 Tom Lane Skill 形成对比视角(一个偏"标准+历史",一个偏"现代工程+测量")。 当用户提到「用 Andres 的视角」「andres 会怎么看」「Andres Freund 模式」「AIO 推动」「Meson 切换」「测量驱动」 「I think / I'm unconvinced」「Greetings, Andres Freund」「PG 性能决策」「地基重写」时使用。 即使用户只是说「帮我用 PG 性能导向 committer 的角度想想」「如果 Andres 会怎么做」 「切换到测量驱动模式」「和 Tom Lane 观点对比」也应触发。 **排除触发(不要激活)**: - 通用 SQL 学习/教学咨询("怎么写 JOIN"、"学 SQL 有什么建议") - PostgreSQL 运维/部署问题(Patroni、pgpool、备份恢复) - 仅提及 Andres Freund 名字作为信息引用("Andres 写了 X commit"作为事实陈述) - 与 PG 性能/现代化基础设施无关的纯 catalog/SQL 语法问题(这是 Tom Lane 的强项,不是本 Skill 的) - **Andres 的个人生活、性格、家庭、地理、私人关系**(公开材料完全无覆盖;用 Tom Lane Skill 也无帮助——应直接拒绝)

70

Quality

86%

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

77%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 an unusually rigorous persona skill: a well-sequenced agentic workflow with speculation gating, anti-fabrication red lines, hard/soft self-checks, and highly concrete templates throughout. Its weaknesses are redundancy (duplicated tables, repeated Tom Lane contrasts, heuristics overlapping 表达 DNA) and poor use of the existing research bundle — the six reference files are barely pointed to while their content is partially duplicated inline.

Suggestions

Deduplicate: keep the certainty-gradient table, high-frequency phrase list, and Tom Lane contrast in one place each — Step 3 and 表达 DNA currently repeat the gradient table, and heuristics 6-8 restate 表达 DNA content.

Move the 人物时间线 table and per-model evidence lists into references/research/ (06-timeline.md and 01-writings.md already cover them), keeping only 2-3 anchor examples inline.

Replace the single end-of-file reference mention with a per-topic pointer list (e.g. '详细对话样本: references/research/02-conversations.md;表达 DNA 完整版: references/research/03-expression-dna.md') so the six research files are actually discoverable.

DimensionReasoningScore

Conciseness

Mostly dense, genuinely novel persona data (mental models, expression DNA, escalation rules) that Claude cannot know otherwise, but there is real tightening to do: the certainty-gradient table appears twice (Step 3C and 表达 DNA), heuristics 6/7/8 duplicate the 表达 DNA section, the Tom Lane contrast is repeated across ~8 sections, and the 人物时间线 table duplicates references/research/06-timeline.md. This sits between anchor 2 ('several unnecessary... padded sections') and anchor 4 ('efficient; minor over-explanation') — roughly a quarter of the ~712 lines is redundant, which is more than 'minor' but the bulk still earns its place.

3 / 5

Actionability

Fully executable guidance for an instruction-only skill: verbatim sentence templates ('What gains have you measured in somewhat realistic workloads?'), exact tool directives (mcp__MiniMax__web_search, WebFetch failure handling for anarazel.de), a copy-paste authenticity-challenge response template, and concrete soft/hard self-check rules (B1-B4) with exact remediation phrasing. The guidance is copy-paste ready and covers common cases, matching anchor 5.

5 / 5

Workflow Clarity

The agentic protocol is clearly sequenced (Step 0 speculation gate → Step 1 question-classification table → Step 2 typed research tracks A-E → Step 3 anchored response) with explicit validation checkpoints and feedback loops: anti-fabrication red lines, pre-output self-check with fix-before-output, hard blockers forcing rewrite/degradation, and a numbered escape-hatch with recovery and re-entry rules. This matches anchor 5's 'clear sequence with explicit validation steps; feedback loops; checklists'.

5 / 5

Progressive Disclosure

The bundle is real and one level deep (references/research/01-06, 2957 lines), but SKILL.md signals it only once — '调研过程详见 references/research/ 目录' at the very end — with no per-file pointers, while large blocks that mirror those files (人物时间线, mental-model evidence, heuristics) are inlined in the body. This matches anchor 3 ('references present but not clearly signaled; content that should be separate is inline') rather than 4, because the inlining is substantial and the navigation to the six well-named research files is essentially absent.

3 / 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 explicitly covers what the skill does, when to trigger it (with both literal and paraphrased trigger phrases), and when NOT to trigger it, and it carves out a clean niche against the companion Tom Lane skill. The only weakness is research-provenance metadata (line counts, byte counts, dimension inventory) that pads the text without adding capability information.

DimensionReasoningScore

Specificity

The description lists several concrete actions — '作为思维顾问,用 Andres Freund 的视角分析 PG 性能/扩展性/AIO/构建现代化...场景', '提炼 6 个核心心智模型、10 条决策启发式和完整的表达 DNA', '与 Tom Lane Skill 形成对比视角' — with minor gaps in coverage. It is not a 5 because a noticeable portion is research provenance padding ('基于 6 个调研维度...共 2957 行 / 200 KB 一手资料的深度调研') that describes the build process rather than capabilities, and verbose text is explicitly not rewarded.

4 / 5

Completeness

Both 'what' (思维框架与表达方式;6 个心智模型、10 条决策启发式、表达 DNA;用作思维顾问分析 PG 性能/现代化场景) and 'when' ('当用户提到...时使用' plus an explicit even-if paraphrase list and exclusion triggers) are clearly and explicitly answered with concrete trigger phrases, matching the anchor-5 example structure. It is not below 5 because neither half is missing or weakly implied.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including direct phrases ('用 Andres 的视角', 'andres 会怎么看', 'AIO 推动', 'Meson 切换', '测量驱动', 'Greetings, Andres Freund') and paraphrase-level variants ('如果 Andres 会怎么做', '切换到测量驱动模式', '和 Tom Lane 观点对比'). Anchor 5's 'comprehensive coverage of natural terms including synonyms' is matched; the direct phrases and their looser paraphrases are both covered.

5 / 5

Distinctiveness Conflict Risk

A clear niche (Andres Freund persona for PG performance/modernization decisions) with distinct triggers, an explicit boundary against the sibling Tom Lane skill ('这是 Tom Lane 的强项,不是本 Skill 的'), and a dedicated 排除触发 list preventing misfires on generic SQL/ops questions. This matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

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

skill_md_line_count

SKILL.md is long (734 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
digoal/blog
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.