Plain-language agent skills for Claude Code, Codex, Cursor and Gemini CLI: honest session reports, straight verdicts, steps you can follow. MIT.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 65%
Response Time: 2h
First Timer Success: 67%
kharmanskyi/open-steps has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kharmanskyi/open-steps respond to incoming external pull requests in approximately 2.2 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 64.0 places kharmanskyi/open-steps in the A tier.
The external contributor pull request merge rate for kharmanskyi/open-steps is 65.0%, based on public PR activity from non-core contributors.
kharmanskyi/open-steps does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Collaborative maintainer environment in kharmanskyi/open-steps. Reviews community pull requests with focus on project quality.
Discussions in kharmanskyi/open-steps 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/kharmanskyi/open-steps?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~10 hours (29% approval). Keep your diff compact for rapid review.
Part of #4, which says why: the pack documents installing on Cursor, and every published number was measured on Claude Code. The seam is in: run.sh asks, one script per tool answers, and evals/README.md, "Measuring another agent", is the contract such a script keeps. This issue is one runner. What to build One executable file, evals/agents/cursor.sh, that turns one Cursor CLI print-mode run (agent -p in docs/other-agents.md) into the stream the scorer reads. It is called as cursor.sh ARM MODEL PROMPT inside a throwaway git repository; evals/agents/claude.sh next to it is the reference. The pack must be installed the way docs/other-agents.md describes (the skills in ~/.agents/skills/, the routing block in AGENTS.md at the project root, which your runner writes into the throwaway repository), because what is measured is whether the installed pack switches on by itself. The one judgment in the file The scorer counts one Skill line for every time the agent opened one of the pack's skills.
Part of #4, which says why: the pack documents installing on Codex, and every published number was measured on Claude Code. The seam is in: run.sh asks, one script per tool answers, and evals/README.md, "Measuring another agent", is the contract such a script keeps. This issue is one runner. What to build One executable file, evals/agents/codex.sh, that turns one Codex CLI headless run (codex exec) into the stream the scorer reads. It is called as codex.sh ARM MODEL PROMPT inside a throwaway git repository; evals/agents/claude.sh next to it is the reference. The pack must be installed the way docs/other-agents.md describes (the skills in ~/.agents/skills/, the routing block in ~/.codex/AGENTS.md), because what is measured is whether the installed pack switches on by itself. The one judgment in the file The scorer counts one Skill line for every time the agent opened one of the pack's skills. Say in the runner's header what that is on Codex, most likely a read of the skill's SKILL.md, s
Part of #4, which says why: the pack documents installing on Gemini CLI, and every published number was measured on Claude Code. The seam is in: run.sh asks, one script per tool answers, and evals/README.md, "Measuring another agent", is the contract such a script keeps. This issue is one runner. What to build One executable file, evals/agents/gemini-cli.sh, that turns one Gemini CLI headless run into the stream the scorer reads. It is called as gemini-cli.sh ARM MODEL PROMPT inside a throwaway git repository; evals/agents/claude.sh next to it is the reference. The pack must be installed the way docs/other-agents.md describes (the skills in ~/.agents/skills/, the routing block in ~/.gemini/GEMINI.md), because what is measured is whether the installed pack switches on by itself. The one judgment in the file The scorer counts one Skill line for every time the agent opened one of the pack's skills. Say in the runner's header what that is on Gemini CLI, the call that activates a skill or a
Same gap as the Cursor one, different contract, so it is a separate piece of work and a separate pull request. What docs/other-agents.md already establishes, read from Gemini CLI's own documentation and not yet run by anyone: The session-start side is hookSpecificOutput.additionalContext on SessionStart. The stop side is AfterAgent with decision: "deny" and a reason, not the obvious SessionEnd, which is best effort and ignores flow control completely. Getting that wrong is the failure that looks like success: the hook runs, nothing blocks, no report is ever asked for, and no error appears. Scope An adapter that speaks Gemini CLI's contract, sharing the hook bodies rather than copying them. A case in hooks/test.sh for the Gemini-shaped payload and output. docs/other-agents.md updated, keeping its run-versus-read labelling honest. Done when The suite passes on Linux and macOS. The pull request shows what was actually run. A payload fed by hand is worth something and is not the same
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 kharmanskyi/open-steps, 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 kharmanskyi/open-steps acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.0% were successfully merged into the primary branch.
kharmanskyi/open-steps has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. 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 64.0 places kharmanskyi/open-steps in the Welcoming tier.
The external pull request merge rate is 65.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
kharmanskyi/open-steps does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for kharmanskyi/open-steps 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.