Use when the user wants to read or write SharePoint lists, manage documents in a SharePoint document library, or create a new SharePoint list from a Power Apps mobile app.
npx skills add https://github.com/microsoft/power-platform-skills --skill add-sharepoint
📋 Shared instructions: shared-instructions.md — read first.
References:
Two paths: existing lists (skip to Step 6) or new lists (full workflow).
Check for memory-bank.md per shared-instructions.md.
Also confirm this is a mobile app:
test -f power.config.json && test -f app.config.js && echo "OK" || echo "ERROR: not a mobile app"
Ask the user:
If lists already exist: Skip to Step 6.
If creating new lists:
EnterPlanMode, present the list designs with columns and typesExitPlanModeSee api-authentication-reference.md for full details.
az account show # Verify Azure CLI logged in
$api = Initialize-SharePointGraphApi -SiteUrl "https://<tenant>.sharepoint.com/sites/<site-name>"
$headers = $api.Headers
$siteId = $api.SiteId
Requires Sites.Manage.All permission.
Always query existing lists first before creating:
$existingLists = Invoke-RestMethod -Uri "https://graph.microsoft.com/v1.0/sites/$siteId/lists?`$select=id,displayName,description,list&`$filter=list/hidden eq false" -Headers $headers
See list-management-reference.md for Find-SimilarLists, Compare-ListSchemas, and Get-ListSchema functions.
Present findings to user with AskUserQuestion:
Print before starting:
> "→ Creating SharePoint lists via Graph API (sequential per list, columns added after list exists)…"
Get explicit confirmation before creating. Use safe functions from list-management-reference.md:
New-SharePointListIfNotExistsAdd-SharePointColumnIfNotExistsAdd-SharePointLookupColumn (for cross-list references)Get the SharePoint Online connection ID (see connector-reference.md):
npx power-apps create-connection --api-id shared_sharepointonline --json
Use shared_sharepointonline as the apiId and capture connectionId from the output. Use these exact values in the commands below.
If create-connection cannot complete because browser-based connection creation is disabled or the connector needs interactive auth, direct the user to create one:
> Open https://make.powerapps.com/environments/<environment-id>/connections → + New connection → search "SharePoint" → Create. Then provide the connection ID or rerun /list-connections shared_sharepointonline.
Print before starting:
> "→ Discovering SharePoint sites accessible to this connection…"
npx power-apps list-datasets --api-id <apiId-from-list> --connection-id <connection-id> --json
Present the sites to the user and ask which one(s) they want to connect to. If the user already specified a site URL, confirm it appears in the list.
If npx power-apps list-datasets fails or returns no results:
Print before starting:
> "→ Discovering lists/document libraries on each selected site…"
For each selected site:
npx power-apps list-tables --api-id <apiId-from-list> --connection-id <connection-id> --dataset '<site-url>' --json
Present the tables to the user and ask which ones they want to add. Suggest tables that look relevant to their use case. If lists were created in Step 5, they should appear here.
Print before starting:
> "→ Running npx power-apps add-data-source per list (sequential, ~10–20 seconds each)."
SharePoint is a tabular datasource — requires --connection-id, --dataset, and --resource-name:
npx power-apps add-data-source --api-id <apiId-from-list> --connection-id <connectionId-from-list> --dataset '<site-url>' --resource-name '<table-name>'
Run once per list or document library.
Read sharepoint-reference.md before writing any SharePoint code — column encoding, choice fields, and lookups have critical gotchas.
Use Grep to find methods in src/generated/services/SharePointOnlineService.ts (generated files can be very large — see connector-reference.md).
Sample usage:
import { SharePointOnlineService } from '../../src/generated/services/SharePointOnlineService';
// Read items
const result = await SharePointOnlineService.GetItems({
dataset: 'https://contoso.sharepoint.com/sites/projects',
table: 'Project Milestones',
});
const items = result.value ?? [];
// Create item
await SharePointOnlineService.PostItem({
dataset: 'https://contoso.sharepoint.com/sites/projects',
table: 'Project Milestones',
item: { Title: 'Launch review', Status: 'Not Started' },
});
// Update item (SharePoint IDs are integers, not GUIDs)
await SharePointOnlineService.PatchItem({
dataset: 'https://contoso.sharepoint.com/sites/projects',
table: 'Project Milestones',
id: 42,
item: { Status: 'Done' },
});
Print before starting:
> "→ Regenerating connector schemas + running tsc to verify SharePoint services compile (~15–30 seconds)."
> Native diff: npx tsc --noEmit instead of npm run build. Do NOT run platform-specific native build commands here.
npx power-apps add-data-source wrote new files into .power/schemas/sharepointonline/. Regenerate connectorSchemas.ts before type-checking so the new list is wired into the runtime schema map:
npm run generate-schemas
npx tsc --noEmit
Fix TypeScript errors before proceeding.
Update memory-bank.md with: connector added, site URL, lists/libraries connected (or created), type-check status.
> Note: No manual executor wiring needed. PowerAppsProvider in app/_layout.tsx handles SharePoint connector routing, connection resolution, and OAuth consent automatically at runtime.
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.
Securely inspect and automate microscopy data workflows against OMERO.server with omero-py, BlitzGateway, OMERO CLI, tables, annotations, ROIs, rendering, and documented OMERO.web APIs. Use for scoped OMERO inventory, metadata export, import/export planning, or reviewed write workflows.
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.
Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions, communicating breaking changes, or creating upgrade guides.
Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals. Use PROACTIVELY for API documentation or developer portal creation.
Analyze fundamental data primitives, type systems, and state management patterns in a codebase. Use when (1) evaluating typing strategies (Pydantic vs TypedDict vs loose dicts), (2) assessing immutability and mutation patterns, (3) understanding serialization approaches, (4) documenting state shape and lifecycle, or (5) comparing data modeling approaches across frameworks.
Take microsoft/power-platform-add-sharepoint from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npx.
Without those the skill loads but fails at the first command.