Name: proofpoint
Rating: 55.2 (1 reviews)
Author: membranedev

proofpoint

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

Quality

62%

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/proofpoint/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 content is a well-structured, actionable CLI guide with a clear connect-and-poll workflow and validation via connection states, though it opens with unnecessary company background and repeats some commands across sections.

Suggestions

Trim the introductory "Proofpoint is a cybersecurity company..." paragraph — Claude already knows this — and fold the redundant "Popular actions" command into the earlier "Searching for actions" section.

Fix the broken "skip to Step 2" references by labeling the sequenced steps explicitly (e.g. Step 1: connect, Step 2: search/run) so the workflow reads as one clean path.

Add a short validation note for the action-run path (check the returned `output`/error fields before proceeding) so the run workflow matches the connection workflow's checkpoint rigor.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI commands and flag tables, but the opening paragraph explains what Proofpoint is and the "Popular actions" section repeats the earlier `action list` command, fitting "Mostly efficient but includes some unnecessary explanation or could be tightened."	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure/get, action list/run, request) with a flag table, but placeholders like CONNECTION_ID and the abstract QUERY intent leave minor gaps, matching "Mostly executable guidance; concrete code or commands with minor gaps."	4 / 5
Workflow Clarity	The install→authenticate→connect→poll-state→search→run sequence is clear with validation via connection-state polling (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but "skip to Step 2" references an unmarked step and sections repeat, so it is "Clear sequence with most checkpoints present; minor validation gaps."	4 / 5
Progressive Disclosure	The single self-contained file is organized into clearly headed sections with no nested references, appropriate for a CLI usage guide; minor redundancy (repeated action-list command) keeps it just below a 5.	4 / 5
	Total	15 / 20 Passed

Description

57%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 answers both what and when with an explicit trigger clause and is distinct due to the named product, but its capability list is generic rather than concrete Proofpoint actions and it lacks natural trigger variations like phishing or email security.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Proofpoint capabilities such as email-message analysis, threat-insight queries, and campaign/attachment/URL lookups.

Add natural trigger terms users would actually say — e.g. "Use when investigating phishing campaigns, analyzing email threats, or querying Proofpoint threat intelligence."

Tighten the trigger to mention the specific data objects (Email Message, Threat Insight, Campaign) so it is less likely to overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	It names the domain ("Proofpoint integration") but the actions — "Manage data, records, and automate workflows" — are generic and not concrete Proofpoint capabilities, matching the score-2 anchor "Names the domain but actions are minimal or generic."	2 / 5
Completeness	It has both a "what" ("Manage data, records, and automate workflows") and an explicit "Use when the user wants to interact with Proofpoint data" trigger, but the "what" is vague rather than concrete, so it sits at "Has both 'what' and 'when'; 'when' could be more explicit or specific."	4 / 5
Trigger Term Quality	"Proofpoint" is a strong natural keyword and "interact with Proofpoint data" is a usable trigger, but common variations users would actually say (phishing, email security, threat intelligence) are absent, fitting "Some relevant keywords but missing common variations or synonyms."	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to a specific named product ("Proofpoint") makes it mostly distinct with low conflict risk, though the generic "Manage data, records, automate workflows" phrasing leaves minor overlap risk with other integration skills.	4 / 5
	Total	13 / 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/proofpoint/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.