CtrlK
BlogDocsLog inGet started
Tessl Logo

db-ai-github-paper-weekly-news

抓取并分析"数据库、AI、GitHub、AI论文"相关的近1周内最新内容,分类汇总,输出图文并茂(含内置 Mermaid 图)的 Markdown 周报到当前项目的 markdown/ 目录。 覆盖数据源:PostgreSQL Weekly、Planet PostgreSQL、Planet PostGIS、PostgreSQL 官方新闻、PostgreSQL Git 提交记录、DuckDB 新闻、AI每日资讯(aibase.com、ai-bot.cn)、GitHub Trending(周榜)、HuggingFace 热门论文。 触发条件:用户提到"数据库周报"、"AI周报"、"GitHub 周报"、"AI 论文周报"、"db weekly"、"抓取本周数据库新闻"、"抓取本周AI动态"、"生成技术周报"、"帮我整理本周的数据库/AI/Github/论文动态"、"weekly news"、"weekly report"、"周刊",或用户希望获取 DB/AI/GitHub/Paper 领域近期综合资讯时,必须使用本 skill。即使用户只说"帮我看看这周有什么技术大事"或"PostgreSQL 最近有什么新闻",也应使用本 skill。

68

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

70%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 delivers a well-sequenced, highly actionable workflow with genuine error-recovery feedback loops and a validation checklist — workflow clarity is excellent. Its weaknesses are verbosity (a duplicated example section and placeholder skeletons) and zero progressive disclosure: everything, including a 155-line output template, is inlined in one file with no reference files.

Suggestions

Move the Step 5 output template and the 示例输出片段 examples into a references/report-template.md file and reference it from SKILL.md, keeping the main file as a lean overview of the workflow.

Delete or shrink section 五 (示例输出片段) since it duplicates template sections A and E already specified in Step 5, keeping only one compact worked example.

Tighten the placeholder Mermaid skeletons in Step 4 (e.g., "主题A --> 主题B") to one short annotated example each, since the accompanying prose already describes what each chart must contain.

DimensionReasoningScore

Conciseness

The body is mostly tight procedural content (source table, per-source strategies, exception handling) with no padding of concepts Claude already knows, but "## 五、示例输出片段" largely re-demonstrates sections already covered by the ~155-line Step 5 template, and placeholder Mermaid skeletons ("主题A --> 主题B") add length without adding guidance.

3 / 5

Actionability

Concrete throughout: exact source URLs, specific fallback search queries ("web_search(\"site:postgresweekly.com issues 2025\")"), a runnable date command, a fixed output filename pattern, and a per-scenario exception table. It falls short of fully copy-paste ready because the per-source fetch steps are written as pseudocode-style step blocks rather than executable commands.

4 / 5

Workflow Clarity

Steps 0–7 are strictly sequenced ("## 二、执行流程(严格按顺序)"), Step 6 provides explicit feedback loops for error recovery (403/429 → web_search fallback, Cloudflare 拦截, 空内容 → 标注不强行填充, 日期无法解析 → 缓冲), and "## 三、质量自检清单" is a concrete pre-output validation checklist.

5 / 5

Progressive Disclosure

The skill is a single ~480-line monolithic SKILL.md with no references/, scripts/, or assets/ bundle at all. Section headers give it reasonable navigability, but the long output template and example fragments clearly belong in a separate reference file rather than inline.

3 / 5

Total

15

/

20

Passed

Description

96%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 concrete capabilities, comprehensively lists data sources, and provides an explicit and richly exemplified trigger clause in both Chinese and English. The only weakness is a handful of overly generic trigger phrases (e.g., "weekly report") that slightly raise conflict risk with unrelated reporting tasks.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("抓取并分析…分类汇总,输出图文并茂(含内置 Mermaid 图)的 Markdown 周报到当前项目的 markdown/ 目录") and comprehensively names all 10 data sources (PostgreSQL Weekly through HuggingFace 热门论文), including a specific output directory and format.

5 / 5

Completeness

It explicitly answers both "what" (fetch, analyze, categorize, and output a Mermaid-illustrated Markdown weekly report to markdown/) and "when" via a dedicated 触发条件 clause with concrete trigger phrases and example user utterances.

5 / 5

Trigger Term Quality

Trigger terms are extensive and natural in both Chinese and English ("数据库周报", "AI周报", "db weekly", "weekly news", "weekly report", "周刊"), and even include casual phrasings a user would actually say ("帮我看看这周有什么技术大事", "PostgreSQL 最近有什么新闻").

5 / 5

Distinctiveness Conflict Risk

The DB × AI × GitHub × Paper weekly-report niche is clearly distinct with domain-specific triggers, but broad generic phrases like "weekly report" and "帮我看看这周有什么技术大事" create minor overlap risk with general summary/reporting skills.

4 / 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

relative_links

Relative link issues: 4 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.