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.

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/one-drive-automation/SKILL.md

The canonical home for this skill is one-drive-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 content is well-organized and actionable with strong tool sequences and a useful quick reference, but it is hurt by duplicated pitfalls, implicit validation in destructive workflows, and a monolithic structure with no reference files. Splitting reference material and adding explicit validation checkpoints would meaningfully raise the score.

Suggestions

Add explicit validation checkpoints for destructive/batch workflows (e.g., verify item_id and confirm with the user before DELETE/permission changes, then re-check permissions after).

Move the full Quick Reference table and detailed pitfalls into a separate references/ file, keeping SKILL.md as a concise overview with one-level-deep links.

De-duplicate the "Known Pitfalls" section against the per-workflow "Pitfalls" blocks to remove repeated guidance and reclaim tokens.

DimensionReasoningScore

Conciseness

The body is mostly efficient and tool-focused with little concept over-explanation, but the "Known Pitfalls" section substantially duplicates pitfalls already listed under each workflow, adding tokens that could be trimmed.

3 / 5

Actionability

Concrete tool slugs, key parameters, and a Quick Reference table give mostly executable guidance for an MCP-tool skill; minor gaps are the absence of worked end-to-end examples for the common cases.

4 / 5

Workflow Clarity

Each workflow has a clear numbered tool sequence and "When to use", but destructive/batch operations (delete, permission grants, copy) lack explicit validate→fix→retry checkpoints; validation is only implicitly mentioned, capping the score at 3.

3 / 5

Progressive Disclosure

The single 240+ line SKILL.md inlines the full API reference, pitfalls, and quick-reference table that could live in separate reference files; no bundle/reference files exist, so structure is section-based rather than file-based.

3 / 5

Total

13

/

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 distinctive with comprehensive action coverage, but it lacks an explicit "when to use" trigger clause, which limits its completeness. Adding a natural trigger phrase would raise the completeness and trigger-term scores.

Suggestions

Add an explicit "Use when..." clause naming natural triggers (e.g., "Use when managing, searching, sharing, or syncing files in OneDrive").

Include common synonyms/file extensions users say (e.g., "OneDrive files", ".docx/.xlsx uploads", "shared links") to improve trigger-term coverage.

Keep the existing action list but pair it with the trigger phrase so both 'what' and 'when' are explicit.

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 description states clearly what the skill does but contains no "Use when..." trigger clause; "Always search tools first for current schemas" is a process note, not a when-to-use trigger, which caps completeness at 3.

3 / 5

Trigger Term Quality

"OneDrive" is a strong natural keyword and the operation terms are relevant, but common synonyms and file extensions are absent, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"OneDrive ... via Rube MCP (Composio)" carves a clear niche with distinct triggers and minimal overlap risk 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.