📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 48%
Response Time: -
First Timer Success: 60%
runkids/skillshare has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in runkids/skillshare respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 62.8 places runkids/skillshare in the A tier.
The external contributor pull request merge rate for runkids/skillshare is 48.4%, based on public PR activity from non-core contributors.
runkids/skillshare currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in runkids/skillshare. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/runkids/skillshare?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (61% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
The gap skillshare ships Windows binaries but never runs its test suite on Windows. .goreleaser.yaml cross-builds windows for amd64 and arm64 and ships them as zip archives, so Windows is a supported release target. Seven files compile only on Windows and no job ever builds them: cmd/skillshare/{console,ui_process,upgrade}_windows.go, internal/childproc/childproc_windows.go, internal/mcp/check_live_windows.go, internal/sync/symlink_windows.go, internal/utils/link_windows.go. test.yaml runs unit + integration tests on ubuntu-latest and macos-latest only. A Windows-only regression therefore reaches users through release binaries with no signal in CI. What a windows-latest job reports today I added the job to my fork and ran it against upstream 7043ca3a: https://github.com/star-nebula/skillshare/actions/runs/37088491097 14 of the 32 packages the unit-test pattern selects fail (15 pass, 3 carry no test files): cmd/skillshare, internal/{audit,config,devcontainer,git,hooks,install,mcp,opl
uv is a Python project and package manager that integrates well with tools. It would be great if I could install skillshare using uv tool, or invoke it using uvx. This would become possible if skillshare's prebuilt binaries were on PyPI. Can skillshare publish binaries to PyPI?
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to runkids/skillshare, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of runkids/skillshare acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.4% were successfully merged into the primary branch.
runkids/skillshare has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 62.8 places runkids/skillshare in the Welcoming tier.
The external pull request merge rate is 48.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, runkids/skillshare currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for runkids/skillshare are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.