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.

80

3.03x
Quality

Does it follow best practices?

Impact

91%

3.03x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable and well-structured with clear tool sequences, but it is monolithic with some redundancy across sections and lacks explicit validation feedback loops for destructive operations.

Suggestions

Consolidate pitfalls and column-value formatting into a single location and cross-reference from workflows to remove the duplication and improve conciseness.

Add explicit validation checkpoints to destructive workflows (e.g., verify the created board ID is returned before adding columns) to lift workflow clarity to 3.

Move the detailed column-value-format reference and quick-reference table into separate reference files (e.g., COLUMN_FORMATS.md, TOOL_REFERENCE.md) and link to them from SKILL.md for better progressive disclosure.

DimensionReasoningScore

Conciseness

The body is dense and avoids explaining concepts Claude already knows, but pitfalls and column-value formats are restated across per-workflow sections and the consolidated 'Known Pitfalls'/'Column Value Formatting' sections, so it could be tightened.

2 / 3

Actionability

Concrete tool slugs, exact parameter names, and precise value formats (e.g. '{"personsAndTeams": [{"id": 123, "kind": "person"}]}') plus a task-to-tool quick-reference table give copy-ready, actionable guidance.

3 / 3

Workflow Clarity

Workflows are clearly sequenced with Prerequisite/Required/Optional labels, but destructive create/update/delete operations lack explicit validate-then-proceed feedback loops beyond the initial connection check, capping workflow clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

The skill is a single ~240-line file with no bundle references; while sections are well-organized, inline reference material (column-value formats, the full quick-reference table) could be split into one-level-deep files rather than kept monolithic.

2 / 3

Total

9

/

12

Passed

Description

82%

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 specific and clearly scoped to Monday.com automation, but it omits an explicit 'Use when...' usage trigger, capping completeness at 2.

Suggestions

Add a 'Use when...' clause (e.g., 'Use when automating Monday.com boards, tasks, items, or work-item workflows') to make the trigger explicit and lift completeness to 3.

Include a few common user phrasings such as 'tasks' or 'Monday boards' alongside the existing object names to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Enumerates six concrete capabilities ('boards, items, columns, groups, subitems, and updates') rather than vague abstractions, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2; 'Always search tools first' is a behavior instruction, not a usage trigger.

2 / 3

Trigger Term Quality

Natural Monday.com vocabulary ('boards', 'items', 'work management') covers the terms a user would actually say when requesting this skill.

3 / 3

Distinctiveness Conflict Risk

The Monday.com-via-Rube-MCP/Composio niche is sharply scoped with domain-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.