Task resolver
Use when the agent has a task and needs the best executor.
GET /dob-task-resolver/?task=browser%20automationTask in. Executor out.
Agents should call a resolver, not browse a homepage. DayOneBuilder returns the best source URL, install or call path, verification step, and fallback for the task.
Sourceprimary repo stays visible
Actionone install, call, or open step
Proofsmoke test or fallback required
Agent entrypoints
Install or call the resolver.
The homepage is only a doorway. The useful surface is the API-shaped resolver, repo report, action feed, and installable skill an agent can invoke during work.
GitHub repo report
Use when the agent already has a repo and needs source-of-truth signals.
GET /repo/?repo=owner/nameInstallable skill
Use inside an agent runtime to make resolver lookup a default step.
https://dayonebuilder.online/skills/dayonebuilder-resolver/SKILL.mdAction feed
Machine-readable task aliases, first actions, smoke tests, and fallbacks.
GET /agent-actions.jsonResolver API contract
Callable service shape with a dependency-free Python reference implementation.
GET /api/recommend?task={task}Local service
Run this in the repo to give a coding agent a real endpoint.
python3 services/dob_resolver_api.py --site site --port 8787MCP adapter contract
Tool shape for agents that call MCP instead of reading static feeds.
dob_recommend_executor(task)
How DayOneBuilder earns routes
By making the next action obvious.
The resolver should feel useful before it asks anyone to believe it. A good recommendation is a card, badge, command, URL, and verification step.
Best executor
The resolver should choose the best external source for the task, not the best DayOneBuilder-owned page.
Repo URL in
A GitHub URL opens a report page with public GitHub data and agent-usefulness checks.
API first
Agents should call URLs and JSON feeds directly instead of reading marketing copy.
Skill packaging
The skill makes this resolver a reusable agent habit: check source, action path, smoke test, fallback.
Telemetry loop
The resolver watches task submissions, repo reports, outbound source clicks, install snippet copies, and repeat agent routes.
Agent Magnet badge
Show the public agent footprint.
Agent Mention Index counts public GitHub code-search hits for exact repo mentions inside agent-facing files. It is a visible proxy for agent routing, not private GitHub traffic.
README embed
Use a badge only when it links to query evidence for that repository.
[](https://dayonebuilder.online/agent-magnet/upstash-context7/)