CtrlK
BlogDocsLog inGet started
Tessl Logo

privacera

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

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/privacera/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 skill delivers executable CLI guidance and a clear connection workflow, but is weighed down by a bloated inline entity catalog and lacks external reference files. Moving the catalog into a reference file and fixing the broken Step 2 reference would materially improve it.

Suggestions

Move the ~160-line entity catalog into a separate references file (e.g. references/entities.md) and link to it from a short overview list.

Add the missing 'Step 2' section or remove the 'Skip to Step 2' references so the connection workflow is internally consistent.

Add brief guidance on how to select among discovered actions (e.g. interpreting inputSchema/outputSchema) to close the actionability gap.

DimensionReasoningScore

Conciseness

The ~160-line bullet catalog of entity names (Dataset, User, Role ... Audit Management) is padded reference material with no explanatory value, while the CLI sections themselves are reasonably efficient.

2 / 5

Actionability

Provides concrete copy-paste commands for install, auth, connection, action search/run, and proxying, with only minor gaps around how to choose among discovered actions.

4 / 5

Workflow Clarity

Clear install-auth-connect-poll-run sequence with state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) as checkpoints, though the 'Skip to Step 2' reference points to a nonexistent Step 2.

4 / 5

Progressive Disclosure

Section headers and the CLI flow are organized, but the large entity catalog is reference data inlined in SKILL.md that belongs in a separate file, and no bundle files are used.

3 / 5

Total

13

/

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 identifies the Privacera niche and provides an explicit use-when trigger, but its capability verbs are generic and it lacks richer trigger synonyms. Distinctiveness is strong thanks to the named product.

Suggestions

Replace generic verbs ('Manage', 'automate workflows') with concrete Privacera actions such as 'govern access', 'apply masking policies', or 'audit data access'.

Add natural trigger terms users would say, e.g. 'data governance', 'access policies', 'masking', or 'compliance', alongside 'Privacera data'.

DimensionReasoningScore

Specificity

Names the Privacera domain plus three action areas ('Manage data, records, and automate workflows'), but the verbs are generic rather than concrete.

3 / 5

Completeness

States both what it does (manage data/records/automate workflows) and when to use it ('Use when the user wants to interact with Privacera data'), though the 'what' is somewhat generic.

4 / 5

Trigger Term Quality

Includes relevant keywords ('Privacera', 'data', 'records', 'workflows') and a use-when trigger, but misses common variations like governance, access policies, or compliance.

3 / 5

Distinctiveness Conflict Risk

Privacera is a specific named product, giving a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.