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

paymo

Paymo integration. Manage Organizations, Pipelines, Leads, Users, Goals, Filters. Use when the user wants to interact with Paymo data.

Quality

73%

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/paymo/SKILL.md

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 delivers actionable, executable CLI guidance with a solid connection-state workflow and clear section structure. It would benefit from trimming the padded intro/redundant sections and moving detailed reference material into separate files.

Suggestions

Trim the introductory Paymo overview paragraph and merge the redundant 'Searching for actions' and 'Popular actions' sections to reduce token overhead.

Concretize the 'QUERY' intent placeholder with a worked example (e.g., --intent 'list tasks') so the action-list command is immediately usable.

Move the proxy flag reference table and detailed connection-state handling into separate reference files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the introductory Paymo overview paragraph and the redundant 'Searching for actions'/'Popular actions' sections add unnecessary padding.	3 / 5
Actionability	Provides mostly executable, copy-paste-ready commands for install, auth, connection, search, run, and proxy, with minor gaps like the unconcretized 'QUERY' intent placeholder.	4 / 5
Workflow Clarity	The connection setup has a clear state-machine sequence with polling checkpoints and a re-poll feedback loop, though step numbering is inconsistent (references an unlabeled 'Step 2' and a '1b' with no '1a').	4 / 5
Progressive Disclosure	Well-organized into clear navigable sections, though all reference-style content (proxy flag table, connection states) is inlined in a single ~140-line file rather than split into reference files.	4 / 5
	Total	15 / 20 Passed

Description

78%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 specific and well-targeted to the Paymo niche, clearly answering what it does and when to use it. The main weakness is the generic 'Manage' verb and a somewhat abstract trigger phrase that could name more concrete use cases.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'Manage Organizations, Pipelines, Leads, Users, Goals, Filters' — naming six specific entities, though the single generic verb 'Manage' limits action diversity compared to multi-verb examples.	4 / 5
Completeness	Clearly answers both 'what' (Paymo integration managing named entities) and 'when' ('Use when the user wants to interact with Paymo data'), but the trigger could be more specific with concrete phrases.	4 / 5
Trigger Term Quality	Good keyword coverage with the product name 'Paymo' and domain entities (Organizations, Pipelines, Leads) plus an explicit 'Use when...' trigger, though a few natural synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — the specific Paymo product — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/paymo/SKILL.md
Commit: f484c82

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