Collect GitHub repo health/usage stats into merged JSON.
76%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/collect-github-stats/SKILL.mdRuns one script: fetch GitHub stats for a repo, merge into docs/github-stats.json.
python3 <skill_dir>/scripts/collect_stats.py [--repo OWNER/NAME] [--out PATH] [--no-enrich]Defaults: --repo griddynamics/rosetta, --out docs/github-stats.json. MUST run from
repo root (or pass absolute --out). --no-enrich skips company/location lookups.
docs/github-stats.json. Script APPEND-MERGES. Traffic is
a 14-DAY ROLLING WINDOW — deleted history is GONE FOREVER, unrecoverable from the API.gh authenticated, repo scope, push access to the target repo.If you learned something new which is reusable, there are process efficiency improvements, you can prevent failures in the future, update ## Lessons learned below for self-improvement.
critical_notes. Fixed: prior unknown keys now carried forward.griddynamics/rosetta
ca35acf
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.