CtrlK
BlogDocsLog inGet started
Tessl Logo

db-ai-github-paper-weekly-news

抓取并汇总"数据库、AI、GitHub、AI 论文"近 1 周新闻,输出图文并茂(含 mermaid 图)的 markdown 周报到当前项目的 markdown/ 目录。覆盖 10 个数据源:postgresweekly.com/issues(自动解析最新 issue 编号)、planet.postgresql.org、planet.postgis.net、postgresql.org/about/newsarchive/、git.postgresql.org shortlog、duckdb.org/news/、aibase.com/zh、ai-bot.cn/daily-ai-news、github.com/trending?since=weekly、huggingface.co/papers/trending。适用于:用户提出"生成周报"、"本周数据库+AI+GitHub+论文快讯"、"跑一次 db-ai-weekly"、"weekly news"等需求。

72

Quality

89%

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

78%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 a well-organized, mostly lean workflow spec with concrete tooling, a clear 7-step sequence, per-source error classification, and real reference files appropriately externalized. It could be tightened by deduplicating the status enum and surfacing a small inline runnable snippet.

Suggestions

Deduplicate the status enum (ok/empty/error/human_required): define it once and reference it from both Step 3 and Step 6 to trim tokens.

Add a short inline runnable example (e.g., a one-liner invoking scripts/crawl.py) so the body has copy-paste-ready guidance without forcing a file hop.

Make the failure→retry loop explicit for transient errors (5xx/429/timeout): note a retry count or backoff before finalizing status="error", strengthening the verification checkpoint.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explaining what markdown/mermaid/RSS is), but the status enum (ok/empty/error/human_required) is restated in both Step 3 and Step 6, a minor redundancy that could be tightened.

4 / 5

Actionability

Concrete guidance throughout — exact URLs, the mcp__MiniMax__web_search/WebFetch tool names, file naming convention (db-ai-weekly-YYYY-MM-DD.md), and a structured JSON item schema — but it relies on referenced scripts for executable code rather than showing inline runnable examples.

4 / 5

Workflow Clarity

Seven steps are clearly sequenced (parse dynamic URL → parallel crawl → failure handling → classify → mermaid → coverage table → write file) with per-source status verification and a human_required fallback; missing an explicit validate→fix→retry loop keeps it just below the top anchor.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references to real bundle files (references/output-template.md, references/human-verification.md, and four scripts/*.py — all verified to exist), content appropriately split, and easy navigation via the 资源 section and inline pointers.

5 / 5

Total

17

/

20

Passed

Description

100%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.

The description is excellent: it concisely states concrete capabilities, names all data sources, and gives explicit natural-language trigger phrases for when to invoke the skill. It uses appropriate third-person voice and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '抓取并汇总', '输出图文并茂(含 mermaid 图)的 markdown 周报', '自动解析最新 issue 编号' — plus enumerates 10 named data sources, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (crawl/aggregate 10 sources into a mermaid markdown weekly report under markdown/) and 'when' ('适用于:用户提出...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides natural user phrases including synonyms and the exact skill name — '生成周报', '本周数据库+AI+GitHub+论文快讯', '跑一次 db-ai-weekly', 'weekly news' — covering the ways a user would naturally request this.

5 / 5

Distinctiveness Conflict Risk

Highly specific niche (DB+AI+GitHub+Paper weekly news from 10 named sources) with distinct triggers and a unique skill name, giving minimal conflict risk with other skills.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.