builderz-labs/mission-control - Open Source PR Review Scorecard

Self-hosted control plane for AI agents: dispatch tasks, review runs, track spend, and operate OpenClaw, Claude Code, Codex, and other runtimes.

C-Rank Grade: A (Welcoming) - 56/100

External PR Merge Rate: 50%

Response Time: 16h

First Timer Success: 50%

Frequently Asked Questions

Is builderz-labs/mission-control welcoming to first-time open-source contributors?

builderz-labs/mission-control has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in builderz-labs/mission-control respond to incoming external pull requests in approximately 16.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 55.7 C-Rank™ score (A Tier) represent?

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 55.7 places builderz-labs/mission-control in the A tier.

What is the external contributor pull request merge rate for builderz-labs/mission-control?

The external contributor pull request merge rate for builderz-labs/mission-control is 50.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in builderz-labs/mission-control?

builderz-labs/mission-control currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

builderz-labs
builderz-labs/mission-controlA•Welcoming6.2k
GitHub
Back to Explorer
builderz-labs

builderz-labs/mission-control

6,232
InactiveA•Welcoming(56/100)Low Sample (<20 PRs)TypeScript

Self-hosted control plane for AI agents: dispatch tasks, review runs, track spend, and operate OpenClaw, Claude Code, Codex, and other runtimes.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in builderz-labs/mission-control welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
16 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
50.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
50.0%
Merge Gauge
50.0%
1st-Timer
Community Vibe53/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for builderz-labs/mission-control
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/builderz-labs/mission-control)](https://getmerged.abhishekco.de/builderz-labs/mission-control?utm_source=github&utm_medium=badge)

Active Good First Issues (1)

View on GitHub

Problem Statement Mission Control supports multiple agent runtimes, including OpenClaw, Hermes Agent, Claude Code, Codex CLI, and OpenCode. However, the Skills Hub still appears to use an OpenClaw / legacy skill-root inventory model rather than the active runtime's canonical skills inventory. In a Hermes-backed deployment, this makes the Skills Hub look incomplete or misleading. For example, on one local install: hermes skills list reports 85 enabled skills Mission Control's Skills Hub reports 6 skills The 6 skills shown are accurate for the roots Mission Control currently scans, but they do not represent Hermes Agent's actual skill inventory. Current Skills Hub roots appear to be: ~/.agents/skills ~/.codex/skills project .agents/skills project .codex/skills ~/.openclaw/skills ~/.openclaw/workspace/skills dynamic ~/.openclaw/workspace-<agent>/skills Hermes Agent's skill model includes additional concepts that are not covered by scanning those directories: builtin skills hub-instal

📅 Opened Jul 12, 2026💬 3 comments
Quality: 55/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for builderz-labs/mission-control

When evaluating whether to contribute to builderz-labs/mission-control, 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 builderz-labs/mission-control acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to builderz-labs/mission-control

01

Is builderz-labs/mission-control welcoming to first-time open-source contributors?

builderz-labs/mission-control has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~16 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 55.7 C-Rank™ score represent?

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 55.7 places builderz-labs/mission-control in the Welcoming tier.

04

What is the external contributor pull request merge rate for builderz-labs/mission-control?

The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in builderz-labs/mission-control?

Yes, builderz-labs/mission-control currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for builderz-labs/mission-control 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.