sharepoint

Inspect Microsoft SharePoint context, discover the right site or library, 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.

Quality

88%

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

Quality

Content

85%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.

A well-structured, highly actionable orchestrator skill with strong workflow sequencing and explicit verification checkpoints. Its main weakness is redundancy: routing and discovery guidance are restated across the table, the workflow list, and the Write Safety section.

Suggestions

Collapse the duplicate routing: keep the "Workflow Skills" table as the single source of routing truth and prune the overlapping re-routing in workflow rules 8/9/10, or vice versa.

Dedupe the discovery guidance between workflow rule 4 and the "Write Safety" discovery bullet so the truthful get_site / list_site_drives / search(query=None) path appears once.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no concept-filler, but routing is duplicated across the "Workflow Skills" table and workflow rules 8/9/10, and discovery guidance repeats between rule 4 and the Write Safety section, so it "could be tightened" per the score-2 anchor rather than earning the score-3 lean/every-token-earns-its-place bar.	2 / 3
Actionability	Gives concrete, near copy-paste-ready guidance: named tools with argument signatures (get_site(...), search(query=None, hostname=..., site_path=..., folder_path=...), list_item_permissions, restore_item_version, move_items_bulk) and exact extension-to-skill routing, meeting the score-3 anchor for specific executable guidance.	3 / 3
Workflow Clarity	A clearly sequenced 17-step workflow with explicit validation checkpoints — re-fetch and verify after writes (step 12), split content vs fidelity verification (step 13), a discovery decision sequence (step 4), and recovery feedback loops (429 retry-once, base64 transport reassessment) — matching the score-3 anchor including feedback loops for risky write/batch operations.	3 / 3
Progressive Disclosure	The overview delegates detail to six specialized sibling skills via a labeled table and routing rules that are all one level deep and clearly signaled, and this skill's own bundle (only assets/ with two SVGs, no references/ or scripts/) is kept out of the inline overview, matching the score-3 anchor for a clear overview with well-signaled one-level navigation.	3 / 3
	Total	11 / 12 Passed

Description

92%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.

A strong, specific description with an explicit Use-when trigger and good natural-language coverage. The only weakness is conflict risk against its sibling SharePoint skills, which share most of the same trigger vocabulary.

Suggestions

Add a distinguishing qualifier to the Use-when clause (e.g. 'before editing content' / 'as the entry point for SharePoint review and edit planning') so the description does not collide with sibling sharepoint-* skills.

Signal that this skill routes to specialized sub-skills (Word/Excel/PowerPoint/site-discovery) to make its orchestrator role and non-overlap explicit.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Inspect Microsoft SharePoint context, discover the right site or library, and prepare safe changes" plus "ownership and status extraction, or change planning" — matching the score-3 anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (inspect/discover/prepare) and when via a clear "Use when the user wants site, page, or file review..." clause, satisfying the score-3 anchor and avoiding the score-2 cap for a missing Use-when trigger.	3 / 3
Trigger Term Quality	Covers natural user vocabulary — "site, page, or file review", "navigation", "information architecture", "ownership and status extraction" — giving good coverage of terms a user would actually say, above the score-2 "some keywords but missing variations" anchor.	3 / 3
Distinctiveness Conflict Risk	SharePoint-scoped niche is clear, but this is an orchestrator over six sibling sharepoint-* skills that share near-identical site/page/file/edit vocabulary, so it "could still overlap with similar skills" per the score-2 anchor rather than being cleanly non-conflicting.	2 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 12 suspicious	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/sharepoint/skills/sharepoint/SKILL.md
Commit: 11c74d6

Reviewed: 17 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.