Name: onedrive
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

onedrive

MS OneDrive integration. Manage Accounts. Use when the user wants to interact with MS OneDrive data.

Quality

62%

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/onedrive/SKILL.md

Quality

Content

67%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 clear connection workflow including state checkpoints. It loses points mainly for an unnecessary introductory explanation of OneDrive and a monolithic single-file structure.

Suggestions

Remove the introductory 'MS OneDrive is a cloud storage service...' paragraph since Claude already knows what OneDrive is.

Move the full popular-actions table and proxy flag reference into a separate reference file, keeping only a quick-start subset inline.

Add at least one fully-worked end-to-end example (real connection id, action, and JSON input/output) to lift actionability to 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but the opening paragraph explaining what OneDrive is ('cloud storage service provided by Microsoft...') is unnecessary padding Claude already knows.	3 / 5
Actionability	Concrete, executable membrane commands with flags throughout and a popular-actions table, but invocations rely on placeholders (<actionId>, CONNECTION_ID, QUERY) with no fully-worked end-to-end example with real values.	4 / 5
Workflow Clarity	Clear install→auth→connect→search→run sequence with state-based polling checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), though not a tight validate→fix→retry feedback loop.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references, but all content (including the long popular-actions table and proxy flag table) is inlined in a single file over 50 lines with no reference split.	4 / 5
	Total	15 / 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 cleanly states a domain and an explicit use-trigger, with a distinctive product name. Its main weakness is the generic, minimal action phrasing ('Manage Accounts') and limited trigger-term coverage.

Suggestions

Replace 'Manage Accounts' with concrete actions users perform, e.g. 'Upload, search, move, share, and delete files and folders in OneDrive'.

Expand trigger terms to include natural phrases like 'OneDrive files', 'shared files', 'sync', or specific intents users would say.

Keep the 'Use when...' clause but tie it to concrete scenarios (uploading, sharing, finding files) for a 5-level completeness.

Dimension	Reasoning	Score
Specificity	Names the OneDrive domain but the only action ('Manage Accounts') is generic and minimal, matching the 'names the domain but actions are minimal or generic' anchor rather than the 3-anchor's concrete 1-2 actions.	2 / 5
Completeness	It has both a 'what' ('MS OneDrive integration. Manage Accounts.') and an explicit 'when' ('Use when the user wants to interact with MS OneDrive data.'), but the 'what' is less specific than a 5-anchor example.	4 / 5
Trigger Term Quality	'MS OneDrive' is a strong natural keyword and 'Use when the user wants to interact with MS OneDrive data' gives a trigger, but common variations (files, folders, sharing, sync) are missing.	3 / 5
Distinctiveness Conflict Risk	'MS OneDrive' is a distinct branded niche with low conflict risk, though there is minor overlap with general cloud-storage/file-management skills.	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/onedrive/SKILL.md
Commit: f484c82

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