bel-move-mail-to-archive

Move a single Microsoft 365 email message to the Archive folder.

2|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/bennoloeffler/bassi --skill bel-move-mail-to-archive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bel-move-mail-to-archive
Source: https://github.com/bennoloeffler/bassi/tree/main/.claude/skills/bel-move-mail-to-archive
Command: npx skills add https://github.com/bennoloeffler/bassi --skill bel-move-mail-to-archive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Enables reliable one-at-a-time moves of MS365 emails to Archive, minimizing context bloat and avoiding batch-related errors.

Core Features & Use Cases

  • One-at-a-time operations: single-message moves for reliability.
  • Parameter preparation: CLI script returns API-ready parameters for Claude tools.
  • Archive config: uses default archive folder or a custom ID if provided.

Quick Start

python scripts/move_to_archive.py --message-id "<msg-id>" [--archive-id "<custom-id>"]

Frequently Asked Questions about bel-move-mail-to-archive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I move emails to archive in Microsoft 365?

Move emails to archive in Microsoft 365 by using the mcp__ms365__move-mail-message API with the message ID and archive folder destination ID. This Skill automates one-at-a-time moves to reliably archive individual emails without batch processing errors.

Can I automate email archiving for MS365 accounts?

Yes, automate email archiving by running the CLI script with a message ID and optional custom archive folder ID. The Skill orchestrates individual archive moves that can be triggered in bulk via sub-agents while keeping context clean.

What's the best way to handle spam and notification emails in Microsoft 365?

Archive spam and notification emails one at a time using this Skill to avoid batch errors and context pollution. It returns structured results including message ID, parent folder, subject, and received date for reliable processing.

Does this work with custom archive folders in MS365?

Yes, the Skill accepts an optional archive folder ID parameter to use custom archive locations, or defaults to your configured archive folder if no ID is provided.

Why use one-at-a-time email moves instead of batch operations?

One-at-a-time moves minimize context bloat and avoid batch-related errors when processing individual archiving tasks like spam or notifications, especially when orchestrated through sub-agents.