AD github-trend-analyzer
分析GitHub趋势榜和热门榜,提供技术趋势总结和创新项目介绍。 当用户询问GitHub趋势、热门项目、技术发展趋势、"今天有什么热门"、 "GitHub trending"、"github热门"、"开源趋势"、"技术风向"等话题时, 必须使用此skill获取GitHub官方Trending页面的数据,进行分析总结。 此skill适用于: - 想了解当前GitHub上什么项目最火 - 关注技术发展趋势和新兴技术 - 寻找有创新性的开源项目 - 了解开源社区的技术风向变化 - 对比不同时间段的趋势变化
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (github-trend-analyzer) differs from the folder (tech-trending-on-github)
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 461 tokens
- 100Running it twice. No mutating operations
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 252: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.