Name: trunarrative
Rating: 60 (1 reviews)
Author: membranedev

trunarrative

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

Quality

70%

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

Quality

Content

75%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 content is highly actionable with executable commands and clear connection-state handling, but it opens with background explanation Claude already knows and has slightly inconsistent step numbering. Trimming the intro and fixing the step labels would lift conciseness and workflow clarity.

Suggestions

Cut or condense the opening platform-description paragraph ('TruNarrative is a platform for fraud and anti-money laundering compliance...') since Claude already knows this domain.

Fix the inconsistent step numbering so 'Step 2' follows a defined Step 1/1a rather than appearing after '1b'.

Move the generic proxy flag table or 'Popular actions' search tip to a clearly signaled reference section to keep the main flow lean.

Dimension	Reasoning	Score
Conciseness	The opening paragraph and a few asides explain platform/background concepts Claude already knows, but the bulk is efficient CLI commands, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Copy-paste ready commands with realistic arguments and a flag table cover the common cases (login, connection ensure/get, action list/run, request proxy), matching 'fully executable; copy-paste ready code or commands'.	5 / 5
Workflow Clarity	The connection flow has explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after user acts), but inconsistent step numbering ('Step 2' after '1b') leaves minor gaps.	4 / 5
Progressive Disclosure	Single-file skill (~150 lines) with reasonable section headers and clearly scoped subsections; no nested references, though the external docs link is the only off-body pointer.	4 / 5
	Total	16 / 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 clearly identifies its niche and includes both what and when, but its action list is generic and lacks natural trigger synonyms. Tightening the action phrasing and adding concrete trigger variations would raise specificity and trigger quality.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions specific to TruNarrative such as 'search cases, run workflow actions, query records'.

Add natural trigger phrases and synonyms users would say, e.g. 'TruNarrative cases, queues, compliance checks, fraud/AML lookups'.

Make the 'Use when' clause more specific than 'interact with TruNarrative data', naming the typical intents (case management, queue work, record search).

Dimension	Reasoning	Score
Specificity	Names the TruNarrative domain and a couple of actions ('Manage data, records, and automate workflows') but the actions are generic and not comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	Both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with TruNarrative data') are present, but the trigger could be more specific, matching the 'both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Relevant keywords (TruNarrative, data, records, workflows) appear but natural synonyms and variations a user would say are missing, fitting 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	Names a specific product (TruNarrative) with distinct triggers and minimal overlap risk with other skills, matching 'clear niche with distinct triggers; minimal conflict risk.'	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/trunarrative/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.