Automated summary

Walks the user step by step through registering, authenticating, and verifying the Well MCP server connection, then suggests starter prompts.

Strengths

Breaks setup into short conversational steps and skips ones already completed
Distinguishes an auth error from a temporary data-path outage instead of implying setup failed
Confirms the connection with a real well_get_schema call and reports the data types found
Offers concrete starting prompts and points to the deeper Well skills

Limitations

Tied to the Well plugin on Claude Code, not reusable for other tools
Troubleshooting stops at sending the user back to the authenticate step

When to use it

Run it right after installing the Well plugin or whenever the Well tools stop responding.

When not to use it

Don't use it for other MCP servers or for accounting analysis already handled by the dedicated Well skills.

Security analysis

Safe

Quality score84/100

This is a pure onboarding/verification guide for an MCP server connection. It contains no shell commands, no network fetches, no credential handling beyond pointing the user at the host's built-in OAuth browser flow, and no instructions to read or transmit files or secrets. The only tool call it suggests is `well_get_schema`, a read-only schema probe, so there is no meaningful execution risk.

No concerns found

How this analysis is made

Examples

First-time setup

I just installed the Well plugin — can you connect it and check that it works?

Connection not working

/well:connect — the Well MCP isn't working, nothing happened when I tried it.

After reinstall

I reinstalled the Well plugin, help me re-authenticate and confirm my workspace data is reachable.

name: connect description: Connect and verify the Well MCP — authenticate, confirm the tools work, and show what to ask. Use when the user runs /well:connect, just installed the Well plugin, or says the Well connection/MCP "isn't working" / "nothing happened". disable-model-invocation: false

Connect to Well

Name: Connect to Well
Author: Skills Guide Bot

Run this right after installing the Well plugin, or whenever the Well tools aren't responding. Walk the user through it conversationally — do not dump all steps at once if a step is already done.

1. Confirm the MCP server is registered

Installing the plugin auto-adds the well MCP server (it is bundled in the plugin manifest). If the user just installed it, make sure it's active:

Tell them to run /reload-plugins if they haven't since installing.
The server should now appear when they run /mcp.

2. Authenticate (one time, browser sign-in — no API key)

The Well MCP uses OAuth, so the first connection needs a one-time sign-in:

Run /mcp, select well, and choose Authenticate. A browser opens — sign in to your Well account and approve. No API key, no config.

If /mcp shows well as already authenticated, skip this.

3. Verify it works

Call well_get_schema (no arguments) to confirm the connection is live. If it returns the list of roots (companies, invoices, transactions, ledger_accounts, …), the connection is working — tell the user "Connected ✓, N data types available."

If it returns an auth error, send them back to step 2. If it returns a server error on the heavy roots, the connection is fine but the workspace data path may be temporarily unavailable — say so rather than implying the setup failed.

4. Show what to ask

Once connected, offer 3 concrete starting prompts so the user gets value immediately:

"Summarize last month's cash flow"
"List my unpaid invoices over €5,000"
"Build my compte de résultat for the last quarter"

Mention the deeper skills are available too: /well:reconciliation, /well:vat-summary, /well:ar-aging, /well:month-end-close, /well:compte-de-resultat, /well:balance-sheet, /well:cash-flow-forecast.

Note on billing

Tool calls use Well credits, billed to the workspace plan. Mention this once if the user asks about cost — do not interrupt every call.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/connect-to-well-mrwakfki/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/connect-to-well-mrwakfki' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/connect-to-well-mrwakfki/download' --output '.skill-downloads/connect-to-well-mrwakfki/SKILL.md.part' && mv '.skill-downloads/connect-to-well-mrwakfki/SKILL.md.part' '.skill-downloads/connect-to-well-mrwakfki/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/connect-to-well-mrwakfki/SKILL.md' && test -s '.skill-downloads/connect-to-well-mrwakfki/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/connect' && cp -R '.skill-downloads/connect-to-well-mrwakfki' '.claude/skills/connect'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/connect-to-well-mrwakfki'

openskills read 'connect-to-well-mrwakfki'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/connect-to-well-mrwakfki/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot