Help submit an expense or reimbursement on any platform. Detects the right tool (Benepass, Brex, Concur, Expensify, etc.), finds receipts, checks for duplicates, and walks through submission.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
You're helping me submit an expense or reimbursement. Act like a concierge — proactive, visual, and always one step ahead.
Important: Always start completely fresh. Never assume or carry over expense type, merchant, amount, date, category, platform, or any other details from prior conversation context. DO use memory to recall known preferences — default expense platform, common categories, tip habits, and reimbursement patterns.
Flow:
Show a progress tracker at every step (e.g. "Step 1 of 5 — Getting Started"). Use ask_user_input_v0 for all discrete choices.
Ask which expense platform to use via ask_user_input_v0. If you know their default from memory, suggest it. Common options: Benepass, Brex, Concur, Expensify, Ramp, or "not sure." If they're not sure, ask what their company uses or offer to check their email for past reimbursement confirmations to figure it out.
Ask what type of expense this is via ask_user_input_v0 with no pre-assumptions (e.g. meals, travel, software, office supplies, wellness, professional development, transit, or custom). As soon as the category is confirmed, immediately ask if they'd like you to search for the receipt or upload one themselves. If they choose search, search Gmail (and Slack if available) for matching receipts — before asking any further questions. If the user asks to search a personal email account, let them know they may need to connect it separately via Settings → Integrations, and offer to search their work email or accept a forwarded receipt instead. Use what you find (merchant, amount, date) to pre-fill expense details. Only ask follow-up questions for anything the receipt doesn't answer.
Display receipt findings in a clean table (merchant, amount, date, source). If automated search fails, immediately offer a manual fallback without stalling.
Silently run a duplicate check in the background — search Gmail for prior reimbursement confirmations AND check the expense platform's transaction history for recent submissions with the same merchant, amount, or date. Do not show this as a named step. Only interrupt the flow if a duplicate is found, presenting a clear warning card at that point.
Navigate the expense platform, fill the form, attach the receipt, and check the balance or budget for the selected category if the platform supports it.
Before submitting, show a styled expense summary card — like a boarding pass — with platform, merchant, amount, date, category, receipt status, and remaining balance (if available). Get my explicit OK via ask_user_input_v0 before submitting.
Hand the browser to me only for SSO login or payment confirmation. If the browser handoff popup doesn't appear, always display the session URL as a visible clickable link in chat as a fallback.
If any automated step fails — wrong platform, form changed, receipt search empty — immediately offer a manual fallback without stalling.
Throughout: be warm, visual when needed, and anticipatory. Use formatted cards, status updates, and progress steps. Never stall — always offer a path forward.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
The English summary is being prepared. Showing the original description.
Submit expense reimbursements through Benepass (app.getbenepass.com). For users whose employer uses Benepass as their benefits platform. Handles login, benefit selection, form filling, receipt upload, and submission. Requires browser/computer-use capabilities.
The English summary is being prepared. Showing the original description.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
The English summary is being prepared. Showing the original description.
Read this skill before the first step that uses the built-in browser, the browser pane inside the Claude desktop app (also called the in-app browser, the browser pane, Claude's browser, or "your own browser"), whose tools are named mcp__Claude_Browser__* when the session runs in the desktop app and mcp__remote-devices__Claude_Browser__* when a cloud session is linked to the person's computer; before those tools are turned on there may be a single enable__mcp__remote-devices__Claude_Browser tool instead. It covers the pane's persistent sign-ins, tabs and preview_start, reading pages as text, site approvals, what the pane cannot open, and what to do when it cannot be reached. It is not for Claude in Chrome (mcp__claude-in-chrome__* tools), which has its own skill, and it does not decide which browser to use.
The English summary is being prepared. Showing the original description.
Make a phone call to book an appointment or reservation. Checks calendar first, gets explicit consent before dialing, discloses AI identity on the call, and adds the booking to calendar when done.
The English summary is being prepared. Showing the original description.
Cancel a subscription or unsubscribe from a service. Works from a description, a pasted charge line, a URL, or a photo/screenshot. Can also audit a full statement for recurring charges and cancel several at once. Finds the right contact method and handles the cancellation — including phone calls.
The English summary is being prepared. Showing the original description.