microsoft-sharepoint_skill

This skill helps you manage SharePoint data and workflows by guiding action usage and authentication with the Membrane CLI.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill microsoft-sharepoint

  • _meta.json297 B
  • SKILL.md6.1 KB

Overview

This skill integrates Microsoft SharePoint into your workflows so you can manage sites, libraries, lists, files, and users programmatically. It exposes common SharePoint operations (list, get, create, update, delete) and supports both high-level actions and direct API proxying. Use it to browse content, automate content updates, and wire SharePoint into backend processes.

How this skill works

The skill uses the Membrane CLI as a bridge to SharePoint, letting Membrane handle authentication, token refresh, pagination, and error handling. You run predefined actions (e.g., list-sites, get-file-content, create-list-item) or send proxied HTTP requests through Membrane when you need custom API calls. Inputs and schemas for each action are discoverable via Membrane action listing and run via membrane action run with JSON parameters.

When to use it

  • Browse and index available SharePoint sites, drives, lists, and files programmatically.
  • Download or stream file content from SharePoint for processing or backup.
  • Create or update list items or files as part of an automation or integration flow.
  • Delete or archive items and folders based on lifecycle or retention rules.
  • Proxy custom SharePoint REST calls when a prebuilt action does not cover a specific endpoint.

Best practices

  • Prefer Membrane prebuilt actions for common operations to get built-in auth, pagination, and error handling.
  • Discover actions first with membrane action list --intent=... to avoid reinventing API calls.
  • Create and reuse a single connection per tenant instead of embedding credentials; Membrane manages the auth lifecycle.
  • Use the proxy request feature for edge cases, but validate inputs and responses since you’ll be dealing with raw API shapes.
  • Pass structured JSON input to actions to ensure predictable results and reduce retries.

Example use cases

  • List all SharePoint sites a user can access and present them in an admin dashboard.
  • Automate ingestion: download new files from a document library, process them, then update metadata or move them to an archive folder.
  • Create and populate a SharePoint list item from a form submission or third-party webhook.
  • Fetch file versions to perform audit, restore, or comparison operations.
  • Send a custom REST request through the proxy to call a SharePoint endpoint not covered by available actions.

FAQ

No. Membrane handles authentication and refresh; you create a connection and let Membrane manage tokens server-side.

Can I call any SharePoint REST endpoint?

Yes. Use the membrane request proxy to forward arbitrary REST calls; Membrane injects auth headers and base URL automatically.

How do I discover available actions and required inputs?

Run membrane action list with an intent and connectionId to see action IDs and input schemas, then run membrane action run with JSON input.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational