CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

collect-github-stats

Collect GitHub repo health/usage stats into merged JSON.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/collect-github-stats/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, single-script skill: the body gives an exact executable command with defaults, prerequisites, and a well-flagged destructive-risk warning (never overwrite the 14-day-rolling-window traffic history), and correctly delegates all logic to the bundled script. Weak points are the wordy self-improvement boilerplate and a soft rather than explicit post-run verification step.

DimensionReasoningScore

Conciseness

The body is lean — a one-line summary, an exact command, defaults, and terse MoSCoW rules with no explanations of concepts Claude already knows. Minor trimmable noise remains: the "Lessons learned" header's meta-instructions ("keep updating, first line is template, keep template, follow '<instructions>', high confidence only") are wordy, and the all-caps emphasis repeats the same warning twice. Not 5 because of these few tokens that don't fully earn their place.

4 / 5

Actionability

"python3 <skill_dir>/scripts/collect_stats.py [--repo OWNER/NAME] [--out PATH] [--no-enrich]" is a copy-paste-ready command with defaults ("--repo griddynamics/rosetta", "--out docs/github-stats.json"), working-directory requirement, flag semantics, prerequisites (gh authed with repo scope and push access), and the error path (script fails loud with fix steps). The referenced script exists at scripts/collect_stats.py. This covers the common case fully.

5 / 5

Workflow Clarity

For this single-action skill the instruction is unambiguous (run one script with documented args), and validation is addressed: the script preflights gh auth/push access, "FAILS LOUD with fix steps", and "MUST NOT accept a partial file" guards the append-merge. However, post-run verification of the output is only soft ("SHOULD relay the script's post-run summary") rather than an explicit check that the merged history gained today's entry, so it sits at 'clear sequence with most checkpoints; minor validation gaps' rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with a single bundle file (scripts/collect_stats.py, verified to exist) that is the only thing referenced; per the rubric's simple-skill guidance, well-organized sections alone warrant a 5. Sections (Run, CRITICAL, Rules, Lessons learned) are clearly labeled and nothing that belongs in a separate file is inlined.

5 / 5

Total

18

/

20

Passed

Description

53%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 states a clear, concrete capability but is a single clause with no trigger guidance and no enumeration of the stats collected. It answers 'what' adequately and 'when' not at all, and its keyword coverage is minimal beyond 'GitHub' and 'stats'.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for GitHub repo stats, traffic, clones, views, or repository health metrics."

Name the specific metrics collected (traffic/views/clones, forks, stars, contributors) so the scope is concrete and searchable.

Mention the append-merge history behavior (14-day rolling traffic window) in the description to distinguish it from one-off stat lookups.

DimensionReasoningScore

Specificity

"Collect GitHub repo health/usage stats into merged JSON" names the domain (GitHub repo health/usage stats) and 1-2 concrete actions (collect stats, merge into JSON), but never specifies which metrics (traffic, views, clones, forks) are collected. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is not 4 because it does not list several specific actions.

3 / 5

Completeness

The 'what' is clear (collect repo health/usage stats and merge them into a JSON history), but there is no 'Use when...' clause or any trigger guidance, which per the rubric caps completeness at 3. Not 4 because 'when' is entirely absent rather than just imprecise.

3 / 5

Trigger Term Quality

Relevant keywords like "GitHub", "repo", "stats", "health", "usage" are present, but common natural variations users would say — "GitHub traffic", "repo stars/clones", "repository statistics" — are missing. Fits 'Some relevant keywords but missing common variations or synonyms'; not 4 because keyword coverage is thin rather than 'good with a few missing'.

3 / 5

Distinctiveness Conflict Risk

"Collect GitHub repo health/usage stats into merged JSON" carves a fairly clear niche (GitHub repository stats collection with a merged JSON history) with minor overlap risk against other GitHub-related skills. Not 5 because without trigger phrases, a request like "get repo stats" could plausibly match other GitHub skills.

4 / 5

Total

13

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

griddynamics/rosetta

Path

.claude/skills/collect-github-stats/SKILL.md

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.