CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 concise, well-sequenced instruction skill with explicit verification checkpoints and an error-recovery loop for a destructive document operation. Its one weakness is actionability: guidance cites specific APIs but lacks complete executable code examples and hedges the editing step.

Suggestions

Add a minimal copy-paste-ready python-docx snippet for the local edit step so the core action is fully executable rather than described.

Replace the 'or equivalent OOXML-aware local tooling' hedge with a concrete default (python-docx) and move alternatives to a brief parenthetical, keeping the primary path unambiguous.

Show the exact fetch and update_file call signatures (e.g., the drive-root-relative path argument) as a short example pair to make upload guidance copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: it never explains what SharePoint/Word/python-docx are, and the workflow, safety, and verification sections each carry only load-bearing detail, so every token earns its place.

3 / 3

Actionability

It names concrete tool calls with parameters ('fetch(download_raw_file=true)', 'update_file', 'python-docx') but provides no complete executable code block, and 'or equivalent OOXML-aware local tooling' hedges the key editing step.

2 / 3

Workflow Clarity

A clear 7-step sequence with an explicit verify step (step 7 re-fetch and verify text + structure) and an error-recovery feedback loop ('If the first overwrite attempt returns itemNotFound, inspect the folder items and use the exact root-relative path'), matching the anchor for explicit validation and feedback loops.

3 / 3

Progressive Disclosure

Under 50 lines with no bundle files and no need for external references, yet well-organized into Overview, Core Workflow, Safety, and Verification sections — meeting the rubric's allowance for simple skills to score 3 on clean organization alone.

3 / 3

Total

11

/

12

Passed

Description

90%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 focused, well-structured description that answers both what it does and when to use it in third person, with natural trigger terms and low conflict risk. The only minor weakness is specificity, since it centers on a single editing action rather than enumerating several distinct capabilities.

DimensionReasoningScore

Specificity

Names a concrete domain ('SharePoint-hosted Word `.docx` files') and a main action ('Edit...preserving document structure and styling'), but it lists one primary action rather than multiple distinct concrete actions like the anchor-3 example.

2 / 3

Completeness

Clearly states what it does ('Edit SharePoint-hosted Word `.docx` files while preserving document structure and styling') and gives an explicit 'Use when the user wants to update a real Word document in SharePoint...' trigger, satisfying both halves.

3 / 3

Trigger Term Quality

Uses natural terms a user would say — 'Word document', 'SharePoint', '`.docx`', 'update' — with good coverage across the 'what' and 'Use when' clauses.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and explicit (SharePoint-hosted Word `.docx` edits), with a distinguishing contrast against plain-text summarization, making it unlikely to trigger the wrong skill.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.