← Back to Skills Marketplace
byungkyu

microsoft-excel

by byungkyu · GitHub ↗ · v1.2.5 · MIT-0
cross-platform ✓ Security Clean
27996
Downloads
42
Stars
0
Active Installs
12
Versions
Install in OpenClaw
/install microsoft-excel
Description
Microsoft Excel API integration with managed OAuth. Read and write Excel workbooks, worksheets, ranges, tables, and charts stored in OneDrive. Use this skill when users want to read or modify Excel spreadsheets, manage worksheet data, work with tables, or access cell values. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Microsoft Excel connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Microsoft Excel action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Microsoft Excel examples; they add no Microsoft Excel capability - Microsoft Excel is not an event source, a trigger cannot read Microsoft Excel data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install this only if you want Maton to access Excel data in your Microsoft account. Before using it, confirm the account and scopes, approve every write or automation separately, keep trigger scopes narrow, and only use the non-Excel trigger references when you intentionally want cross-app automation with a named source and destination.
Capability Assessment
ℹ Credentials
Network access, Bash, and an OAuth-backed Maton account are proportionate for API integration, and the instructions default to read/list calls with confirmation before writes or new connections.
✓ Install Mechanism
Installation is through pinned Maton CLI package instructions or Homebrew with pinning; the artifact contains Markdown documentation and no executable scripts.
ℹ Instruction Scope
The package includes shared trigger catalogues for non-Excel sources such as Linear, but the artifact repeatedly states they do not expand Excel capability and should be used only when the user names that connected source.
ℹ Persistence & Privilege
OAuth tokens are stored in the OS credential store, and functions, triggers, and destinations can persist, but these behaviors are disclosed with explicit approval, scoping, and deletion guidance; no hidden persistence was found.
ℹ Purpose & Capability
The skill's main capability is reading and writing Excel workbooks through Microsoft Graph via Maton-managed OAuth, which matches its stated purpose; hosted functions and triggers are documented as optional automation around approved Excel actions.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install microsoft-excel
  3. After installation, invoke the skill by name or use /microsoft-excel
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.5
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.4
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.3
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.2
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.1
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.4
- Base API URLs updated from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for all endpoints. - Connection management instructions revised to reflect new URLs. - Security note added: all write operations now require explicit user approval and confirmation of target resource. - "LICENSE.txt" file removed.
v1.0.3
- Added a "clawdbot" metadata section specifying the required environment variable (`MATON_API_KEY`) and an identifying emoji. - No other changes to functionality or documentation.
v1.0.2
- Documentation in SKILL.md simplified by removing the duplicated and overly detailed API reference section. - No changes to functionality or code; this release updates documentation only.
v1.0.1
No user-facing changes in this version. - No file changes detected between versions 1.0.0 and 1.0.1. - Skill behavior and documentation remain unchanged.
v1.0.0
Initial release: Integrate Microsoft Excel API using managed OAuth via Maton. - Read and write Excel workbooks, worksheets, ranges, tables, and charts stored in OneDrive or SharePoint. - Supports file access by both path and file ID, with full coverage of worksheet and range operations. - Includes connection management with API calls for listing, creating, retrieving, and deleting OAuth connections. - Allows session management for improved performance on batch operations. - Requires network access and a valid Maton API key for authentication. - Provides detailed usage examples and API references in SKILL.md.
Metadata
Slug microsoft-excel
Version 1.2.5
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 12
Frequently Asked Questions

What is microsoft-excel?

Microsoft Excel API integration with managed OAuth. Read and write Excel workbooks, worksheets, ranges, tables, and charts stored in OneDrive. Use this skill when users want to read or modify Excel spreadsheets, manage worksheet data, work with tables, or access cell values. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Microsoft Excel connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Microsoft Excel action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Microsoft Excel examples; they add no Microsoft Excel capability - Microsoft Excel is not an event source, a trigger cannot read Microsoft Excel data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 27996 downloads so far.

How do I install microsoft-excel?

Run "/install microsoft-excel" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is microsoft-excel free?

Yes, microsoft-excel is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does microsoft-excel support?

microsoft-excel is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created microsoft-excel?

It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.5.

💬 Comments