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

plextrac

PlexTrac integration. Manage data, records, and automate workflows. Use when the user wants to interact with PlexTrac 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/plextrac/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 highly actionable with executable commands and a mostly clear connection workflow, supported by good section structure. The main weaknesses are minor verbosity in the intro/context passages and a dangling "Step 2" reference that breaks the workflow's explicitness.

Suggestions

Trim the opening context paragraph and phrases like "so you can focus on the integration logic rather than auth plumbing" to assume Claude's familiarity.

Label "Step 2" explicitly (e.g. add a "### 2. Search for actions" heading) so the forward references in the connection flow resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening paragraph explaining what PlexTrac is and who uses it, plus flourishes like "so you can focus on the integration logic rather than auth plumbing", are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request proxy) plus a flag table, fully executable and covering the main scenarios.	5 / 5
Workflow Clarity	There is a clear install→login→connect→poll→search→run sequence with state checks and recovery guidance for CLIENT_ACTION_REQUIRED and error states, but the "Step 2" reference is never labeled and some checkpoints are implicit rather than explicit validation.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files needed; the only gap is that the proxy flag table and best-practices detail could live in a separate reference file.	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 cleanly states what the skill does and when to use it with a distinct, product-specific trigger, but its capability verbs are generic and it omits natural synonym variations a user might say. Tightening the action list and broadening trigger terms would lift the weaker dimensions.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete PlexTrac capabilities such as "create findings, generate reports, track remediation, and manage engagements".

Expand the trigger clause to include natural synonyms users say, e.g. "Use when the user wants to work with PlexTrac findings, reports, engagements, or vulnerability data."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the PlexTrac domain and lists a few actions, but the actions themselves are generic rather than concrete capabilities, matching the anchor for domain-plus-1-2-actions without comprehensiveness.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with PlexTrac data"), but the "when" clause is fairly general, matching the anchor where both are present yet the trigger could be more specific.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with PlexTrac data" surfaces the core keyword "PlexTrac", but it lacks common variations or synonyms (e.g. findings, reports, pentest), fitting the anchor for some relevant keywords with missing variations.	3 / 5
Distinctiveness Conflict Risk	The product-specific trigger "PlexTrac" carves out a clear niche with a distinct trigger phrase and minimal overlap with other skills, matching the clear-niche anchor.	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/plextrac/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.