CtrlK
BlogDocsLog inGet started
Tessl Logo

github-trending

抓取 GitHub 上 star 涨得最快的项目(Trending 榜),打分标注是否与研究方向相关, 生成 Obsidian 笔记到 GitHubTrending 文件夹。默认周榜。 触发词:"GitHub 周榜"、"star 涨得最快"、"过去一周 GitHub 热门"、"GitHub trending"、 "看看这周 GitHub 上火了什么"、"GitHub 日榜"、"GitHub 月榜"

75

Quality

94%

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

92%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 lean, script-driven workflow skill: executable commands for every phase, explicit output validation with error-recovery paths for rate limits and network failure, and sound boundary guidance (example engine names are not a whitelist; pushed_at only proves code updates). The only blemish is minor redundancy between the overview and the 注意事项 section.

DimensionReasoningScore

Conciseness

Efficient overall — bullet-style operational facts (SSL fallback, rate-limit partial-status handling, no-git policy) that Claude cannot infer, with no concept-explaining padding. Not 5 because of minor repetition: '脚本本身不调用大模型' appears both in the overview (line 19) and again in 注意事项 (line 90).

4 / 5

Actionability

Fully executable guidance: copy-paste bash commands with exact flags and {TEMP_DIR} placeholders for all three phases, a comment showing the --language variant, an explicit phrase→--since mapping ('周榜'→weekly, '日榜'→daily, '月榜'→monthly), and stated stdout contract (script prints final note path).

5 / 5

Workflow Clarity

Clear phased sequence (config → parse period → fetch/score → discovery → note → report) with explicit validation and feedback loops: '确认 {TEMP_DIR}/github_trending.json 是非空 JSON 数组。为空则看 stderr 诊断', partial-status preservation on API failure ('不要把空结果写成“没有新增项目”'), and network/SSL fallback handling.

5 / 5

Progressive Disclosure

A single well-sectioned SKILL.md serving as the overview; implementation detail is delegated to the three scripts, shared conventions live one level deep and are clearly signaled ('[Agent 运行约定](../_shared/agent-runtime.md)'). Nothing that belongs in a separate reference file is inlined; navigation is trivial at this size.

5 / 5

Total

19

/

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 strong description: concrete multi-action capability statement, explicit and natural trigger-word coverage in both Chinese and English, and a clearly bounded niche. The only gap is that the new-project discovery phase (GitHub Repository Search) is not mentioned in the description.

DimensionReasoningScore

Specificity

Lists several concrete actions — '抓取 GitHub 上 star 涨得最快的项目(Trending 榜)', '打分标注是否与研究方向相关', '生成 Obsidian 笔记到 GitHubTrending 文件夹' — with a concrete output location and default period. Not 5 because the project-discovery/search capability (Phase 1b of the body) is omitted from the description; not 3 because it goes well beyond naming 1-2 actions.

4 / 5

Completeness

Explicitly answers both 'what' (fetch trending repos, score research relevance, write Obsidian notes to a named folder, default weekly) and 'when' (a dedicated 触发词 trigger list with concrete phrases). Matches the anchor-5 example structure of capability list plus explicit trigger clause.

5 / 5

Trigger Term Quality

The 触发词 clause gives comprehensive natural user phrasings with synonyms and variants across both languages: 'GitHub 周榜', 'star 涨得最快', '过去一周 GitHub 热门', 'GitHub trending', '看看这周 GitHub 上火了什么', 'GitHub 日榜', 'GitHub 月榜'. These are exactly what a user would say, covering daily/weekly/monthly variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche: GitHub Trending ingestion scored against a research profile and written as Obsidian notes. Triggers ('GitHub 周榜', 'GitHub trending', 'star 涨得最快') are distinct and unlikely to fire for a different skill; only negligible overlap with a sibling daily-papers note pipeline.

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
huangkiki/dailypaper-skills
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.