CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

3.03x
Quality

58%

Does it follow best practices?

Impact

91%

3.03x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/monday-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid reference skill for Monday.com automation that covers the major workflows comprehensively with good structural organization and clear tool sequencing. Its main weaknesses are redundancy across sections (pitfalls repeated in both workflow-specific and general sections), lack of concrete executable examples showing full tool invocations with payloads, and missing validation/error-handling steps in workflows. The document would benefit from deduplication, adding copy-paste-ready tool call examples, and splitting detailed reference material into separate files.

Suggestions

Add at least one complete, copy-paste-ready tool invocation example per core workflow showing exact parameter payloads (e.g., a full MONDAY_CREATE_ITEM call with column_values JSON)

Add validation/verification steps to workflows — e.g., after creating an item, verify it appears in MONDAY_LIST_BOARD_ITEMS; after updating a column value, confirm the change took effect

Deduplicate pitfalls: consolidate the per-workflow pitfalls and the 'Known Pitfalls' section into a single reference, or keep only workflow-specific pitfalls inline and remove the general section

Consider splitting column value formatting reference and the quick reference table into a separate REFERENCE.md file to reduce the main skill's length

DimensionReasoningScore

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 by ~30%.

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

Multi-step workflows are clearly sequenced with labeled steps (Prerequisite, Required, Optional), which is well done. However, there are no explicit validation checkpoints or error recovery feedback loops — for example, after creating an item with column_values, there's no step to verify the values were set correctly, and no guidance on handling API errors or malformed column values.

2 / 3

Progressive Disclosure

The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic ~250-line document with no bundle files to offload detail into. The column value formatting, pagination patterns, and individual workflow details could be split into separate reference files. The single external link to Composio docs is appropriate but insufficient for the volume of content.

2 / 3

Total

8

/

12

Passed

Description

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 does a good job specifying concrete capabilities and the target platform (Monday.com), making it distinctive and specific. However, it lacks an explicit 'Use when...' clause that would help Claude know when to select this skill, and it could benefit from more natural trigger terms that users might actually say when requesting Monday.com automation help.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Monday.com, monday boards, project tracking, or task management on Monday.'

Include common user-facing trigger variations such as 'project management', 'task tracking', 'monday board', or 'work management platform' to improve matching against natural user requests.

DimensionReasoningScore

Specificity

Lists multiple specific concrete entities and actions: 'boards, items, columns, groups, subitems, and updates' along with the platform (Monday.com) and integration method (Rube MCP/Composio). Also includes a concrete procedural instruction to 'search tools first for current schemas.'

3 / 3

Completeness

The 'what' is well-covered (automate Monday.com work management across multiple entity types), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. The when is only implied by the domain mention.

2 / 3

Trigger Term Quality

Includes 'Monday.com', 'boards', 'items', 'columns', 'groups', 'subitems', and 'updates' which are relevant domain terms. However, it misses common user variations like 'monday board', 'task management', 'project management', 'work tracking', or casual phrases users might say when needing this skill.

2 / 3

Distinctiveness Conflict Risk

Monday.com is a very specific platform, and the description names the exact integration method (Rube MCP/Composio). This creates a clear niche that is unlikely to conflict with other skills unless there were multiple Monday.com skills.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

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.