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。

69

Quality

85%

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 highly actionable, well-structured writing-guide skill with concrete templates, executable SQL, a clear stepped workflow, and a self-check checklist. Its main weaknesses are mild redundancy that hurts conciseness and an implicit rather than explicit validate→fix→retry loop in the workflow.

Suggestions

Remove the duplicated block-layout text diagram — keep it in only one place (either §4.2 or the §10 sample) to tighten the body and improve conciseness.

Make the self-check feedback loop explicit in §6, e.g. 'If any item fails, fix the issue and re-run the checklist before saving' to lift workflow clarity toward 5.

Consider moving the §8 topic quick-reference table and/or the §10 sample output into separate reference files so SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly directive and efficient and does not explain concepts Claude already knows, but it carries redundancy — the block-layout text diagram appears in both §4.2 and the §10 sample, and the §8 topic quick-reference table re-treads topic coverage already enumerated in the description — that could be tightened.

3 / 5

Actionability

Guidance is fully concrete and copy-paste-ready: an executable SQL example, an exact 12-section template, per-section quantitative specs ('至少 5 条,Q&A 格式', '列出 TOP 5 调优手段'), exact file-naming patterns, and a full sample output excerpt covering the common case.

5 / 5

Workflow Clarity

A clear 5-step sequence is given with an explicit validation checkpoint (Step 4 自检) and a detailed 9-item self-check checklist (§6), but the error-recovery feedback loop (if a check fails → fix → re-validate) is only implied rather than spelled out, leaving it just below a 5.

4 / 5

Progressive Disclosure

The body is well-organized into clearly numbered sections (§一–§十) with content that is appropriately inline for a writing guide rather than an API reference, and no bundle files exist; the minor gap is that the §8 topic table and §10 sample could optionally be split into reference files to keep the ~310-line core leaner.

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 highly specific, well-constructed description that explicitly states what it does, where output is saved, and exactly when to invoke it, with natural trigger synonyms and a distinctive niche. Its only limitation is that the capability is essentially a single deliverable (write one structured article) rather than multiple distinct actions.

DimensionReasoningScore

Specificity

Concrete input→output→persist actions are stated ('输入一个筑基课文章标题及相关参考资料…输出图文并茂、结构完整的 Markdown 筑基课文章,保存至项目 markdown/ 目录') with comprehensive topic enumeration, but it describes one core deliverable action rather than multiple distinct actions, so it sits below a clean 5.

4 / 5

Completeness

It clearly answers 'what' (produces an illustrated, structured Markdown foundation-course article saved to markdown/) and 'when' (an explicit 'Use when…' equivalent clause with concrete triggers), matching the anchor for explicit what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Explicit natural trigger phrases users would say are enumerated with synonyms ('只要用户提及“筑基课”、“数据库原理”、“数据库内核”写作,或给出了数据库存储/索引/扫描相关的技术文档让你写成教程,都应使用此 Skill'), giving comprehensive coverage; file extensions are not applicable to this topic-driven skill.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — database-internals foundation-course tutorial writing — anchored by the distinctive brand term '筑基课' and domain-specific storage/index/scan triggers, keeping conflict risk with other skills 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.

Validation15 / 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.