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.
Install with Tessl CLI
npx tessl i github:Lingjie-chen/MT5 --skill one-drive-automation67
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 effectively lists specific OneDrive operations and identifies the integration platform, making it distinctive. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill. The trigger terms could also be expanded to include more natural user language variations.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when user mentions OneDrive, Microsoft cloud storage, or needs to share/sync files via OneDrive'
Include additional natural trigger terms users might say: 'cloud storage', 'share link', 'Microsoft OneDrive', 'sync', '.onedrive'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'file management, search, uploads, downloads, sharing, permissions, and folder operations'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The instruction 'Always search tools first' is implementation guidance, not usage triggers. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'OneDrive', 'uploads', 'downloads', 'sharing', 'permissions', but missing common user variations like 'cloud storage', 'sync files', 'share link', or 'Microsoft OneDrive'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to 'OneDrive' and 'Rube MCP (Composio)' which creates a distinct niche. Unlikely to conflict with generic file or other cloud storage skills due to explicit platform naming. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill document with excellent workflow clarity and progressive disclosure. The main weaknesses are moderate verbosity with some repeated information across sections, and the lack of concrete executable examples - the document describes what tools to use and their parameters but doesn't show actual code or JSON payloads that could be copy-pasted.
Suggestions
Add 1-2 concrete executable examples per workflow showing actual tool calls with sample JSON parameters (e.g., a complete RUBE_SEARCH_TOOLS call followed by ONE_DRIVE_SEARCH_ITEMS with real parameter values)
Consolidate the 'Known Pitfalls' section with workflow-specific pitfalls to reduce redundancy - either remove the summary section or remove inline pitfalls
Add a brief example showing the expected response format from key operations like search or file upload to help Claude parse results correctly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy, particularly in the 'Known Pitfalls' section which repeats information already covered in workflow-specific pitfalls. The quick reference table adds value but the overall document could be tightened. | 2 / 3 |
Actionability | Provides specific tool names and parameter lists, but lacks executable code examples. The tool sequences are clear but would benefit from concrete JSON/code snippets showing actual API calls with sample values. | 2 / 3 |
Workflow Clarity | Excellent workflow structure with clear numbered sequences, explicit prerequisites marked, required vs optional steps distinguished, and comprehensive pitfalls sections for each workflow. Validation steps are implicit through prerequisite checks. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from prerequisites to setup to core workflows to common patterns. External reference to Composio docs is appropriate. Quick reference table provides excellent navigation for common tasks. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.