Name: persona
Rating: 56.8 (1 reviews)
Author: membranedev

persona

Persona integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Persona data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/persona/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 is highly actionable with executable commands and a state-machine-style connection workflow including feedback loops, landing it just above the midpoint. Conciseness is held back by an unnecessary product blurb and empty stub sections, and workflow clarity has a minor sequencing gap (an undefined "Step 2").

Suggestions

Remove or trim the opening "Persona is a customer data platform..." paragraph and the empty "Persona Overview" / "When to use which actions" stubs to improve conciseness.

Either define "Step 2" and add a matching "1a" heading, or renumber the connection steps (e.g. 1, 2, 3) so the workflow sequence is unambiguous.

Populate "Popular actions" with a few concrete example action names, or remove the section if it only duplicates the "Searching for actions" guidance.

Dimension	Reasoning	Score
Conciseness	The bulk is concrete commands, but the opening product-description paragraph ("Persona is a customer data platform that helps businesses understand their customers better...") and stub sections ("Persona Overview", "When to use which actions") add unnecessary padding.	3 / 5
Actionability	Provides many copy-paste-ready commands (install, login, connection ensure, action run, request) plus a flags table, with only minor gaps such as the "Popular actions" section not actually listing any actions.	4 / 5
Workflow Clarity	The connection workflow is sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-retry feedback loop, but references an undefined "Step 2" and uses a "1b" heading with no matching "1a".	4 / 5
Progressive Disclosure	No bundle files exist; content is organized into clear section headers within a single file, though at ~140 lines with near-empty stub sections it could be better organized or split.	4 / 5
	Total	15 / 20 Passed

Description

62%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 a concrete entity list and an explicit trigger clause, placing it solidly above the midpoint. Its main weakness is the single generic verb ("Manage") and lack of trigger-term synonyms, which keep specificity and trigger quality at the middle anchor.

Dimension	Reasoning	Score
Specificity	Names many concrete domain entities ("Persons, Organizations, Deals, Leads, Projects, Activities") but only a single generic verb ("Manage ... and more"), so actions remain minimal rather than comprehensive.	3 / 5
Completeness	Explicitly provides both a "what" ("Manage Persons, Organizations, Deals, Leads, Projects, Activities and more") and a "when" ("Use when the user wants to interact with Persona data"), though the trigger is somewhat generic.	4 / 5
Trigger Term Quality	Includes relevant keywords (Persona, Persons, Deals, Leads, Projects, Activities) and a "Use when the user wants to interact with Persona data" trigger, but misses common synonyms/variations a user would naturally say.	3 / 5
Distinctiveness Conflict Risk	The Persona-specific entity list (Deals, Leads, Projects) makes it mostly distinct with only minor overlap risk against other CRM/data skills, though "interact with Persona data" is fairly broad.	4 / 5
	Total	14 / 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/persona/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.