sharepoint-word-docs
Edit SharePoint-hosted Word `.docx` files while preserving document structure and styling. Use when the user wants to update a real Word document in SharePoint rather than summarize it as plain text.
Best use case
sharepoint-word-docs is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Edit SharePoint-hosted Word `.docx` files while preserving document structure and styling. Use when the user wants to update a real Word document in SharePoint rather than summarize it as plain text.
Teams using sharepoint-word-docs should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sharepoint-word-docs/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sharepoint-word-docs Compares
| Feature / Agent | sharepoint-word-docs | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Edit SharePoint-hosted Word `.docx` files while preserving document structure and styling. Use when the user wants to update a real Word document in SharePoint rather than summarize it as plain text.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SharePoint Word Docs ## Overview Use this skill for `.docx` edits that start from SharePoint. Treat the file as a real Word package, not as extracted text, and preserve the existing document structure and styling unless the user explicitly accepts formatting loss. ## Core Workflow 1. Search for the file and identify the exact target by title, path, and file type. 2. Fetch extracted text once to verify it is the right document and to locate the target section. 3. Fetch the raw `.docx` with `fetch(download_raw_file=true)` before editing. 4. Edit locally with `python-docx` or equivalent OOXML-aware local tooling so the original Word package remains intact. 5. Ensure that the upload path can preserve a normal styled Word package before overwriting the original. 6. Write the revised file back with `update_file` using the exact drive-root-relative path from SharePoint metadata. 7. Re-fetch and verify both: - the intended text or section change - the expected structure or styling when possible ## Safety - Do not replace a styled `.docx` with plain text output. - Do not replace a styled `.docx` with a minimal regenerated package merely to make upload succeed unless formatting loss is already acceptable from the request context. - Treat inline base64 binary upload as potentially brittle for richer `.docx` packages. If the write path looks unsafe, stop and explain the formatting risk rather than silently degrading the file. - If the first overwrite attempt returns `itemNotFound`, inspect the folder items and use the exact root-relative path from SharePoint metadata. ## Verification - Content verification alone is not enough for existing styled documents. - Check heading structure, spacing, and style preservation when possible. - If you can only validate text content, say so explicitly and note the remaining formatting risk.
Related Skills
geistdocs
Expert guidance for Geistdocs, Vercel's documentation template built with Next.js and Fumadocs — MDX authoring, configuration, AI chat, i18n, feedback, deployment. Use when creating documentation sites, configuring geistdocs, writing MDX content, or setting up docs infrastructure.
sharepoint
Inspect Microsoft SharePoint context and prepare safe changes. Use when the user wants site, page, or file review, ownership and status extraction, or change planning before editing content, navigation, or information architecture.
sharepoint-spreadsheets
Edit SharePoint-hosted spreadsheet files while preserving workbook structure, formulas, and formatting. Use when the user wants to update a real spreadsheet in SharePoint rather than summarize extracted sheet text.
sharepoint-spreadsheet-formula-builder
Design, repair, and roll out formulas in SharePoint-hosted workbooks with connector-aware retrieval, validation, and upload discipline. Use when the user wants to add a formula column, fix a broken formula, choose between a fill-down formula and a spill formula, build a lookup or filter formula, or reuse workbook logic safely.
sharepoint-shared-doc-maintenance
Maintain shared SharePoint strategy, roadmap, planning, or status documents from changing source documents. Use when the user wants cross-document synthesis, source-of-truth propagation, or targeted updates to a maintained shared document.
sharepoint-powerpoint
Create, edit, restyle, and review PowerPoint `.pptx` files fetched from SharePoint, with emphasis on style preservation, slide cloning, theme-aware updates, and rendered visual QA. Use when the user wants reliable slide edits that should match an existing deck's design language.
google-docs
Inspect and edit Google Docs documents with index-aware batch updates. Use when the user wants to read document text or structure, find paragraph indexes, rewrite sections in place, edit tables, or apply style-aware document changes with Google Docs tools.
workflow
Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.
vercel-sandbox
Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.