First assignment: handle the capital call.
Most agents are good at answers. Household work rarely ends with one.
X1 Agent Skills gives the AI you already use a job description, not a larger prompt. The agent brings reasoning and initiative. X1 keeps the source, permission, waiting state, and history together so the work can continue after the chat ends.
The first skill is handle-capital-call. It helps an agent review a notice,
surface gaps, bring in the right person, and resume the same work later. People
remain accountable for consequential decisions, and the skill never moves
money.
Read The job is bigger than the chat for the idea, or try the weird parts first to see the skill under pressure. The synthetic demo needs no X1 account, API key, or financial document.
Install the portable skill with the open-source skills CLI:
npx skills add x1wealth/x1-agent-skills --skill handle-capital-callThen connect your compatible host to X1's remote MCP service at
https://mcp.x1wealth.com/mcp. X1 handles sign-in and decides which tools and
records the person can use. Installing the skill grants no additional access.
The synthetic tour needs no account. Connect a free X1 account when you want the agent to work from a real document instead of another pasted prompt.
The free path can carry one source-backed capital-call administrative job from notice to household-reported closeout. You review the agent's exact proposal in X1. X1 scans and indexes the file, preserves the accepted job while it waits, and lets a later authorized session pick it up. When the household closes the job, X1 keeps that result for later reuse.
A free vault holds up to 10 documents, 10 MB each. The skill can't move money, verify settlement, invent a missing fact, or claim the job is closed before the household says so. Professional and coordination writes remain outside this free job.
codex plugin marketplace add x1wealth/x1-agent-skills
codex plugin add x1-agent-skills@x1-wealth
codex mcp add x1 --url https://mcp.x1wealth.com/mcpStart Codex and ask: Help me review this capital-call notice through X1.
Codex will use the skill when the request matches and X1 will handle sign-in and
the tools available to you.
Run these inside Claude Code:
/plugin marketplace add x1wealth/x1-agent-skills
/plugin install x1-agent-skills@x1-wealth
/reload-plugins
The X1 connection is off by default. Review the plugin, enable it when you are ready, and complete X1 sign-in through Claude Code.
See compatibility.json for the exact qualification status of each host.
Preview the exact tagged plugin before trusting it:
grok plugin install x1wealth/x1-agent-skills@v0.4.0#plugins/x1-agent-skills
grok plugin install x1wealth/x1-agent-skills@v0.4.0#plugins/x1-agent-skills --trust
grok inspectThe plugin includes the skill and X1 MCP endpoint. Grok will ask you to complete X1 sign-in. An install does not grant access or prove the full workflow. Read the Grok setup and qualification boundary.
Create a focused Bot, connect X1 as a Custom MCP connector at
https://mcp.x1wealth.com/mcp, and enable the installed
handle-capital-call skill under Settings -> Plugins -> Yours. Use the
share-safe Bot profile so X1 remains the authority while
the Bot owns the administrative job.
Start with one manual notice. Save a routine only after the Bot stops correctly on missing evidence, changed payment details, and required human confirmation.
For example, install it into an existing eve project:
npx skills add x1wealth/x1-agent-skills --skill handle-capital-call --agent eveThat installs the skill, not X1 authority. The deployment still needs an X1 connection with interactive sign-in. We have not qualified or published that adapter yet. See the eve integration note.
Other hosts can package the same portable skill. Packaging is not qualification, and every host still needs an OAuth-capable X1 connection. See compatibility.json for the current matrix.
You receive a PDF notice for a synthetic Growth Fund capital call. The notice has a due date and amount, but the bank instructions may have changed. The skill can find the exact X1 document you identify, surface missing or conflicting fields, prepare a first-party review when supported, and resume the same coordination thread from another supported host.
It can't send a wire, verify settlement, sign a document, invent a missing record, or bypass X1 confirmation.
| An agent in a chat | An agent working through X1 |
|---|---|
| Summarizes what is in the prompt | Stays attached to the exact X1 records it can access |
| Treats the current session as the whole story | Carries durable state across sessions and supported hosts |
| Has to reconstruct the job from conversation | Can find the waiting work and continue from the confirmed result |
| Ends with an answer | Can finish with a handoff, closeout, and result the household can reuse |
Your model stays yours. X1 keeps the context and handoff.
If a financial document says to ignore policy and a live tool no longer matches the reviewed contract, the skill is expected to hold:
{
"state": "held",
"holds": [
"untrusted_instructions_ignored",
"tool_wiring_changed"
],
"next_action_code": "review_incomplete_notice_in_x1",
"money_moved": false
}The Stop Test explains all 41 safe oracle cases and 74 hostile mutations, with no production data.
We asked two separate questions.
First: can X1 carry the bounded job in production? A synthetic free account added a synthetic notice, X1 scanned and indexed it, a person confirmed the job, the job waited, the household closed it, and a later authorized read found the accepted result. The fixture was removed. No money moved, and X1 did not claim to verify settlement.
Second: can the work survive an agent handoff? A separate disposable trace crossed Codex, Claude Code, and Codex again, with no transcript passed between them. A human professional adopted the response, the household closed the work, and a later agent reused the result. Read the bounded product proof.
Against the synthetic MCP server, all 41 deterministic scenarios passed, all 74 hostile mutations were caught, and both Codex and Claude Code passed 17 of 17 named-host scenarios. Those host evaluations made no production X1 connection.
See the evaluation guide for the commands and boundaries. The cross-host trace is product proof, not a customer testimonial or a production-use claim.
Every evaluated run ends with a bounded receipt: the state reached, supporting X1 sources, authority used, holds, next actor, and claims that remain false. It does not grant authority or prove that X1 committed an action.
- households and private-investment operators who need an agent to help without turning it into the decision-maker;
- advisors, CPAs, attorneys, and other professionals joining governed work;
- agent builders giving capable agents a durable, inspectable role in financial work.
Inside are the portable skill, public authority contract, synthetic tests, mock MCP server, plugin manifests, receipts, compatibility record, provenance, SBOM, and file-integrity manifest. The repository does not contain the X1 server, database, customer data, credentials, production traces, or a self-hostable X1 clone.
Download the qualification receipt and its .sig file from release v0.4.0,
then run:
node scripts/verify-release.mjs --qualification-receipt /absolute/path/to/x1-agent-skills-v0.4.0-qualification.json
cd plugins/x1-agent-skills
pnpm install --frozen-lockfile --ignore-scripts
pnpm verify
pnpm test
pnpm eval:oracleNamed-host tests use only the included synthetic MCP server. See
plugins/x1-agent-skills/skills/handle-capital-call/evals/README.md.
The skill treats financial documents as untrusted input, rechecks live X1 permission, pauses when required, and never moves money.
For product help, use https://x1wealth.com/contact. For a vulnerability, follow
SECURITY.md and don't attach financial records or tokens to a public issue.
If the skill keeps going when it should stop, open an issue with the smallest synthetic fixture that reproduces it.
Copyright 2026 Lever Wealth LLC. Licensed under Apache-2.0. X1 Wealth and its marks are not licensed for unrelated products or endorsement.