CtrlK
BlogDocsLog inGet started
Tessl Logo

sharepoint-site-discovery

Resolve the right SharePoint site, library, and folder before file work. Use when the user needs to find the right site context, browse a known site, inspect document libraries, or narrow the correct folder before fetching or editing a file.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%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 concise and actionable with concrete tool-call signatures and a well-organized section structure. The main weakness is workflow_clarity: validation and error-recovery checkpoints are implicit rather than explicit.

Suggestions

Add an explicit validation/branching checkpoint in the workflow for when get_site returns no match or list_site_drives yields ambiguous candidates (e.g., 'if no site matches the hostname, ask the user to confirm the hostname before proceeding').

Specify the recovery loop for keyword search that returns too many results (e.g., 'if search(query="...") returns more than N hits, narrow by adding hostname/site_path and re-run') so the feedback path is explicit rather than implied.

Clarify the validation step when a browse result has zero children (e.g., confirm the folder_path is empty vs. mis-specified) to give the discovery loop a concrete retry condition.

DimensionReasoningScore

Conciseness

Lean procedural guidance with no concept-explanation padding (no "what is SharePoint" filler); every line earns its place and assumes Claude's competence.

3 / 3

Actionability

Gives concrete tool-call signatures with arguments—search(query="..."), search(query=None, hostname=..., site_path=..., folder_path=...), get_site(...), list_site_drives(...)—so Claude knows exactly which tool and parameters to invoke.

3 / 3

Workflow Clarity

A clear six-step sequenced workflow is present, but validation/retry checkpoints are only implicit (e.g., what to do when get_site finds no match or a drive listing is ambiguous), which matches the "steps listed but checkpoints missing or implicit" anchor.

2 / 3

Progressive Disclosure

No bundle files are needed; the body is under 50 lines and well-organized into Start Here, Workflow, Output Conventions, and Example Requests sections, satisfying the simple-skill exception for a top score.

3 / 3

Total

11

/

12

Passed

Description

100%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 is specific, uses natural trigger terms, and clearly states both capability and invocation conditions in third person. It carves a distinct niche unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—"Resolve the right SharePoint site, library, and folder", "browse a known site", "inspect document libraries", "narrow the correct folder before fetching or editing a file"—rather than vague language.

3 / 3

Completeness

Explicitly answers both what ("Resolve the right SharePoint site, library, and folder before file work") and when ("Use when the user needs to find the right site context, browse a known site, inspect document libraries, or narrow the correct folder...").

3 / 3

Trigger Term Quality

Covers natural user-facing terms—"site", "library", "folder", "document libraries", "browse", "fetch", "edit"—that a user would plausibly say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

Carves a clear niche—SharePoint site/library/folder discovery prior to file work—with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.