acculynx-automation

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

2.43x

Quality

53%

Does it follow best practices?

Impact

95%

2.43x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./composio-skills/acculynx-automation/SKILL.md

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is too vague to effectively guide skill selection. While it names the specific platform (Acculynx) and integration method (Rube MCP/Composio), it fails to describe what specific tasks can be automated and provides no trigger guidance for when Claude should use this skill. The procedural note about searching tools is implementation detail rather than capability description.

Suggestions

Add specific Acculynx capabilities like 'create estimates, manage leads, schedule appointments, track projects' to clarify what tasks can be automated.

Add a 'Use when...' clause with trigger terms like 'roofing CRM', 'Acculynx', 'contractor management', 'roofing estimates', or specific workflow names.

Remove the procedural guidance ('Always search tools first') from the description - this belongs in the skill body, not the selection-focused description.

Dimension	Reasoning	Score
Specificity	The description says 'Automate Acculynx tasks' which is extremely vague - it doesn't specify what tasks can be automated (creating estimates, managing projects, scheduling, etc.). 'Search tools first for current schemas' is procedural guidance, not capability description.	1 / 3
Completeness	The 'what' is extremely vague ('automate tasks'), and there is no 'Use when...' clause or equivalent trigger guidance. The description fails to answer when Claude should select this skill over others.	1 / 3
Trigger Term Quality	Includes 'Acculynx' which is a specific product name users would mention, and 'Rube MCP' and 'Composio' as technical terms. However, it lacks natural task-oriented keywords users might say like 'roofing', 'estimates', 'leads', 'CRM', or specific Acculynx features.	2 / 3
Distinctiveness Conflict Risk	'Acculynx' is a specific product which helps distinguish it, but 'automate tasks via MCP' is generic enough to potentially conflict with other Composio/MCP-based automation skills. Without specific task types, overlap risk exists.	2 / 3
	Total	6 / 12 Passed

Implementation

85%

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-structured skill that efficiently guides Claude through Acculynx automation via Rube MCP. The workflow is clear with proper validation checkpoints, and the content respects token budget. The main weakness is that tool call examples use placeholder syntax rather than fully concrete, executable examples with realistic parameter values.

Suggestions

Replace placeholder comments like '/* schema-compliant args from search results */' with a concrete example showing actual Acculynx-specific parameters (e.g., creating a job or fetching contacts)

Add one complete end-to-end example showing a real Acculynx task from search through execution with actual tool slugs and arguments

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, avoiding unnecessary explanations of what Acculynx or Composio are. Every section serves a purpose and assumes Claude understands the concepts.	3 / 3
Actionability	Provides concrete tool call patterns with parameter examples, but uses pseudo-code style rather than fully executable code. The argument placeholders like '/* schema-compliant args */' reduce copy-paste readiness.	2 / 3
Workflow Clarity	Clear 3-step workflow with explicit sequence (discover → check connection → execute). Includes validation checkpoint for connection status and explicit guidance to confirm ACTIVE status before proceeding.	3 / 3
Progressive Disclosure	Well-organized with clear sections progressing from prerequisites to setup to workflow to pitfalls. External reference to Composio docs is one level deep and clearly signaled. Quick reference table aids navigation.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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: ComposioHQ/awesome-claude-skills
Commit: 2790447

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

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.