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.
- License 许可
- MIT
- 最近更新
- 2026-07-19
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- sharepoint-shared-doc-maintenance
- description
- 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.
02 资源文件 1
- 参考文档agents/openai.yaml279 B
03 SKILL.md 正文
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
- Identify the maintained document.
- Identify the likely source documents that feed it.
- Compare timestamps so you know which sources changed after the maintained document's last update.
- Fetch only the maintained document plus the changed source docs.
- Extract the concrete delta:
- timeline shifts
- milestone changes
- new risks
- updated owners
- revised launch dates
- removed commitments
- Decide whether the maintained document needs:
- no change
- a targeted insertion
- a broader section rewrite
- Apply the smallest edit that fully propagates the source change.
- 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.
04 同仓库更多 Skills
Zotero
Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.
zoom-apps-sdk
Use when using Apps SDK.
youtube
Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.
x-post-creator
Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.
x-api
Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".