Provider-agnostic operations for agentic resources. ARK codifies patterns and practices developed across dozens of agentic application projects.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 76%
Response Time: -
First Timer Success: 81%
mckinsey/agents-at-scale-ark has a recorded first-timer success rate of 81.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mckinsey/agents-at-scale-ark 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 66.5 places mckinsey/agents-at-scale-ark in the A tier.
The external contributor pull request merge rate for mckinsey/agents-at-scale-ark is 75.9%, based on public PR activity from non-core contributors.
mckinsey/agents-at-scale-ark currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Provider-agnostic operations for agentic resources. ARK codifies patterns and practices developed across dozens of agentic application projects.
Collaborative maintainer environment in mckinsey/agents-at-scale-ark. Reviews community pull requests with focus on project quality.
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/mckinsey/agents-at-scale-ark?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (95% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
exected a wrap around with an expand button
unlike top level items that keep highlighted as long as I'm on the screen - the agents, teams and all monitoring items are highlighted here is a highlighted top level nav item Happens on both, dark and white mode.
Currently, this button does nothing when there are no Ark agents instsalled. It should either be hidden or disabled.
Problem The ark install command does not support passing custom Helm values during installation. Users who want to configure executor credentials or customize Helm chart values must perform a two-step process: Install with defaults using ark install Manually run helm upgrade with --set flags to configure values This creates poor UX and forces users to learn both Ark CLI and Helm syntax. Impact Who is affected: Users installing marketplace executors who need credential injection via extraEnvFrom Users wanting to customize Helm chart values during installation (storage size, resources, replicas, etc.) Proposed Solution Add support for passing Helm values directly to ark install: # Using --set flag ark install marketplace/executors/executor-claude-agent-sdk \ --set 'extraEnvFrom[0].secretRef.name=github-credentials' # Using --values flag ark install marketplace/executors/executor-claude-agent-sdk \ --values my-values.yaml This enables single-command installation with custom confi
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 mckinsey/agents-at-scale-ark, 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 mckinsey/agents-at-scale-ark acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.9% were successfully merged into the primary branch.
mckinsey/agents-at-scale-ark has a recorded first-timer success rate of 81.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 66.5 places mckinsey/agents-at-scale-ark in the Welcoming tier.
The external pull request merge rate is 75.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mckinsey/agents-at-scale-ark 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 mckinsey/agents-at-scale-ark 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.