Vergio agent skill

Install a portable Vergio skill in any MCP client and keep opportunity decisions written back correctly.

Install the Vergio skill in any MCP client that accepts a SKILL.md file. It gives your agent the Monday Opportunity Briefing recipe, the permission boundary, and the required write-back convention.

• Open or download the complete SKILL.md
• Read the Monday Opportunity Briefing
• Fetch the machine-readable playbook manifest

Keep tool definitions current

Use the MCP reference as the source of tool truth. It renders the composed surface from Vergio's core tools, wallet tools, and managed watch tools. The skill teaches how to use those tools together. It does not copy their input schemas or prices.

Wallet and managed-watch tools require their scopes and an active commercial state. If any tool returns an unavailable result, handle it gracefully and do not blind-retry.

Understand exposure evidence

When Vergio returns account rows over REST or MCP, delivered_to_agent proves only that Vergio delivered the rows to an agent; whether a human saw them is unknown. selected_for_first_party_surface means the ranker selected rows for the agency's first-party surface at list-build time; it is a selection decision, not a render or view receipt. Neither class proves a human viewed the rows. With your own agent, write back operator decisions through record_outcome or set_account_status to restore that missing fidelity.

Write every operator decision back

Begin every opportunity workflow with list_in_market_accounts. This is step one of every playbook.

After presenting opportunities to your operator, record what happened:

• For a pursued deal, call record_outcome with a DEAL_STAGES action.
• For a dismissed opportunity, call set_account_status with not_a_fit, or use the dismissal-with-reason path.

Never promise or send a generic dismissed action to record_outcome. That tool does not accept one.

Respect recorded authority

Vergio prepares any next action but sends only through a channel and recipient with recorded authority. If authority is absent or unclear, prepare a channel-neutral action package and stop before sending.

The downloadable artifact carries its playbook key and version in the header. It is machine-readable-stable for that declared version.

Updated July 23, 2026