CtrlK
BlogDocsLog inGet started
Tessl Logo

one-drive-automation

Automate OneDrive file management, search, uploads, downloads, sharing, permissions, and folder operations via Rube MCP (Composio). Always search tools first for current schemas.

77

1.70x
Quality

71%

Does it follow best practices?

Impact

85%

1.70x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/one-drive-automation/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-structured and highly actionable, with clear tool sequences and strong parameter/pitfall guidance for OneDrive operations. Its main weakness is redundancy between the per-workflow Pitfalls and the consolidated Known Pitfalls/Common Patterns sections.

Suggestions

Remove the duplicated 'Known Pitfalls' and 'Common Patterns' content that already appears in each workflow's Pitfalls subsection, or replace the per-workflow lists with a single canonical section.

Add explicit validate→fix→retry feedback loops for batch/destructive operations (e.g., after a copy operation, monitor the returned URL until completion; after a delete, confirm recycle-bin placement).

DimensionReasoningScore

Conciseness

Mostly efficient with no over-explanation of OneDrive concepts, but the 'Known Pitfalls' and 'Common Patterns' sections substantially duplicate pitfalls already stated per-workflow (KQL limits, drive_id overriding user_id, async copy, ID formats).

3 / 5

Actionability

Concrete tool slugs with [Prerequisite]/[Required]/[Optional] tags, named parameters with example values, and a Quick Reference table make the guidance mostly executable, though full call payloads are not shown.

4 / 5

Workflow Clarity

Numbered tool sequences with role tags are clear, and verification steps appear for risky operations (confirm ACTIVE connection, verify item_id before permission changes, get confirmation for write roles), though formal validate→fix→retry feedback loops are absent.

4 / 5

Progressive Disclosure

Single-file skill with well-organized sections (Prerequisites, Setup, Core Workflows, Common Patterns, Quick Reference) and clear navigation; no bundle files exist, and content is appropriately placed with only minor inlining of reference material.

4 / 5

Total

15

/

20

Passed

Description

75%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 is specific and clearly distinct, listing concrete OneDrive actions and the Rube MCP integration. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks to upload, download, search, share, or organize files in OneDrive.'

Include common synonyms or natural phrasings (e.g., 'OneDrive files', 'share a OneDrive file') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'file management, search, uploads, downloads, sharing, permissions, and folder operations' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The 'what' is clearly stated via the enumerated actions, but there is no explicit 'Use when...' trigger clause; per the judging guidelines a missing when-clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keywords ('OneDrive', 'search', 'uploads', 'downloads', 'sharing', 'permissions') that users would say, but missing common synonyms or file-extension variants.

4 / 5

Distinctiveness Conflict Risk

Scoped to 'OneDrive ... via Rube MCP (Composio)', a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.