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.
Best use case
sharepoint-shared-doc-maintenance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using sharepoint-shared-doc-maintenance 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-shared-doc-maintenance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sharepoint-shared-doc-maintenance Compares
| Feature / Agent | sharepoint-shared-doc-maintenance | 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?
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.
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 Shared Doc Maintenance ## Overview Use this skill when the job is not just editing one document, but keeping a maintained shared document aligned with newer source documents. Optimize for finding the real delta and applying the smallest necessary patch. ## Core Workflow 1. Identify the maintained document. 2. Identify the likely source documents that feed it. 3. Compare timestamps so you know which sources changed after the maintained document's last update. 4. Fetch only the maintained document plus the changed source docs. 5. Extract the concrete delta: - timeline shifts - milestone changes - new risks - updated owners - revised launch dates - removed commitments 6. Decide whether the maintained document needs: - no change - a targeted insertion - a broader section rewrite 7. Apply the smallest edit that fully propagates the source change. 8. Re-fetch and verify that the maintained document now reflects the new source-of-truth details in the right section. ## Synthesis Rules - Treat maintenance as a distinct workflow, not as generic document summarization. - For roadmap and milestone maintenance, prefer concrete propagation over broad re-summarization. - Use modification timestamps as a triage tool, not as proof of substantive change. - For multi-document synthesis requests, verify the source set before writing. If the user asks for a consolidated strategy or a summary of all related materials, enumerate the source documents explicitly and verify that likely variants were not skipped. - Even if you expect only one source to have changed, enumerate the source set so you do not miss a second updated input. ## Verification - Verification should confirm both the new fact and its placement in the document. - Do not stop at proving a changed year, date, or milestone appears somewhere. Confirm it appears in the roadmap, recommendations, timing discussion, or risk framing where readers would expect it. - If the maintained document is already on a low-fidelity fallback format because of connector limits, favor precise content patches over broad structural rewrites. ## Recovery Notes - Optimize for quick triage: - list likely source docs once - use modification times to narrow the fetch set - fetch only the maintained doc plus changed sources - extract the exact delta before editing - avoid rewriting unaffected sections - If a changed source contains a strong explicit marker such as `UPDATE`, `TIMELINE CHANGED`, revised year ranges, or renamed milestones, treat that as a high-confidence propagation target.
Related Skills
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-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.
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-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.
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.
vercel-queues
Vercel Queues guidance (public beta) — durable event streaming with topics, consumer groups, retries, and delayed delivery. $0.60/1M ops. Powers Workflow DevKit. Use when building async processing, fan-out patterns, or event-driven architectures.
vercel-functions
Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.