monday-automation
Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.
75
65%
Does it follow best practices?
Impact
91%
3.03xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/monday-automation/SKILL.mdQuality
Discovery
67%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 strong in specificity and distinctiveness, clearly identifying Monday.com as the target platform and listing concrete entities it manages. However, it lacks an explicit 'Use when...' clause, which caps completeness, and could benefit from more natural trigger terms that users would actually say when requesting help with project/task management.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Monday.com boards, task management in Monday, or automating Monday.com workflows.'
Include natural user-facing trigger terms like 'project management', 'task tracking', 'Monday board', or 'work management tool' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete entities and actions: 'boards, items, columns, groups, subitems, and updates' along with the automation context via 'Rube MCP (Composio)'. Also includes the operational guidance to 'search tools first for current schemas.' | 3 / 3 |
Completeness | Clearly answers 'what' (automate Monday.com work management with specific entities), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill. The 'when' is only implied by the domain mention. | 2 / 3 |
Trigger Term Quality | Includes 'Monday.com' and domain-specific terms like 'boards, items, columns, groups, subitems, updates' which are relevant but somewhat technical. Missing natural user phrases like 'project management', 'task tracking', 'work items', or 'Monday board' that users might actually say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform reference 'Monday.com' and the tooling reference 'Rube MCP (Composio)'. Very unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%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 with clear workflow sequences and good coverage of Monday.com operations via Rube MCP. Its main weaknesses are redundancy across sections (pitfalls repeated in both workflow-specific and general sections) and the lack of concrete, copy-paste-ready tool invocation examples showing exact parameter payloads. The document would benefit from consolidating repeated information and adding at least one complete end-to-end example.
Suggestions
Add at least one complete, copy-paste-ready tool invocation example showing exact parameters (e.g., a full MONDAY_CREATE_ITEM call with column_values JSON) to improve actionability.
Consolidate pitfalls into a single section or remove duplicates from individual workflows to reduce redundancy and improve conciseness.
Consider extracting the column value formatting reference and quick reference table into a separate REFERENCE.md file to improve progressive disclosure for this complex skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some redundancy—pitfalls are repeated across sections (e.g., column_type snake_case, ID formats mentioned multiple times), and the 'Known Pitfalls' section largely restates what was already covered in individual workflow pitfalls. The quick reference table adds value but the overall document could be tightened significantly. | 2 / 3 |
Actionability | The skill provides concrete tool names, parameter specifications, and value format examples, which is good. However, it lacks executable code examples or copy-paste ready sequences—there are no actual tool invocation examples showing exact parameter payloads. The column value formatting section is helpful but would benefit from complete tool call examples. | 2 / 3 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with prerequisite/required/optional annotations, explicit ordering, and detailed pitfalls. The ID resolution pattern establishes a clear prerequisite chain. The setup section includes a verification step (confirm ACTIVE status before proceeding). Pagination handling includes cursor lifecycle details. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic document (~250 lines) with no references to supporting files. The detailed column value formatting, pagination patterns, and per-workflow pitfalls could be split into separate reference files. For a skill of this complexity, some progressive disclosure to external files would improve navigability. | 2 / 3 |
Total | 9 / 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 | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- 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.