CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tom-lane-perspective

PostgreSQL 核心 committer Tom Lane 的思维框架与表达方式。基于 6 个调研维度(著作、对话、表达 DNA、他者视角、决策、时间线) 共 2421 行 / 160 KB 一手资料的深度调研,提炼 6 个核心心智模型、10 条决策启发式和完整的表达 DNA。 用途:作为思维顾问,用 Tom Lane 的视角分析开源项目治理问题、审视 patch 评审、调试 PostgreSQL 相关决策、 处理"维护者 vs 运动员"张力等场景。 当用户提到「用 Tom Lane 的视角」「tgl 会怎么看」「Tom Lane 模式」「regards, tom lane」「I object, I'll rewrite」 「Tom Lane 风格评审」「patch 评审」「commitfest」「维护者 vs 运动员」「It's hard to argue that」「Let's just」 「undo thinko」「以 PG committer 身份」「core team 视角」时使用。即使用户只是说「帮我用 PG 核心 committer 的角度想想」 「如果 Tom Lane 会怎么做」「切换到 PostgreSQL 治理模式」「PG 什么时候支持 X」「tgl 会怎么 review」也应触发。 **排除触发(不要激活)**: - 通用 SQL 学习/教学咨询("怎么写 JOIN"、"学 SQL 有什么建议") - PostgreSQL 运维/部署问题(Patroni、pgpool、备份恢复) - 仅提及 Tom Lane 名字作为信息引用("Tom Lane 写了 X commit"作为事实陈述) - 与开源治理/PG 内部决策无关的纯技术问答

66

Quality

83%

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

66%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 excels at behavioral precision: a gated workflow, anti-fabrication red lines, self-audits, and escape hatches make this persona skill unusually rigorous and directly executable. It is held back by heavy internal duplication — the certainty ladder, signature rules, and key evidence each appear 2-4 times across models, heuristics, and DNA sections — and by an essentially un-navigated 160 KB reference bundle while reference-appropriate content stays inlined in the main file.

Suggestions

Deduplicate systematically: keep the certainty-gradient table and signature/frequency rules in the 表达 DNA section only and have Step 3 reference them; merge 启发式 2/3/4/7 into the corresponding 心智模型 sections (模型 3/2/6/4) since they restate the same evidence and phrases.

Split reference-like material out of SKILL.md into one-level-deep files — e.g. references/timeline.md (人物时间线 + 最新动态) and references/sources.md (附录:调研来源) — keeping the operative role-play rules, workflow, and models in the main file.

Add per-file navigation for the existing research bundle: instead of a bare directory pointer, map each file to its purpose (e.g. '表达 DNA 细节见 references/research/03-expression-dna.md') so the 160 KB of research is discoverable rather than buried.

DimensionReasoningScore

Conciseness

The ~640-line body contains systematic duplication: the 5-level certainty gradient table appears twice (Step 3C and 表达 DNA), the synchronous_commit ALL-CAPS example is cited in 模型 2, 4, 6 and 启发式 4, and 启发式 2/3/4/7 largely restate 模型 3/2/6/4; the 人物时间线 and 最新动态 sections also overlap on 2026 events. This goes beyond 'could be tightened' — several whole sections are padded restatements, matching the 'noticeably verbose' anchor rather than the level-3 anchor.

2 / 5

Actionability

For an instruction-only skill the guidance is fully concrete and copy-paste ready: exact openers ("I have to admit I don't have a clear position on this"), a sentence-skeleton catalog (起手/转折/拍板/结尾), named search targets (git.postgresql.org, message-id archives), anchor requirements (commit hash, bug #, message-id), and template phrases. This matches the 'fully executable, specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

The Step 0 speculation gate → Step 1 classification table → Step 2 research protocol (per question type) → Step 3 output recipe is clearly sequenced, with explicit validation checkpoints (anti-fabrication red lines, post-generation certainty-gradient audit, a 5-item self-check command) and genuine feedback loops (escape-hatch rules for fabricated hashes, style slips, and out-of-scope topics with recovery actions). This matches the top anchor: clear sequence, explicit validation, error-recovery loops, and a checklist.

5 / 5

Progressive Disclosure

The bundle contains references/research/ with six large raw files, but the body signals them only once ("调研过程详见 references/research/ 目录") with no per-file navigation or indication of which file covers what. Meanwhile large reference-like content — the full timeline table, 智识谱系, and the sources appendix — is inlined in SKILL.md rather than split out. This matches the anchor 'content that clearly belongs in separate files is inlined; references are buried', and is above level 1 only because the structure is real and the references are one level deep.

2 / 5

Total

14

/

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.

An exceptionally well-constructed description: explicit what/when, comprehensive natural trigger phrases with synonyms and signature quotes, and an unusual but effective negative-trigger section that reduces mis-activation risk. The only flaw is research-meta padding about corpus size that adds length without adding user-relevant capability information.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "分析开源项目治理问题、审视 patch 评审、调试 PostgreSQL 相关决策、处理『维护者 vs 运动员』张力" — plus concrete deliverables ("6 个核心心智模型、10 条决策启发式和完整的表达 DNA"). It falls short of a 5 because research-provenance padding ("基于 6 个调研维度…共 2421 行 / 160 KB 一手资料的深度调研") inflates the text without adding capability information.

4 / 5

Completeness

Both questions are answered explicitly: what ("作为思维顾问…提炼 6 个核心心智模型、10 条决策启发式和完整的表达 DNA") and when ("当用户提到…时使用" with a long list of concrete trigger phrases, plus an explicit exclusion list). This mirrors the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural, spanning synonyms and signature phrases users would actually say: "用 Tom Lane 的视角", "tgl 会怎么看", "regards, tom lane", "I object, I'll rewrite", "commitfest", "以 PG committer 身份", "core team 视角", plus implicit-trigger variants ("如果 Tom Lane 会怎么做"). This matches the anchor's comprehensive coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous — simulating a specific PostgreSQL committer's reasoning on governance/patch review — with highly distinctive triggers (tgl, commitfest, 'I object, I'll rewrite'). The explicit 排除触发 section (generic SQL learning, ops/deployment, name-as-citation) actively mitigates the few generic trigger terms like "patch 评审", keeping conflict risk minimal.

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 (658 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

digoal/blog

Path

skills/tom-lane-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.