ksuite-setup
Skill0 starsChanged 45 days agoMITView on GitHub
Connect and use Infomaniak kSuite (Mail, Calendar, tasks, Contacts, kDrive, kChat, kMeet, Chk, kPaste). Use when the user says "connecte kSuite", "connect my mail / calendar / kDrive / kChat", "Infomaniak", asks to read mail, check the agenda, create a draft, post to kChat, or when another skill needs mail, calendar, files or team chat.
- Reads credentials
- Installs packages
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- analystSkill
- build-appSkill
- build-websiteSkill
- business-setupSkill
- content-pipelineSkill
- content-writerSkill
- email-assistantSkill
- email-digestSkill
- meeting-prepSkill
- memorySkill
- odooSkill
- plugin-builderSkill
- qfieldcloudSkill
- qgisSkill
- quarto-slidesSkill
- research-leadSkill
- researchSkill
- r-sessionSkill
- schedulerSkill
- scrum-masterSkill
- skill-creatorSkill
- task-managerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 1 is distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Prefer layer A when its tools are present in your tool list.
- Very specific: line 31
If the user wants a real test: add --test (tries IMAP, SMTP and CalDAV logins, sends nothing).
- Very specific: line 39
Use the step-by-step walkthrough below only if the user prefers to edit .env by hand.
- Very specific: line 43
Follow .claude/rules/connections-protocol.md: one step per message, wait for "ok", number the steps, never ask for the account password.
- Very specific: line 47
.env exists?: If not: copy .env.example to .env (offer to do it).
- Very specific: line 60
Add, pick the channel, copy the URL into KCHAT_WEBHOOK_URL.
- Very specific: line 79
Update config/preferences.yaml: email: ksuite, calendar: ksuite, chat: kchat, files: kdrive, and task_manager: ksuite if the user wants …
- Very specific: line 112
All scripts print JSON with a success key.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
kSuite (Infomaniak) connector
kSuite is the default suite of AIGORA (replaces Google Workspace and Slack). Two complementary layers, both optional and independent:
| Layer | What | Needs | Best for |
| A. Official Infomaniak MCP servers | mcp__ksuite-mail__*, mcp__ksuite-calendar__*, mcp__ksuite-kdrive__*, mcp__ksuite-kchat__*, mcp__ksuite-contact__* | Node.js + one API token | Interactive work: search mail, list events, browse kDrive, read kChat, find a contact |
| A'. Community MCP server (opt-in) | mcp__ksuite-extra__*: tasks, kMeet rooms, Chk short links, kPaste | KSUITE_EXTRA_MCP=1, token + DAV login | What Infomaniak has no official MCP for |
| B. Local Python scripts (this skill) | IMAP/SMTP, CalDAV (events + tasks), CardDAV (contacts), kChat webhook | Mail app password, DAV login, webhook URL | Deterministic pipelines (email-digest, scrum-master), no Node.js |
| C. kDrive desktop folder | Plain files in the folder synced by the kDrive app (KDRIVE_LOCAL_PATH) | kDrive desktop app, link_kdrive.py | Reading client files, saving deliverables; works on every plan |
Full inventory of Infomaniak tools and status: docs/KSUITE.md.
Prefer layer A when its tools are present in your tool list. Fall back to layer B scripts otherwise. Never ask for the main Infomaniak account password: only application passwords and API tokens.
Step 0: Check status (always first)
python3 .claude/skills/ksuite-setup/scripts/check_status.pyIf the user wants a real test: add --test (tries IMAP, SMTP and CalDAV logins,
sends nothing).
Fastest setup: let the user run it in R
Recommend first: aigora_ksuite_configurer() in the RStudio console. It asks for the CalDAV
short username, the mail address, application passwords (masked, never shown to you) and the
kChat webhook, writes .env, installs caldav if needed and runs the connection tests.
Use the step-by-step walkthrough below only if the user prefers to edit .env by hand.
Setup walkthrough (one step per message, in French if preferences say so)
Follow .claude/rules/connections-protocol.md: one step per message, wait for
"ok", number the steps, never ask for the account password. The user-facing guide
with screenshots-level detail is docs/KSUITE.md; quote from it.
- .env exists? If not: copy
.env.exampleto.env(offer to do it). - Mail (IMAP/SMTP): IMAP/SMTP needs a device password of the mail address, NOT the
account application password (that one only works for CalDAV/CardDAV). Path:
manager.infomaniak.com > Service Mail > domain > address > "Appareils" tab >
"Ajouter un appareil" (or the assistant at config.infomaniak.com). Login = full address.
Symptom of the wrong password type: CalDAV/CardDAV OK but IMAP "Invalid login or password".
They fill
KSUITE_MAIL_USER(full address) andKSUITE_MAIL_PASSWORDin.envthemselves. Do not ask them to paste the password in the chat; if they do, write it to.envand tell them it is now stored only there. - Calendar (CalDAV): username from https://config.infomaniak.com > My Calendar >
Manual synchronization (short form like
AB12345). FillKSUITE_DAV_USER,KSUITE_DAV_PASSWORD. Thenpip install caldav. - kChat webhook (optional): kChat > New > Integrations > Incoming Webhooks >
Add, pick the channel, copy the URL into
KCHAT_WEBHOOK_URL. - API token for MCP servers (optional, layer A): https://manager.infomaniak.com/v3/ng/accounts/token/list,
create a token with scopes
workspace:mail,workspace:calendar,user_info,drive,kchat(only the ones wanted). Put it inINFOMANIAK_TOKEN. AddKDRIVE_ID(number in the kDrive URL.../app/drive/123456/...) andKCHAT_TEAM_NAME(<team>inhttps://<team>.kchat.infomaniak.com). Then:
Tell the user to restart Claude Code in the RStudio Terminal (python3 .claude/skills/ksuite-setup/scripts/register_mcp.py --dry-run python3 .claude/skills/ksuite-setup/scripts/register_mcp.py/exit, thenclaude). - kDrive folder (recommended, every plan): the user installs the kDrive desktop app, then
python3 .claude/skills/ksuite-setup/scripts/link_kdrive.py(auto-detects~/kDrive, or--path). In R:aigora_kdrive(). Restart Claude Code. - Community server (optional): only if the user wants kMeet / Chk / kPaste / tasks via MCP.
Explain it is a young community project (MIT), filtered to those tools with strict send
confirmation. Then
KSUITE_EXTRA_MCP=1in.envandregister_mcp.py --only extra. - Test:
check_status.py --test(IMAP, SMTP, CalDAV, CardDAV), and with MCP: callcalendar_list_calendars. - Update
config/preferences.yaml:email: ksuite,calendar: ksuite,chat: kchat,files: kdrive, andtask_manager: ksuiteif the user wants tasks on the phone.
Everyday commands (layer B)
# Mail: read (read-only, does not mark as read)
python3 .claude/skills/ksuite-setup/scripts/mail_fetch.py --hours 24 [--unread-only] [--output .tmp/x.json]
# Mail: create drafts (NEVER sends; the user sends from kSuite Mail)
python3 .claude/skills/ksuite-setup/scripts/mail_draft.py --to a@b.ch --subject "..." --body-file .tmp/draft.txt [--in-reply-to "<message-id>"]
python3 .claude/skills/ksuite-setup/scripts/mail_draft.py --from-json .tmp/drafts.json
# Calendar
python3 .claude/skills/ksuite-setup/scripts/calendar_events.py calendars
python3 .claude/skills/ksuite-setup/scripts/calendar_events.py list --days 7
python3 .claude/skills/ksuite-setup/scripts/calendar_events.py create --summary "..." --start "2026-10-06 14:00" --end "2026-10-06 15:00" [--calendar "..."]
# Tasks (CalDAV VTODO, synced to the phone by kSync / iOS Reminders)
python3 .claude/skills/ksuite-setup/scripts/calendar_events.py tasks [--all]
python3 .claude/skills/ksuite-setup/scripts/calendar_events.py task-add --summary "..." [--due 2026-10-09] [--priority high]
python3 .claude/skills/ksuite-setup/scripts/calendar_events.py task-done --uid <uid>
# Contacts (CardDAV, read-only)
python3 .claude/skills/ksuite-setup/scripts/contacts.py search "dupont"
python3 .claude/skills/ksuite-setup/scripts/contacts.py export --output data/contacts.csv
# kDrive local folder
python3 .claude/skills/ksuite-setup/scripts/link_kdrive.py [--path "..."] [--unlink]
# kChat (posts to other people: confirm with the user first)
python3 .claude/skills/ksuite-setup/scripts/kchat_post.py --file .tmp/briefing.mdAll scripts print JSON with a success key.
Rules
- Drafts, never direct sending. The scripts have no send command on purpose.
- Confirm before: posting to kChat, creating or deleting calendar events, moving or
deleting mail or kDrive files through MCP tools (
confirm_before_sending: true). - kDrive WebDAV is not available on kSuite Free/Standard plans and is unsupported by Infomaniak: use the synced folder (layer C) or the kDrive MCP server.
- Mail sending through MCP is denied in
.claude/settings.json(mail_send_email). Keep it that way unless the user explicitly removes the rule. - SwissTransfer cannot be automated reliably (anti-bot captcha): prepare the file in kDrive and let the user send it from swisstransfer.com or the app.
- Secrets live only in
.envand in Claude Code's local MCP config. Never echo them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

