Name: truora
Rating: 51.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

truora

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

Quality

56%

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

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 body delivers strong executable Membrane CLI guidance with clear connection-state handling, but it is weighed down by a large padded entity list that should be split into a reference file. Trimming that list and unifying the workflow into a numbered sequence would notably improve it.

Suggestions

Move the 'Truora Overview' entity and per-country sanction list into a references/ file (e.g. ENTITIES.md) and link to it from the body, reclaiming the context budget.

Consolidate the install → authenticate → connect → search → run flow into one numbered sequence with explicit validation checkpoints.

Fill in at least one concrete action example end-to-end (real intent and actionId) so the run/proxy path is fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The ~75-line 'Truora Overview' bulleted list (entity types and per-country sanction lists) is heavy padding that Claude does not need inline, matching 'noticeably verbose; several unnecessary explanations or padded sections', despite the command-focused sections otherwise being lean.	2 / 5
Actionability	Concrete, copy-paste-ready commands are provided throughout (install, login, connection ensure, action list/run, request proxy) with a flags table, but examples rely on placeholders like 'QUERY', 'CONNECTION_ID', and '<actionId>' that leave minor gaps, fitting 'mostly executable guidance; minor gaps'.	4 / 5
Workflow Clarity	The connect-to-run flow is sequenced with explicit state branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop, but the steps are spread across sections rather than a single numbered sequence with checkpoints, matching 'clear sequence with most checkpoints present'.	4 / 5
Progressive Disclosure	Sections are reasonably organized but the large inline entity/sanction-list dump is content that clearly belongs in a separate reference file, and no external references are signaled, fitting 'some structure; content that should be separate is inline'.	3 / 5
	Total	13 / 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 correctly includes an explicit 'Use when' trigger and leverages a distinctive brand name, but it relies on generic verbs instead of Truora's concrete identity-verification capabilities. Tightening the action list and trigger phrases would materially improve it.

Suggestions

Replace generic verbs with concrete Truora capabilities, e.g. 'Run identity verifications, background checks, and phone-number lookups' instead of 'Manage data, records, and automate workflows'.

Expand the trigger with natural user phrases: 'Use when the user wants to run identity verification, background checks, or onboarding via Truora'.

Mention the Latin-America / fraud-prevention niche to sharpen distinctiveness beyond the brand name alone.

Dimension	Reasoning	Score
Specificity	It names the domain ('Truora integration') but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete Truora capabilities like identity verification or background checks, matching the 'names the domain but actions are generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Truora data') are present, but the 'when' could be more specific about Truora's actual use cases, fitting 'has both what and when; when could be more explicit'.	4 / 5
Trigger Term Quality	The trigger relies on the brand keyword 'Truora' and 'data', which are relevant but miss common natural variations a user would say (e.g., 'background check', 'identity verification', 'onboarding'), placing it at 'some relevant keywords but missing synonyms'.	3 / 5
Distinctiveness Conflict Risk	The unique brand name 'Truora' gives it a clear, distinct trigger with minimal conflict risk, but the generic accompanying actions ('manage data, records') leave minor overlap risk, matching 'mostly distinct; 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/truora/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.