Build a reusable skill, MCP connector or end-to-end automation in DevRev Computer that solves an enterprise problem using the provided Enterprise-Bench dataset, and demonstrate a useful, evidence-backed outcome that another authorized teammate can repeat.
One challenge. Three build paths. Enterprise-Bench data only.
Enterprise teams repeat the same investigations, handoffs and data checks. Turn one of those jobs into a capability that a colleague can run with their own inputs, inspect the evidence and use again.
Package a repeatable workflow in Computer: when to use it, what inputs it needs, which tools to use and how to produce a useful result.
For example, review a customer's documented commitments and prepare an evidence-backed handoff for another teammate.
Connect Computer to an external tool or sandbox service. MCP, or Model Context Protocol, is a standard way to expose tools an AI application can call.
Your connection should enable a completed workflow, such as turning an approved commitment into a tracked sandbox task. A connection alone is not the outcome.
Pick a use case, such as debugging incidents, and automate it end to end using agents, workflows, MCP and DevRev data objects.
Combine the building blocks into a working flow from intake to a useful, recorded outcome. Read the wildcard problem statement.
Pick an enterprise use case, such as debugging incidents, and automate it end to end using DevRev agents, workflows, MCP connectors and data objects.
Start with a ticket or engineering issue from Enterprise-Bench. Gather related records and knowledge articles, have an agent propose an evidence-backed diagnosis, route a follow-up for approval, and record the approved outcome in the sandbox.
Show the complete flow, including missing evidence, a declined action and recovery from a failed step. Do not claim to fix a production incident or invent a causal link.
The builder skill pack helps coding agents create and improve DevRev agents and workflows. Review its instructions, explicitly request the resource you want to create, and verify changes in your assigned playground.
The public builder pack has embedded example credentials replaced with placeholders. The wildcard uses the same Enterprise-Bench-only data boundary and permission-aware, approval-gated sandbox actions as the other build paths.
Reconcile account and opportunity records with supporting evidence. Flag missing or conflicting fields and propose grounded corrections.
Show: The current value, proposed change and its source. No guessing and no silent overwrites.
Bring together support history, engineering blockers and documented commitments into an explainable customer review.
Show: Evidence, missing inputs and useful next steps. Any score must disclose its rules and limitations.
Connect Computer to an external sandbox follow-up board. Turn commitments from supplied transcripts into task drafts, then create them after approval.
Show: The preview, user approval, source reference and duplicate prevention on repeated runs.
Connect engineering context with support cases and account records to help a support lead prepare a factual customer update.
Show: Verified links, clear uncertainty and no invented resolution dates.
DevRev will provide team playground access with Enterprise-Bench data and an SE-led kickoff. An SE is a solutions engineer who will walk through the environment, skills and supported connector setup.
Complete the short form with your name and your team leader's email. Solo builders can use their own email.
DevRev will share your playground setup and kickoff details through the nominated contact. Use the supplied data and approved sandbox tools.
Build your skill, connector or end-to-end automation. Test different records, missing evidence and another authorized user's experience.
Playground invitations, resource limits and the kickoff schedule will be communicated separately. Registration is a request for access, not an instant login.
Show a specific enterprise problem and a working solution. Explain what it adds beyond a generic chat prompt.
Use parameterized inputs. Demonstrate the workflow with another authorized colleague and different Enterprise-Bench records.
Make important claims inspectable. Handle missing data, ambiguous identities and partial results without inventing facts.
Respect permissions and keep credentials out of code. Preview and approve sandbox writes; handle errors and duplicates.
The builder guide covers custom MCP registration, organization-wide skills, worked examples, testing and troubleshooting.
The starter passed local protocol checks. Remote deployment and installation in your assigned playground still need validation. Hosting a connector requires a reachable, authenticated endpoint, not just a local script.
Register your team contact so DevRev can send the setup and access details. Do not include passwords or access tokens in the form.