Name: connectall
Rating: 61.6 (1 reviews)
Author: membranedev

connectall

ConnectALL integration. Manage data, records, and automate workflows. Use when the user wants to interact with ConnectALL data.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/connectall/SKILL.md

Quality

Content

82%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 content is highly actionable with executable commands and a well-sequenced connection workflow including state-based validation. Its main weaknesses are a slightly padded intro and an unlabeled 'Step 2' cross-reference that weakens navigation.

Suggestions

Trim the marketing-style opening paragraph ('helps organizations improve collaboration, visibility, and efficiency...') to a one-line product definition, since Claude does not need the value-stream pitch.

Fix the broken cross-reference: either label 'Step 2' (e.g., '### 2. Search for actions') or rephrase 'skip to Step 2' to name the target section directly.

Consider extracting the proxy flags table and clientAction state details into a short reference file so SKILL.md reads as a lean overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and a flags table, with only minor over-explanation (the marketing-style intro paragraph and phrases like 'so you can focus on the integration logic'), fitting the 'efficient; minor instances that could be trimmed' anchor.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases (login, connection ensure, polling with --wait, action list/run with --input, request with a full flags table), matching the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→poll-state→search→run→proxy sequence exists with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the 'skip to Step 2' reference points at an unlabeled step, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized with clear section headers and no external references are needed, but at ~140 lines it is a single inlined file rather than an overview pointing to one-level-deep references, so it lands at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

62%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 cleanly states both purpose and a 'Use when' trigger for a named product, but its action verbs are generic and it lacks trigger synonyms or file-extension-style variations. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records') with specific ConnectALL actions (e.g., 'sync records across tools, map fields, automate workflows between Jira and Azure DevOps').

Broaden trigger terms with natural synonyms users say (e.g., 'value stream management', 'tool synchronization', 'ConnectALL sync').

Make the 'when' clause more concrete by listing the specific ConnectALL data or integration scenarios that should trigger the skill.

Dimension	Reasoning	Score
Specificity	Names the domain ('ConnectALL integration') and a couple of actions ('Manage data, records, and automate workflows'), but the verbs are generic and coverage is not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor rather than the multi-specific-action level above.	3 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with ConnectALL data') are present; the trigger could be more specific, so it sits at 4 rather than 5.	4 / 5
Trigger Term Quality	Relevant keywords ('ConnectALL', 'data', 'records', 'workflows') appear, but common variations or synonyms a user might say are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	ConnectALL is a named niche platform with a distinct trigger ('interact with ConnectALL data'), but the generic 'manage data, records' verbs create minor overlap risk with broader data skills, keeping it just below 5.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/connectall/SKILL.md
Commit: f484c82

Reviewed: 4 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.