Name: microsoft-sharepoint
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

microsoft-sharepoint

Microsoft Sharepoint integration. Manage Sites. Use when the user wants to interact with Microsoft Sharepoint data.

Quality

59%

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 ./skills/microsoft-sharepoint/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

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

The body is highly actionable with concrete CLI commands and a well-structured connection workflow. It loses points for an unnecessary concept-explaining intro, an unverified destructive-action path, and a large inline action table.

Suggestions

Trim the opening SharePoint explainer paragraph; assume Claude knows what SharePoint is and lead directly with the integration workflow.

Add a verification/confirmation checkpoint before destructive actions (e.g., confirm the target drive item or list item before running delete-drive-item/delete-list-item).

Consider moving the large popular-actions table into a referenced file (e.g., ACTIONS.md) and summarizing the key categories inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what SharePoint is ("a web-based collaboration and document management platform... Think of it as a central repository"), a concept Claude already knows; the remainder is mostly tight command examples, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the minor-trim 4-anchor.	3 / 5
Actionability	Provides concrete copy-paste commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a keyed actions table, matching the 'mostly executable guidance with minor gaps' anchor; minor gaps are placeholder values and the vague line "Use action names and parameters as needed."	4 / 5
Workflow Clarity	The connection workflow has clear sequencing with validation (poll until READY, handle CLIENT_ACTION_REQUIRED, check error fields), but the skill covers destructive operations (delete-drive-item, delete-list-item) with no verification step before running them, which caps workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no external references, which is appropriate for this integration skill; the large inline popular-actions table is a minor organization gap that keeps it at 4 rather than 5.	4 / 5
	Total	14 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 correctly answers both what the skill does and when to use it in third person, with a distinct SharePoint niche. Its main weakness is thin action specificity and limited trigger-term coverage.

Suggestions

Replace the generic "Manage Sites" with several concrete actions (e.g., list/create sites, lists, list items, drives, and files) to lift specificity.

Expand trigger terms to include natural synonyms users say such as SharePoint lists, document libraries, files, and folders.

Tighten the "Use when" clause with concrete trigger phrases (e.g., "Use when the user wants to manage SharePoint sites, lists, files, or document libraries").

Dimension	Reasoning	Score
Specificity	"Manage Sites" is the only action named and it is generic; this matches the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	States a clear "what" ("Microsoft Sharepoint integration. Manage Sites.") and an explicit "Use when" trigger ("Use when the user wants to interact with Microsoft Sharepoint data"), but the trigger could be more specific, fitting the 4-anchor rather than 5.	4 / 5
Trigger Term Quality	Includes "Microsoft Sharepoint", "Sites", and "Sharepoint data" but omits common synonyms users would say such as lists, files, document libraries, or documents, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	SharePoint is a distinct niche with a clear trigger phrase and low conflict risk, but the generic "interact with Microsoft Sharepoint data" wording leaves minor overlap risk versus a 5-anchor with distinct, comprehensive triggers.	4 / 5
	Total	13 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/microsoft-sharepoint/SKILL.md
Commit: f484c82

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