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.

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 ./skills/monday-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Scale 1-5

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, well-organized skill that covers Monday.com automation comprehensively with clear tool sequences and specific parameter guidance. Its main weaknesses are repetition across sections (pitfalls are stated multiple times), lack of concrete executable examples showing full tool invocations, and a monolithic structure that could benefit from splitting reference material into separate files. The workflow annotations (Prerequisite/Required/Optional) are a notable strength.

Suggestions

Consolidate repeated pitfalls — remove per-workflow pitfall sections and keep only the 'Known Pitfalls' section, or vice versa, to reduce redundancy by ~30%

Add at least one fully concrete end-to-end example showing actual tool call parameters (e.g., creating a board with specific columns and adding an item with column values)

Add verification steps after create/update operations (e.g., 'Verify: call MONDAY_LIST_BOARD_ITEMS to confirm the item was created with correct column values')

Extract the Quick Reference table and Column Value Formatting section into a separate REFERENCE.md file to improve progressive disclosure

DimensionReasoningScore

Conciseness

The skill is comprehensive but notably verbose for Claude. There's significant repetition across sections (e.g., pitfalls about column IDs, ID formats, and parameter details are restated multiple times). The 'Known Pitfalls' section largely repeats information already covered in per-workflow pitfalls. The quick reference table adds value but the overall document could be tightened by ~30%.

3 / 5

Actionability

The skill provides concrete tool sequences, specific parameter names, exact value format examples (e.g., status JSON, date JSON, people JSON), and a comprehensive quick reference table. However, it lacks fully executable end-to-end examples showing actual tool calls with realistic parameters — the guidance is specific but presented as descriptions rather than copy-paste-ready invocations.

4 / 5

Workflow Clarity

Each workflow has a clear numbered sequence with prerequisite/required/optional annotations, which is excellent. However, there are no explicit validation or verification steps — for example, after creating a board or item, there's no step to verify the creation succeeded. The ID resolution pattern is well-documented. The lack of error recovery steps (what to do if a tool call fails) prevents a score of 5.

4 / 5

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's a monolithic ~250-line document with no bundle files. The 'Common Patterns', 'Known Pitfalls', and per-workflow pitfalls sections contain significant overlap that could be consolidated or split into reference files. For a skill of this complexity, some content (like the full column value formatting reference or the quick reference table) would benefit from being in separate files.

3 / 5

Total

14

/

20

Passed

Description

70%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 effectively identifies the specific platform (Monday.com) and lists the key entities it can manage, making it distinctive and reasonably specific. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The description also lists objects rather than concrete actions (e.g., 'create', 'update', 'delete').

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Monday.com, managing boards, tracking tasks, or project management workflows.'

Replace the object list with action-oriented phrases, e.g., 'Create and manage boards, add/update items, configure columns, organize groups, track subitems, and post updates.'

DimensionReasoningScore

Specificity

Lists several specific entities (boards, items, columns, groups, subitems, updates) and names the domain (Monday.com work management) and the integration mechanism (Rube MCP/Composio). However, it doesn't describe specific actions like 'create boards', 'update items', 'add columns' — it just lists the objects.

4 / 5

Completeness

The 'what' is reasonably clear (automate Monday.com work management across various entities), but there is no explicit 'Use when...' clause. The instruction to 'always search tools first' is operational guidance, not a trigger condition. Per rubric guidelines, missing 'Use when' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'Monday.com', 'boards', 'items', 'columns', 'groups', 'subitems', 'updates', and 'work management'. Missing some natural user phrases like 'task tracking', 'project management', 'monday board', or 'create a board'.

4 / 5

Distinctiveness Conflict Risk

Monday.com is a very specific platform, and the description names it explicitly along with platform-specific terminology (boards, subitems, groups) and the integration method (Rube MCP/Composio). This creates a clear niche with minimal conflict risk.

5 / 5

Total

16

/

20

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
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.