Name: certify
Rating: 52.8 (1 reviews)
Author: membranedev

certify

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

Quality

59%

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/certify/SKILL.md

Quality

Content

61%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 concrete Membrane CLI commands and a solid connection workflow, but it loses points to a duplicated command, an unexplained overview section, and missing verification steps after potentially destructive action/proxy execution.

Suggestions

Remove the duplicated `action list` command by merging 'Popular actions' into 'Searching for actions', or actually list 2-3 common Certify actions there.

Add a verification checkpoint after `membrane action run` / proxy requests, e.g. re-fetch or inspect the `output` field to confirm the operation succeeded before proceeding.

Either expand the 'Certify Overview' bullets into a meaningful schema (Certification/Criterion/User) or remove them to tighten the document.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and lean, but the `action list --intent=QUERY --connectionId` command is duplicated (Searching for actions and Popular actions), and the 'Certify Overview' bullets (Certification/Criterion/User) are unexplained filler.	3 / 5
Actionability	Concrete, copy-paste-ready commands throughout (install, login, connection ensure, action run, request) with a thorough flags table; minor gaps are the ID placeholders and the 'Popular actions' section only showing the discovery command instead of real actions.	4 / 5
Workflow Clarity	The install→auth→connect→poll→search→run flow is sequenced with a real connection-state feedback loop, but action execution and proxy requests (which can be destructive/batch) have no verify-the-result checkpoint, capping the score per the rubric.	3 / 5
Progressive Disclosure	No bundle files exist; content is a single, well-sectioned file with a clearly signaled external docs link, appropriate for a CLI-wrapper skill, with only a minor gap from the unexplained overview bullets.	4 / 5
	Total	14 / 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 Use-when clause and a distinctive product name, but it relies on generic action verbs and misses the natural expense-report vocabulary users would actually say.

Suggestions

Replace generic verbs with concrete expense-report actions, e.g. 'Create and submit expense reports, track receipts, and manage approvals in Certify.'

Add natural trigger phrases a user would say: 'Use when the user mentions expense reports, receipts, reimbursement, or approvals in Certify.'

Tighten the trigger clause from 'interact with Certify data' to specific intents (submitting/approving expenses) to reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('Certify integration') but the actions 'Manage data, records, and automate workflows' are generic rather than concrete to the expense-report domain (e.g. creating or approving expense reports).	2 / 5
Completeness	Both a 'what' (Certify integration, manage data/records/workflows) and an explicit 'Use when...' trigger are present, but the trigger ('interact with Certify data') is generic rather than concrete phrases.	4 / 5
Trigger Term Quality	'Certify' is a natural keyword a user would say, but the description omits the domain synonyms users actually use such as 'expense reports', 'receipts', 'reimbursement', or 'approvals'.	3 / 5
Distinctiveness Conflict Risk	The product name 'Certify' gives a clear, distinct niche with low conflict risk, though the surrounding generic wording ('interact with Certify data') leaves minor overlap risk.	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/certify/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.