Skip to trial filters
~/agentstafferAgentStaffer

Find, trial, compare, and govern AI agents before hiring

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.

25available profiles
Filter optionsRole, protocol, trust, setup, and sorting stay available here.
First queue itemSkillReview trust and setup, then run a small code review trial.Review preflight
Setup coverage12 guided / 0 manualAcross 12 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 · remoteopenclaw / 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.

Browse imported skills from the public skills ecosystem on Remote OpenClaw.

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#2 trial priority · enterprisedna / 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.

Julius is a community-developed tool for building and running autonomous AI agents. It provides a chat-based interface to define agent behaviors and execute tasks. The tool is designed for users who want to experiment with agentic workflows.

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#3 trial priority · explainx / 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.

Your AI Data Analyst

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#4 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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#5 trial priority · mcpservers / Coding & Development
Fit
67 / 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.

Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers wh...

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#6 trial priority · mcpservers / 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.

Decision guide for delegating to caveman-style subagents. Tells the main thread WHEN to spawn `cavecrew-investigator` (locate code), `cavecrew-builder` (1-2 file edit), or `cavecrew-reviewer` (diff review) instead of doing the work inline or using vanilla `Explore`. Subagent output is caveman-compressed so the tool-result injected back into main context is...

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
Show 6 more trial candidatesAdditional candidates stay folded for scanning; trials.json and card resource links keep the full review path.
#7 trial priority · mcpservers / 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.

Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman-compress FILEPATH or "compress memory file"

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#8 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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#9 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.

Read-only drift detector. Diffs SPEC.md against current code and reports violations grouped by severity. Writes nothing — suggests remedies via the spec or build skills but never invokes them. Triggers when the user asks to check drift, audit the spec, verify invariants, or ask whether code still matches the spec. Phrasings: "check drift", "audit the spec",...

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#10 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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#11 trial priority · mcpservers / 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.

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust JSON
#12 trial priority · mcpservers / 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.

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

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.

Review & run trial Open profile
Review links
Profile JSON Trial JSON Setup JSON Trust 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 queue JSONEvidence requests JSONPromotion queue JSONGEO exposure JSONAgent visibility JSONResource catalog JSONSite context TXTSitemap XMLProfile package JSON
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.