CtrlK
BlogDocsLog inGet started
Tessl Logo

affinity-automation

Automate Affinity tasks via Rube MCP (Composio). Always search tools first for current schemas.

66

6.23x
Quality

55%

Does it follow best practices?

Impact

81%

6.23x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./composio-skills/affinity-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-5

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

The body is a well-structured, single-file skill with concrete tool-call examples and a clear setup workflow, but it is held back by repeated directives, placeholder arguments in the execute step, and a missing error-recovery loop for batch tool execution.

Suggestions

Add an explicit error-recovery step after RUBE_MULTI_EXECUTE_TOOL (inspect error response, adjust arguments per schema, re-run) to provide the validation feedback loop batch execution requires.

Replace the '/* schema-compliant args from search results */' placeholder in Step 3 with a concrete minimal example argument block so the execute call is copy-paste ready.

De-duplicate the 'always search first' guidance to a single canonical location (e.g., Tool Discovery or Known Pitfalls) to tighten the token budget.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete tool blocks, but the 'always search first' directive is repeated in Prerequisites, Tool Discovery, the workflow, and Known Pitfalls, which is redundant padding; this fits the 3-anchor (mostly efficient with some unnecessary repetition) better than 4.

3 / 5

Actionability

Tool calls are concrete with real tool names and field names (queries, session, toolkits, memory), but Step 3 leaves arguments as '/* schema-compliant args from search results */' and uses placeholders like TOOL_SLUG_FROM_SEARCH and your_session_id, so it is mostly-executable with minor gaps rather than copy-paste ready.

4 / 5

Workflow Clarity

The Setup and Core Workflow give a clear sequence with connection-status checkpoints, but RUBE_MULTI_EXECUTE_TOOL performs batch tool execution without an error-recovery feedback loop for execution failures, and the rubric caps batch-operation skills lacking validation at 3.

3 / 5

Progressive Disclosure

No bundle files exist, so this is a single-file skill under 50 lines with well-organized sections (Prerequisites, Setup, Tool Discovery, Core Workflow, Pitfalls, Quick Reference), which meets the simple-skill exception for a 5.

5 / 5

Total

15

/

20

Passed

Description

46%Weight 40%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 clearly names its niche (Affinity automation via Rube MCP/Composio) and a process directive, but lacks a "Use when..." trigger clause and natural user-facing keywords, relying on technical jargon instead.

Suggestions

Add an explicit 'when' clause, e.g. 'Use when the user wants to automate Affinity CRM tasks like creating or updating contacts, organizations, deals, and list entries.'

Replace jargon-only triggers with natural user phrases ('Affinity CRM', 'Affinity lists', 'Affinity deals') so the description matches language a user would actually say.

Enumerate 2-3 concrete Affinity operations instead of the generic 'tasks' to lift specificity from domain-plus-one-action to several-specific-actions.

DimensionReasoningScore

Specificity

"Automate Affinity tasks via Rube MCP" names the domain plus one concrete action (automate), but "tasks" is generic and no specific Affinity operations (lists, deals, contacts) are enumerated, so it matches the 3-anchor (1-2 concrete actions, not comprehensive) rather than 4.

3 / 5

Completeness

It states a clear "what" (automate Affinity tasks via Rube MCP) but has no "Use when..." clause or explicit trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

The keywords present are technical jargon ("Rube MCP", "Composio", "Affinity tasks") with no natural phrases a user would say; it is closer to the 2-anchor (one or two generic keywords, missing natural phrases) than 3, which would require common variations users actually voice.

2 / 5

Distinctiveness Conflict Risk

"Affinity" plus "Rube MCP (Composio)" carves a clear niche with minimal overlap risk against other skills; it falls just below 5 because the generic "Automate ... tasks" phrasing leaves slight overlap room with other automation skills.

4 / 5

Total

12

/

20

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
ComposioHQ/awesome-claude-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.