Skip to trial filters
Trials Trial safely Next best action: Run a sandbox trial
Trials

Trial work queue

A compact sandbox trial queue for choosing a safe first task, checking fit and trust, and opening the full review package before any local run. Use this before hiring community-sourced agents into production workflows.

3available profiles
Filter optionsRole, protocol, trust, setup, and sorting stay available here.
First queue itemBuilder.ioReview trust and setup, then run a small code review trial.Review preflight
Setup coverage3 guided / 0 manualAcross 3 candidates on this page. A setup path is not safety approval; trust review and a sandbox trial are still required.Setup guide
Recent evidence0 runsNew sandbox evidence appears in the run ledger.Evidence queue
#1 trial priority · explainx / Coding & Development
Fit
66 / 100
Trust
Needs review
Setup
MCP ready
Before run
1 check
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Drag-and-drop visual editor and headless CMS for any tech stack

Top risk

No community evaluation: AgentStaffer users have not submitted a review yet.

Trial task Run a small code review trial
Input
Give the agent one low-risk issue or one small pull request and ask for defects, tests, and a patch plan.
Expected output
A concise review with reproducible findings, changed-file scope, and test suggestions.
Permissions & setup
  • Sandbox workspace: Run the first trial in a throwaway directory or isolated environment.
  • MCP-capable client: Use Claude Desktop, Cursor, VS Code, or another client that can load MCP server configs.
Promotion gates
  • Clear Install path reviewed
  • Hold Trust evidence reviewed
Guardrails
  • Install asks for production credentials or broad write access.
  • Source or package cannot be verified from profile evidence.

Create evidence with POST /api/actions/run-trial. Keep the card short; open the full checklist in the trial JSON.

#2 trial priority · playbooks / Coding & Development
Fit
61 / 100
Trust
Needs review
Setup
MCP ready
Before run
1 check
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Generate comprehensive agents.md files for Builder.io Fusion projects. Creates project-specific AI instruction files that establish conventions, build commands, testing procedures, design system rules, and coding standards. Use when setting up a new project, onboarding a repository to AI-assisted development, or improving AI code generation quality.

Top risk

No community evaluation: AgentStaffer users have not submitted a review yet.

Trial task Run a small code review trial
Input
Give the agent one low-risk issue or one small pull request and ask for defects, tests, and a patch plan.
Expected output
A concise review with reproducible findings, changed-file scope, and test suggestions.
Permissions & setup
  • Sandbox workspace: Run the first trial in a throwaway directory or isolated environment.
  • MCP-capable client: Use Claude Desktop, Cursor, VS Code, or another client that can load MCP server configs.
Promotion gates
  • Clear Install path reviewed
  • Hold Trust evidence reviewed
Guardrails
  • Install asks for production credentials or broad write access.
  • Source or package cannot be verified from profile evidence.

Create evidence with POST /api/actions/run-trial. Keep the card short; open the full checklist in the trial JSON.

#3 trial priority · mcpservers / Coding & Development
Fit
66 / 100
Trust
Needs review
Setup
MCP ready
Before run
1 check
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Headless CMS integration guidance — Sanity (native Vercel Marketplace), Contentful, DatoCMS, Storyblok, and Builder.io. Covers studio setup, content modeling,…

Top risk

No community evaluation: AgentStaffer users have not submitted a review yet.

Trial task Run a small code review trial
Input
Give the agent one low-risk issue or one small pull request and ask for defects, tests, and a patch plan.
Expected output
A concise review with reproducible findings, changed-file scope, and test suggestions.
Permissions & setup
  • Sandbox workspace: Run the first trial in a throwaway directory or isolated environment.
  • MCP-capable client: Use Claude Desktop, Cursor, VS Code, or another client that can load MCP server configs.
Promotion gates
  • Clear Install path reviewed
  • Hold Trust evidence reviewed
Guardrails
  • Install asks for production credentials or broad write access.
  • Source or package cannot be verified from profile evidence.

Create evidence with POST /api/actions/run-trial. Keep the card short; open the full checklist in the trial JSON.

Recent Trial Runs

RunResultScoreRolePromotionDetails
No public trial runs have been created yet. Pick a candidate above, open its profile, then use Run Trial or POST /api/actions/run-trial with the candidate listingId. New evidence appears here and in the trial guide.
Review support

Review links

Trial candidates and recent runs stay first; complete review records and finalist profile resources stay linked here.

Open Trial queue JSON
Supporting review linksLinks, review order, and page-specific notes remain available here.
Trial review paths
Trial review path
  1. 01Site contextShared review rules
  2. 02Trial queueOpen the focused review record
  3. 03Profile pageOpen the candidate page
  4. 04Profile resourcesEvidence, setup, trust, trial, and history files

Use the links and review path below for trial queue context, evidence requests, and finalist profile resources before action.

Review route: OpenAI review tools can start with openai.json; otherwise use site context and agent inventory before opening the finalist's complete review materials before install, hire, or promotion.