CtrlK
BlogDocsLog inGet started
Tessl Logo

connectwise-psa

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

56

Quality

64%

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/connectwise-psa/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 concrete, executable CLI integration guide with a solid connection workflow and feedback loop. Its main weaknesses are a padded introductory paragraph and a slightly long inline actions table that could be extracted.

Suggestions

Trim the opening paragraph that explains what a PSA/MSP is; assume Claude's familiarity and lead with the Membrane CLI workflow.

Fix the dangling "skip to Step 2" reference by labeling the action-search/run sections as Step 2.

Consider moving the 20-row popular-actions table into a references file and keeping only the most common entries inline.

DimensionReasoningScore

Conciseness

The opening paragraph explains what a PSA platform and MSPs are (concepts Claude largely already knows) and there is some prose padding, though most of the body is tight CLI commands, fitting "mostly efficient with some unnecessary explanation".

3 / 5

Actionability

Copy-paste executable commands cover install, auth, connection, action search, action run, and proxy, plus a table of popular action keys; minor gaps remain in binding placeholders like CONNECTION_ID to concrete extraction steps.

4 / 5

Workflow Clarity

There is a clear install→authenticate→connect→poll sequence with a genuine feedback loop (poll state, handle CLIENT_ACTION_REQUIRED / SETUP_FAILED), but the "skip to Step 2" reference is dangling and action execution lacks validation.

4 / 5

Progressive Disclosure

A well-organized, self-contained single-file guide with clear section headers and no nested references; at ~180 lines with a long inline popular-actions table it is slightly above the simple-skill threshold and could be split, so it falls just short of a 5.

4 / 5

Total

15

/

20

Passed

Description

61%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 is distinctive and includes an explicit use-when trigger, but its action list is generic rather than concrete. Tightening "Manage data, records, and automate workflows" into specific operations would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Connectwise PSA operations, e.g. "Manage tickets, companies, contacts, projects, and time entries".

Add a few natural trigger synonyms users might say (service desk, MSP, sales opportunities) alongside "Connectwise PSA".

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the Connectwise PSA domain but uses generic, abstract actions rather than concrete operations (e.g. create tickets, list companies), matching the score-2 anchor of minimal/generic actions.

2 / 5

Completeness

Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Connectwise PSA data") are present; the when is explicit but the what is vague, so it falls short of a 5.

4 / 5

Trigger Term Quality

"Connectwise PSA" is a strong natural keyword a user would actually say, but coverage is narrow and misses common variations/synonyms (tickets, service desk, companies, MSP).

3 / 5

Distinctiveness Conflict Risk

The named product "Connectwise PSA" carves a clear niche with distinct triggers and minimal conflict risk against other skills.

5 / 5

Total

14

/

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
membranedev/application-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.