Name: plecto
Rating: 60 (1 reviews)
Author: membranedev

plecto

Plecto integration. Manage Organizations, Persons, Deals, Pipelines, Activities, Notes and more. Use when the user wants to interact with Plecto data.

Quality

70%

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

Quality

Content

75%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 well-structured and highly actionable with executable commands and a clear connection workflow including feedback loops. The main gaps are the empty "Popular actions" section and dangling "Step 2" references.

Suggestions

Either populate the "Popular actions" section with a few concrete example actions (e.g., list deals, get KPI values) or rename it to avoid implying a list that isn't there.

Label the workflow steps explicitly (Step 1, Step 2) or remove the "skip to Step 2" / "Step 2" references so the dangling pointers resolve.

Tighten the introductory paragraph and remove "Use action names and parameters as needed" to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is command-heavy and mostly lean, with only minor over-explanation (the introductory "Plecto is a real-time dashboard software..." paragraph, the filler line "Use action names and parameters as needed", and the rambling agent-types sentence) that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready commands with real flags for install, auth, connect, search, run, and proxy, but the "Popular actions" section is a gap — it promises popular actions yet only redirects to the discovery command without listing any.	4 / 5
Workflow Clarity	The connection-readiness flow is a clear sequence with explicit state branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but references to "Step 2" are dangling with no matching labeled step, a minor clarity gap.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-organized with clear section headers; the detailed clientAction state machine and proxy flag table are reasonably kept inline for a CLI skill, though the file is longer than a pure overview.	4 / 5
	Total	16 / 20 Passed

Description

66%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 distinct and explicitly answers both what and when, but its action vocabulary is generic ("Manage") and its trigger terms are limited to the single proper noun "Plecto" with no synonyms.

Suggestions

Replace the generic verb "Manage" with specific actions (e.g., "Create, update, and query Organizations, Persons, Deals...") to raise specificity.

Expand the trigger clause with natural phrases users actually say, e.g., "Use when the user wants to query Plecto KPIs, manage deals, or pull dashboard data."

Drop the vague "and more" or replace it with the remaining concrete object types for tighter coverage.

Dimension	Reasoning	Score
Specificity	It names six concrete Plecto objects ("Organizations, Persons, Deals, Pipelines, Activities, Notes") but relies on a single generic verb ("Manage") and pads with "and more", so the action coverage is not comprehensive.	3 / 5
Completeness	It states both a clear "what" (manage the listed Plecto entities) and an explicit "when" ("Use when the user wants to interact with Plecto data"), but the "when" is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	The only natural keyword is the proper noun "Plecto" in "Use when the user wants to interact with Plecto data", with no synonyms or common variations, matching the "Works with PDF files" anchor.	3 / 5
Distinctiveness Conflict Risk	"Plecto integration" targets a specific named SaaS application, giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	15 / 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/plecto/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.