Name: triggre
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

triggre

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

Quality

61%

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/triggre/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 a well-structured, actionable CLI guide with a strong connection-state feedback loop. Its weaknesses are mild verbosity/redundancy and the absence of validation checkpoints for destructive data operations.

Suggestions

Add a verification checkpoint after data-mutating actions (e.g., re-query the record or check the action `output`/status before declaring success) to lift workflow clarity above the destructive-operations cap.

Dedupe the 'Searching for actions' and 'Popular actions' sections, which repeat the `membrane action list` invocation with slightly different flags.

Trim padding such as 'designed for business users and citizen developers' and the 'so you can focus on the integration logic' aside to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary explanation such as 'designed for business users and citizen developers' and redundant action-list invocations across 'Searching for actions' and 'Popular actions', fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, request) plus a flags table provide mostly executable guidance with only minor gaps such as the generic placeholder input '{"key": "value"}'.	4 / 5
Workflow Clarity	The connection workflow has explicit state-based checkpoints and a poll/handle/re-poll feedback loop, but data-mutating operations (action run, proxy POST/PUT/DELETE on records) lack validation/verification steps; per the destructive/batch cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Working with Triggre, Authentication, Connecting, Actions, Proxy, Best practices) with no bundle files present; minor gaps like overlapping action-list sections keep it just below a 5.	4 / 5
	Total	14 / 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 cleanly names the Triggre platform and provides an explicit 'Use when' trigger, satisfying both what and when. Its main weakness is generic action verbs ('manage', 'automate') that lack concrete, distinguishing operations.

Suggestions

Replace generic verbs with concrete Triggre operations (e.g., 'Create and update records, query dashboards, trigger processes') to lift specificity and distinctiveness.

Expand the trigger phrase with natural synonyms users might say (e.g., 'Triggre data, records, tasks, or processes') to improve trigger-term coverage.

Tighten the 'when' clause to name specific Triggre objects (tasks, dashboards, process instances) rather than the vague 'interact with Triggre data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Triggre integration') and a few actions ('Manage data, records, and automate workflows'), but the verbs/nouns are generic rather than concrete operations, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Triggre data') are present, but the 'when' could be more explicit/specific, matching the anchor for having both with room to sharpen the trigger.	4 / 5
Trigger Term Quality	Relevant keywords ('Triggre', 'data', 'records', 'workflows') and a trigger phrase ('Use when the user wants to interact with Triggre data') are present, but common variations or synonyms are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific platform 'Triggre' gives it a clear niche with minimal conflict risk, though the generic action verbs ('manage data', 'automate workflows') leave minor overlap with other data-management skills, fitting 'mostly distinct; minor overlap risk'.	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/triggre/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.