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

sertifi

Sertifi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sertifi 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/sertifi/SKILL.md

Quality

Content

63%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 delivers highly actionable, executable CLI guidance with a well-sequenced connection workflow and explicit state-based checkpoints. Its main weaknesses are a large inlined entity list that belongs in a reference file and minor verbose/marketing phrasing that inflates token cost.

Suggestions

Move the ~45-item Sertifi entity list into a separate reference file (e.g. references/entities.md) and link to it from the overview to improve progressive disclosure and reduce token load.

Trim marketing phrasing ('so you can focus on the integration logic rather than auth plumbing', 'This will burn less tokens and make communication more secure') to leaner factual statements.

Fix the 'skip to Step 2' reference by labeling the downstream section as Step 2 or rewording the pointer to the actual section name.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the ~45-item Sertifi entity list and marketing-fluff phrases ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') add tokens that could be trimmed or moved.	3 / 5
Actionability	It provides concrete, copy-paste-ready bash commands for login, connection ensure, action list/run, and proxy requests plus a flags table, with only minor placeholder gaps (CONNECTION_ID, QUERY, <agentType>).	4 / 5
Workflow Clarity	The install→authenticate→connect→poll sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, SETUP_FAILED) and a poll-again feedback loop, though the 'skip to Step 2' reference points to no labeled Step 2.	4 / 5
Progressive Disclosure	Section headers are well organized, but no bundle files exist and the large inlined entity list is reference content that would be better split into a separate file, fitting 'some structure but content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

61%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 clearly identifies its niche via the Sertifi brand and includes an explicit 'Use when' trigger, but its action wording is generic and it omits the natural domain vocabulary (contracts, payments, e-signatures) that users would actually say. Strengthening the concrete actions and trigger terms would lift the weaker dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Sertifi operations such as creating and sending contracts, collecting payments, and requesting e-signatures.

Expand the trigger clause to include natural user phrasing: 'Use when the user wants to send Sertifi contracts, collect payments, request e-signatures, or automate closing workflows.'

Mention the hospitality, travel, and events closing-process niche in the description to further sharpen distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Sertifi integration') but its actions — 'Manage data, records, and automate workflows' — are generic and abstract rather than concrete operations, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 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 Sertifi data'), but the 'when' could be more specific, matching the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Natural keywords are limited to the brand name ('Sertifi', 'interact with Sertifi data'); it misses the domain terms users would actually say like contracts, payments, or e-signatures, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Sertifi' is a specific named product, giving the skill a clear niche with a distinct brand trigger and minimal risk of firing for the wrong skill.	5 / 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/sertifi/SKILL.md
Commit: f484c82

Reviewed: 4 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.