Free-first agent task resolver

Stop scanning skill directories by hand.

Give this page a coding or automation task and it returns the best matched skill catalog, official skill pack, or resolver module, with source links, trust notes, install steps, and a test path.

The current seed focuses on five recurring jobs: best agent skill selection, skill safety checks, MCP server finding, skill pack management, and the DayOneBuilder resolver lane itself.

Ranked picks Shows why a source wins instead of dumping another giant list.

Trust visible Source, license, fit, and uncertainty stay on the card.

No login Basic use works in the browser with local seed data only.

How ranking works

1. Match the task to a narrow job, not a vague category. 2. Prefer official or curated sources with visible install paths. 3. Penalize license gaps, weak verification, or "install varies" hand-waving.

What this MVP does not hide

If a repo is source-available instead of open source, or if a directory only points you to community listings, the card says so plainly.

Resolver output

Ranked recommendations

Each result includes a trust score, why it won, where it comes from, how to install or call it, how to test it, and a copyable agent instruction.

Pick an example or type a task to render the first ranked shortlist.

Seed coverage

Five seeded resolver jobs

The page ships with a small local dataset so it works offline and loads instantly. The next step is expanding coverage without turning this into another noisy catalog.

Best agent skill

For agents that need one good starting point instead of another hour of repo browsing.

Skill safety checker

For checking whether a third-party skill looks well-formed, reviewable, and sane before install.

MCP server finder

For locating the best source when the agent needs a server or skill around an external integration job.

Skill pack manager

For choosing the cleanest install flow when you need curated or official bundles, not ad hoc folders.

Selection guide

What the cards optimize for

Better routing beats bigger lists. If a directory is broad but a smaller official repo is safer and faster for the exact task, the official repo should win.

Objective signals

Official ownership or strong curation history

Clear install, call, or test path

Visible license notes and known limits

Task fit for coding or automation work

Need a team shortlist?

Basic resolver use stays free. If your team wants a tighter shortlist, support mapping, or a managed internal resolver lane, use the lightweight interest path below.

Ask about team support Read the registry JSON