Community Registry — Verified Public

Discover Amplifier
Bundles & Agents

Browse, rate, and share bundles ranked by community usage and LLM-verified quality. Swept from 19 team members and beyond.

Bundles
Contributors
Total Stars
Verified public
Loading…
How Ratings Work
Transparent, community-sourced quality signals
19

Team Members Swept

Public GitHub repos are swept nightly for new bundles, changes, and usage signals. Only repos with public visibility are listed. Results update automatically.

AI

LLM-as-Judge Ratings

An automated pipeline evaluates each bundle on documentation quality, capability breadth, prompt design, and observable output quality. Runs on every update and bi-weekly for unchanged bundles.

Community Signals

Users self-report which bundles they use. Mentions in GitHub Discussions, Teams, and Slack are picked up by the sweep. Every report increments the weekly user count.

Built something with Amplifier?

Share your bundle with the community. We'll run an LLM quality check, seed usage tracking, and add it to the registry. Open-source and team-private bundles both welcome.

GitHub Discussions
About

Quality Breakdown
LLM Verdict
AI Quality Assessment

Install
Tags
Repository
View on GitHub
Quality Rubric — v1.0

Every bundle is scored on five dimensions — two from the GitHub API (objective), three from an LLM reading the public README (consistent). Same rubric, every time. Scores are recomputed nightly.

1 — Documentation LLM-judged
4Clear purpose, audience, install, usage example, AND tradeoffs or when-not-to-use.
3Clear purpose, install, at least one usage example. No major gaps.
2Purpose clear, install present, but no examples or audience is unclear.
1README exists but sparse, vague, or mostly template boilerplate.
0No README, empty, or gives no useful information.
2 — Bundle / Agent Design LLM-judged
4Proper Amplifier structure, rich context files, clear agent description, follows delegation philosophy, obvious care in prompt design.
3Proper structure, meaningful context files, install and type declaration make sense.
2Recognizable Amplifier bundle, install present, context files thin.
1Minimal structure, install declared, little or no context or guidance.
0Cannot be identified as a proper Amplifier bundle.
3 — Activity & Maintenance GitHub API
4Last commit ≤ 30 days AND at least one of: issues closed, release tag, merged PR in past 90 days.
3Last commit ≤ 60 days, or ≤ 90 days with some issue or PR activity.
2Last commit ≤ 180 days.
1Last commit between 6 and 12 months ago.
0No commits in over 12 months, or repository appears abandoned.
4 — Code / Prompt Quality LLM-judged
4Clear expertise: well-structured prompts with reasoning guidance, handles edge cases, no quick-fix patterns.
3Solid, minor weaknesses. Prompts coherent and purposeful.
2Functional but shallow. Prompts generic or could apply to many tools unchanged.
1Minimal — little design thought visible in prompts or code.
0No meaningful implementation. Placeholder or entirely boilerplate.
5 — Trust Signals GitHub API
4LICENSE + CI/CD workflow files + tests or CHANGELOG.
3LICENSE + CI/CD. No tests or CHANGELOG.
2LICENSE only. README has clear structure.
1LICENSE only. README unstructured.
0No LICENSE file.
Score → Stars
18 – 20 pts★★★★★ 5.0
15 – 17 pts★★★★½ 4.5
12 – 14 pts★★★★ 4.0
9 – 11 pts★★★½ 3.5
6 – 8 pts★★★ 3.0
3 – 5 pts★★ 2.0
0 – 2 pts★ 1.0

Rubric v1.0 · View full rubric on GitHub · To dispute a score, open an issue with label score-dispute