Manage SharePoint sites, lists, files, and folders through pre-built actions with automatic authentication.
Works with
Provides 20+ actions covering site discovery, list and item management, file operations, versioning, and folder creation
Supports direct API proxy requests to SharePoint endpoints when pre-built actions don't cover your use case
Handles authentication and credential refresh automatically through Membrane CLI; no manual token management required
Includes action discovery via
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmicrosoft-sharepointExecute the skills CLI command in your project's root directory to begin installation:
Fetches microsoft-sharepoint from membranedev/application-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate microsoft-sharepoint. Access via /microsoft-sharepoint in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
24
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
24
stars
Microsoft SharePoint is a web-based collaboration and document management platform. It's primarily used by organizations of all sizes to store, organize, share, and access information from any device. Think of it as a central repository for files and a tool for team collaboration.
Official docs: https://learn.microsoft.com/sharepoint/dev/
When to use which actions: Use action names and parameters as needed.
This skill uses the Membrane CLI to interact with Microsoft Sharepoint. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/cli
membrane login --tenant
A browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search microsoft-sharepoint --elementType=connector --json
Take the connector ID from output.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --json
The user completes authentication in the browser. The output contains the new connection id.When you are not sure if connection already exists:
membrane connection list --json
If a Microsoft Sharepoint connection exists, note its connectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --json
This will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| List Drive Items | list-drive-items | Lists items (files and folders) in a drive or folder. |
| List Lists | list-lists | Lists all SharePoint lists in a site. |
| List Sites | list-sites | Lists the SharePoint sites that the user has access to. |
| List File Versions | list-versions | Lists all versions of a file. |
| List List Items | list-list-items | Lists all items in a SharePoint list. |
| List Drives | list-drives | Lists the document libraries (drives) available in a SharePoint site. |
| Get Drive Item | get-drive-item | Retrieves metadata for a specific file or folder in a drive. |
| Get Drive Item by Path | get-drive-item-by-path | Retrieves metadata for a file or folder using its path. |
| Get List Item | get-list-item | Retrieves a specific item from a SharePoint list. |
| Get File Content | get-file-content | Downloads the content of a file. |
| Get List | get-list | Retrieves details about a specific SharePoint list. |
| Get Drive | get-drive | Retrieves details about a specific drive (document library). |
| Get Site | get-site | Retrieves details about a specific SharePoint site. |
| Create List Item | create-list-item | Creates a new item in a SharePoint list. |
| Create Folder | create-folder | Creates a new folder in a drive. |
| Create List | create-list | Creates a new SharePoint list in a site. |
| Update Drive Item | update-drive-item | Updates the metadata of a file or folder (e.g., rename). |
| Update List Item | update-list-item | Updates an existing item in a SharePoint list. |
| Delete Drive Item | delete-drive-item | Deletes a file or folder from a drive. |
| Delete List Item | delete-list-item | Deletes an item from a SharePoint list. |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json
To pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"
When the available actions don't cover your use case, you can send requests directly to the Microsoft Sharepoint API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpoint
Common options:
| Flag | Description |
|---|---|
-X, --method |
HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header |
Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data |
Request body (string) |
--json |
Shorthand to send a JSON body and set Content-Type: application/json |
--rawData |
Send the body as-is without any processing |
--query |
Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam |
Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
I recommend microsoft-sharepoint for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: microsoft-sharepoint is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added microsoft-sharepoint from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: microsoft-sharepoint is focused, and the summary matches what you get after install.
microsoft-sharepoint reduced setup friction for our internal harness; good balance of opinion and flexibility.
microsoft-sharepoint is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added microsoft-sharepoint from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
microsoft-sharepoint fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
microsoft-sharepoint is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for microsoft-sharepoint matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 72