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.

7available profiles
Filter optionsRole, protocol, trust, setup, and sorting stay available here.
First queue itemfeedforward-learning-local skill by plurigrid/asiReview trust and setup, then run a small code review trial.Review preflight
Setup coverage7 guided / 0 manualAcross 7 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 · playbooks / Coding & Development
Fit
55 / 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.

This skill enables forward-forward local learning by applying layer-wise contrastive updates without backprop, improving autonomous feature discrimination.

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 · skillsdirectory / Coding & Development
Fit
59 / 100
Trust
Verified source
Setup
MCP ready
Before run
0 checks
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Plan-then-execute implementation against SPEC.md. Native single-thread loop, no sub-agents. On test or build failure, auto-invokes the backprop skill before retrying — a failed verification always considers whether a new §V invariant would prevent recurrence. Triggers when the user asks to build, implement, execute the spec, or tackle a specific §T task (`b...

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
  • Clear 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 · skillsdirectory / Coding & Development
Fit
50 / 100
Trust
Verified source
Setup
MCP ready
Before run
0 checks
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Trace runtime bugs back to spec gaps — identify missing acceptance criteria, update specs, generate regression tests, and detect patterns

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
  • Clear 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.

#4 trial priority · playbooks / Coding & Development
Fit
55 / 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.

This skill enables gradient-free optimization using discrete perturbations and trits to train non-differentiable functions and ternary networks.

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.

#5 trial priority · skillsdirectory / Coding & Development
Fit
59 / 100
Trust
Verified source
Setup
MCP ready
Before run
0 checks
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

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
  • Clear 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.

#6 trial priority · skillsdirectory / Coding & Development
Fit
59 / 100
Trust
Verified source
Setup
MCP ready
Before run
0 checks
Top risk

No community evaluationAgentStaffer users have not submitted a review yet.

Full readiness snapshotCandidate summary and risk context stay available here.

Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3",...

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
  • Clear 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.

Show 1 more trial candidatesAdditional candidates stay folded for scanning; trials.json and card resource links keep the full review path.
#7 trial priority · deepnlpagents / Coding & Development
Fit
33 / 100
Trust
Needs review
Setup
Source guide
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.

Source code of "How to Correctly do Semantic Backpropagation on Language-based Agentic Systems" 🤖

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.
  • License review: License metadata is missing from the current public profile.
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.