CtrlK
BlogDocsLog inGet started
Tessl Logo

db-foundation-course

编写"数据库筑基课"文章的专用 Skill,面向数据库架构师、DBA 和业务开发者。输入一个筑基课文章标题及相关参考资料(技术文档、产品手册、开源项目地址、deepwiki、论文等),输出图文并茂、结构完整的 Markdown 筑基课文章,保存至项目 markdown/ 目录。适用主题覆盖:表存储结构(heap/parquet/arrow/zedstore/LSM-Tree/HStore等)、索引结构(btree/gin/brin/hnsw/ivfflat/bloom等)、数据类型与操作符(vector/jsonb/tsvector/range/array等)、优化器扫描算法(seq scan/index scan/bitmap scan/join/agg/并行等)、场景化实践(时序/GIS/RAG/全文检索/图数据/数据湖等)以及事务/锁/并发/安全等周边主题。只要用户提及"筑基课"、"数据库原理"、"数据库内核"写作,或给出了数据库存储/索引/扫描相关的技术文档让你写成教程,都应使用此 Skill。

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/skills_for_claude_web/db-foundation-course/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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-organized, highly actionable skill body: explicit workflow, a required article template, executable SQL/diagram examples, and a pre-save self-check checklist. Its main weaknesses are token efficiency (duplicated illustrative sections could be trimmed) and the complete absence of progressive disclosure — the entire topic catalog, sample excerpt, and per-category guidance are inlined rather than split into reference files.

Suggestions

Move the 主题速查表 (§八) and 示例输出片段 (§十) into a references/ file (e.g. references/topics.md and references/sample-heap.md) and link them with one-line pointers, converting the body into a lean overview.

Trim §三's per-category sub-bullets to one representative category inline and point the rest to the reference file; the current detail level duplicates what the topic catalog already signals.

Add an explicit feedback loop to the 自检 step: 'if any checklist item fails, fix and re-run the checklist before saving', mirroring the validate→fix→retry pattern the rubric rewards for workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly prescriptive rather than explanatory of known concepts, but it includes tightening opportunities: the 40-line 示例输出片段 (§十) partially duplicates §三 and §四 guidance, and the 主题速查表 (§八) plus detailed per-topic sub-bullets in §三 run long for a context file. It is above the 2 anchor ('several unnecessary explanations or padded sections') because nearly all content is directive rather than padded explanation, but below 4 because whole sections could be trimmed or split out without losing clarity.

3 / 5

Actionability

Concrete, executable guidance throughout: runnable SQL with pageinspect ('SELECT * FROM heap_page_items(get_raw_page(''tbl_demo'', 0))'), ready-to-use mermaid and text-diagram templates, concrete file-naming examples ('markdown/20240919_heap-storage.md'), and an explicit 12-section article template. It misses a 5 due to minor gaps: the '所属系列: [数据库筑基课大纲](链接)' placeholder is not a resolvable link, and §九's 'web_fetch' step lacks concrete parameters/handling for failures.

4 / 5

Workflow Clarity

A clear 5-step sequence (读取参考资料 → 提纲 → 逐节撰写 → 自检 → 输出) plus an explicit pre-output validation checklist (§六 '输出前必须核对' with 9 checkbox items) and a closing reminder to re-run the checklist. It falls short of the 5 anchor because there is no explicit error-recovery loop (what to do when a 自检 item fails — fix and re-check — is only implied by '逐项检查'), leaving a minor validation gap at the 4 anchor.

4 / 5

Progressive Disclosure

This is a single-file skill with no references/, scripts/, or assets/ bundle at all — everything (a 316-line body, a ~20-line topic catalog table, a ~40-line sample article excerpt, per-category deep-dive guidance) is inlined in SKILL.md. Section headers are clear and navigation is possible, so it is above the 2 anchor, but content that clearly belongs in separate reference files (the 主题速查表 and 示例输出片段, plus per-topic sub-guides) is inlined, matching the anchor-3 pattern of structure present but separable content kept inline.

3 / 5

Total

14

/

20

Passed

Description

82%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 that explicitly defines inputs, outputs, save location, and topic coverage, with an explicit 'use when' trigger clause and distinctive domain vocabulary. Its main weaknesses are the second-person phrase '让你写成教程' (which incurs the rubric's specificity penalty) and a long padded enumeration of technologies that inflates length without adding proportional trigger value.

Suggestions

Rewrite the second-person phrase '让你写成教程' in third person (e.g. '将...技术文档改写为教程时') to avoid the voice penalty and tighten specificity.

Trim the long parenthetical enumeration of technologies (heap/parquet/arrow/zedstore/LSM-Tree/HStore 等) to representative examples plus a category summary; the full catalog already lives in the body's 主题速查表.

DimensionReasoningScore

Specificity

The description names concrete actions ("输入一个筑基课文章标题及相关参考资料...输出图文并茂、结构完整的 Markdown 筑基课文章,保存至项目 markdown/ 目录") and comprehensively enumerates covered topics, which would rate a 4. However, the second-person phrasing "让你写成教程" ("lets you write it into a tutorial") triggers the rubric's mandatory 1-point penalty on specificity, bringing it to 3. It is above the 2 anchor because the domain and multiple concrete input/output actions are explicitly stated.

3 / 5

Completeness

Both 'what' and 'when' are explicitly answered with concrete trigger phrases: what — "输入一个筑基课文章标题及相关参考资料...输出图文并茂、结构完整的 Markdown 筑基课文章,保存至项目 markdown/ 目录"; when — "只要用户提及'筑基课'...都应使用此 Skill". This matches the anchor-5 example structure (what + explicit 'use when' clause) exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases are explicitly provided: "只要用户提及'筑基课'、'数据库原理'、'数据库内核'写作,或给出了数据库存储/索引/扫描相关的技术文档让你写成教程,都应使用此 Skill" — these are phrases a user would plausibly say. It stops short of a 5 because some natural variations (e.g. '写一篇数据库教程'、'内核原理文章'、'存储引擎') are not enumerated, but it clearly exceeds the generic keyword level of a 3.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (数据库筑基课 technical article writing) with distinctive triggers ('筑基课', '数据库内核', storage/index/scan technical docs to be turned into tutorials). Conflicts with adjacent skills (general writing, general database Q&A) are unlikely because the trigger vocabulary is domain-specific and unusual; this matches the anchor-5 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

17

/

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

relative_links

Relative link issues: 1 missing

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.