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.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/sharepoint/skills/sharepoint-shared-doc-maintenance/SKILL.md

Quality

Content

70%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clear, validated workflow and appropriate organization for a compact instruction-only skill. Its main weaknesses are mild redundancy in Recovery Notes and the absence of concrete, executable SharePoint-specific commands.

Suggestions

Tighten or differentiate the Recovery Notes section so it does not repeat the Core Workflow steps verbatim; keep only the genuinely new guidance (e.g., the high-confidence marker handling).

Add at least one concrete, executable example of the fetch/delta/patch operation, such as a sample SharePoint Graph API call or a concrete before/after delta patch, to lift actionability.

Name the specific mechanism used to fetch and edit the maintained document (e.g., Graph API, file connector) so the workflow is reproducible rather than conceptual.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts Claude already knows, but the Recovery Notes section largely restates steps already covered in Core Workflow, which could be tightened.	2 / 3
Actionability	It gives a clear procedure with specific delta categories (timeline shifts, milestone changes, new risks, updated owners) and decision branches, but provides no concrete executable commands or tool invocations for the SharePoint context, leaving the guidance conceptual.	2 / 3
Workflow Clarity	An explicit 8-step sequence is present with a validation checkpoint (step 8: re-fetch and verify) and a dedicated Verification section confirming both the new fact and its placement, matching the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	The skill is roughly 50 lines with no need for external references and is organized into clear, well-labeled sections (Overview, Core Workflow, Synthesis Rules, Verification, Recovery Notes), satisfying the simple-skill allowance for a top score.	3 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly answers both what the skill does and when to use it, with an explicit trigger clause. It is held back from the top level by somewhat abstract action phrasing and a few technical trigger terms that users may not naturally say.

Suggestions

Replace technical phrasing like "source-of-truth propagation" and "cross-document synthesis" with natural user-facing terms such as "keep a shared document in sync" or "update one document from changed source files".

List a couple more concrete actions (e.g., "propagate shifted milestones, updated owners, and revised launch dates into a maintained roadmap") to reach the multi-action specificity anchor.

Add common trigger variations users would actually say, such as "update my SharePoint strategy doc" or "sync the roadmap with new source files".

Dimension	Reasoning	Score
Specificity	It names the domain (SharePoint strategy/roadmap/planning/status docs) and a concrete action ("Maintain...from changing source documents") but does not enumerate multiple distinct concrete actions the way the anchor-3 example does.	2 / 3
Completeness	It explicitly states what the skill does (maintain shared SharePoint documents from changing sources) and provides an explicit "Use when the user wants..." trigger clause, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural terms like SharePoint, roadmap, strategy, status documents, and targeted updates are present, but phrases such as "source-of-truth propagation" and "cross-document synthesis" lean technical and common variations are underrepresented.	2 / 3
Distinctiveness Conflict Risk	The SharePoint-maintained-document framing is a recognizable niche, but "cross-document synthesis" and general document maintenance could still overlap with broader document or summarization skills.	2 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/plugins
Path: plugins/sharepoint/skills/sharepoint-shared-doc-maintenance/SKILL.md
Commit: 11c74d6

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.