Deep Skill Finder – Real Tests Real Reviews find skills that Real Work
C-Rank Grade: A (Welcoming) - 71/100
External PR Merge Rate: 95%
Response Time: <1h
First Timer Success: 100%
wheelry/deep-skill-finder has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in wheelry/deep-skill-finder 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 71.2 places wheelry/deep-skill-finder in the A tier.
The external contributor pull request merge rate for wheelry/deep-skill-finder is 95.2%, based on public PR activity from non-core contributors.
wheelry/deep-skill-finder currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in wheelry/deep-skill-finder. Reviews community pull requests with focus on project quality.
Discussions in wheelry/deep-skill-finder focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/wheelry/deep-skill-finder?utm_source=github&utm_medium=badge)
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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~0 hours (43% approval). Keep your diff compact for rapid review.
Hi! I found a Skill named [skill-name] on the website and copied the provided installation prompt into my Agent. However, the Agent could not find the exact Skill. It ran a semantic search instead and returned several similar recommendations. This makes me wonder whether: The website index and installation API are temporarily out of sync. The Skill was renamed or removed. The generated installation prompt contains an outdated slug. It would be helpful if the Skill page could verify availability before displaying the installation prompt, or show a clear message when a Skill is no longer installable.
Could deep-skill-finder provide a preview step before installing a recommended Skill?The preview could show:Files that will be installedCommands or scripts included in the packageExternal services the Skill may contactRequired environment variablesInstallation directoryPotential security warningsA --dry-run option would also help Agents inspect the package and explain the expected changes before asking the user for confirmation.
Hi! I came across jin-tian-chi-shen-me while using deep-skill-finder to search for skills on the website. I copied the prompt provided by the website and gave it to my Agent, but the Agent responded that it couldn't find or install a skill with that name, and it returned five similar skills instead. This made me a little confused about whether jin-tian-chi-shen-me is still available or whether the installation command might be out of sync with the current skill list. I'm not sure if this is expected behavior or a small issue with the skill index/installation flow, so I wanted to share it here in case it's helpful. Thanks for building this! I’ve been enjoying using deep-skill-finder to discover skills, and I’d be happy to provide more details if needed.
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 wheelry/deep-skill-finder, 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 wheelry/deep-skill-finder acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.2% were successfully merged into the primary branch.
wheelry/deep-skill-finder has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 71.2 places wheelry/deep-skill-finder in the Welcoming tier.
The external pull request merge rate is 95.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, wheelry/deep-skill-finder currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for wheelry/deep-skill-finder 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.