Name: biztera
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

biztera

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

Quality

63%

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/biztera/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 executable CLI commands and a clear connection workflow, but it is weighed down by a large padded entity list and lacks validation guidance for destructive operations. Splitting reference material into bundle files would improve organization.

Suggestions

Move the entity catalog and popular-actions table into a separate references file (e.g. references/actions.md) and link to it, removing the inlined duplicate-heavy list from SKILL.md.

Add an explicit validation/confirmation step before destructive actions like delete-project and delete-approval-request (e.g. list-then-confirm before deleting).

Trim duplicate and generic entries from the entity list so every token earns its place.

Dimension	Reasoning	Score
Conciseness	The ~170-line flat bullet list of entities (with many duplicates such as Alert, Event, Task, Comment, Notification) is substantial padding that adds no actionable knowledge, even though the CLI sections themselves are reasonably lean.	2 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus flag tables and a popular-actions table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints and error branches, but destructive actions (delete-project, delete-approval-request) are listed without any validation or verification step, capping workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	It has clear section structure but no bundle files; the large entity catalog and popular-actions table are inlined content that would be better placed in a separate reference file, and no external references are signaled.	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 states both what the skill does and when to use it, anchored to a distinct proprietary app. Its main weakness is generic action phrasing and thin natural-keyword coverage rather than concrete Biztera-specific trigger terms.

Suggestions

Replace generic verbs with concrete Biztera operations, e.g. 'Create and update projects, approval requests, and invitations; list messages and notifications.'

Expand the 'Use when' clause with natural user phrases such as 'Biztera projects,' 'Biztera approvals,' or 'manage Biztera records.'

Mention the specific record types users are likely to name (projects, approval requests, organizations, invitations) to strengthen trigger matching.

Dimension	Reasoning	Score
Specificity	Names the Biztera domain plus a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete Biztera operations, so it is not comprehensive.	3 / 5
Completeness	Both a 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Biztera data') are present, though the trigger could be more specific and concrete.	4 / 5
Trigger Term Quality	The natural trigger 'Use when the user wants to interact with Biztera data' supplies a relevant keyword, but coverage of natural terms and synonyms is limited to 'Biztera data,' 'records,' and 'workflows,' missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named proprietary app 'Biztera' provides a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	15 / 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/biztera/SKILL.md
Commit: f484c82

Reviewed: ~7 hours 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.