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. Its main weaknesses are the lack of an explicit 'Use when...' clause and missing common user-facing trigger terms beyond the technical Monday.com vocabulary. Adding trigger guidance and natural language variations would make this description more effective for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Monday.com, managing project boards, tracking tasks, or automating work management workflows.'
Include natural language trigger terms users might say, such as 'project management', 'task tracking', 'Monday board', or 'work management tool'.
| 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. The 'when' is only implied by the mention of Monday.com, which caps this at 2 per the rubric guidelines. | 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 common user phrasings like 'project management', 'task tracking', 'work items', or 'Monday board' variations that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Monday.com' and 'Rube MCP (Composio)'. This is unlikely to conflict with other skills as it targets a very specific platform and integration method. | 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-organized skill with clear workflow sequences and good structural patterns (ID resolution, pagination, column formatting). Its main weaknesses are verbosity through repetition of pitfalls across sections, lack of concrete executable examples showing actual tool invocations, and all content being inline rather than using progressive disclosure to separate reference material from core workflows.
Suggestions
Add 1-2 concrete tool invocation examples showing exact parameters (e.g., a complete MONDAY_CREATE_ITEM call with column_values JSON) to improve actionability
Consolidate duplicated pitfalls — remove per-workflow pitfall entries that are already covered in the 'Known Pitfalls' section to reduce token count by ~30%
Move the Quick Reference table and Column Value Formatting section to a separate REFERENCE.md file, linking from the main skill to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but verbose for its purpose. There's significant repetition across sections — pitfalls about column IDs, ID formats, and parameter quirks are restated multiple times. The 'Known Pitfalls' section largely duplicates information already covered in per-workflow pitfalls. However, it doesn't explain basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and value format examples (e.g., status JSON, date JSON), which is good. However, there are no executable code examples or copy-paste ready tool invocations — everything is described rather than demonstrated with concrete tool call examples showing exact input/output. | 2 / 3 |
Workflow Clarity | Each workflow has a clear numbered sequence with labeled steps (Prerequisite, Required, Optional), explicit tool ordering, and 'When to use' context. The setup section includes a verification step before proceeding. The ID resolution pattern and pagination handling provide good guidance for error-prone operations. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a monolithic document (~250 lines) with no references to external files for detailed content. The column value formatting, pagination details, and per-workflow pitfalls could be split into separate reference files to keep the main skill leaner. | 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
7cc63f3
- 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.