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

truework

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

Quality

64%

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

Quality

Content

67%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 a well-structured, actionable Membrane/Truework integration guide with concrete commands and a clear state-machine workflow. Its main weaknesses are occasional marketing-style padding and a single vague guidance line that could be tightened.

Suggestions

Trim filler such as 'so you can focus on the integration logic rather than auth plumbing' and replace 'Use action names and parameters as needed' with concrete selection guidance.

Consider moving the proxy flag table and the clientAction state-machine detail into a references/ file so SKILL.md stays a lean overview.

Number the end-to-end flow (install → login → connect → ready → search → run) explicitly so the multi-step sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as 'so you can focus on the integration logic rather than auth plumbing' and the filler line 'When to use which actions: Use action names and parameters as needed.', fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a flag table, landing at 'mostly executable guidance' with only minor gaps such as the vague action-selection guidance.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with explicit state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, matching 'clear sequence with most checkpoints present' though step numbering is informal.	4 / 5
Progressive Disclosure	No bundle files exist, but the single SKILL.md is well-sectioned with clear navigation; the proxy flag table and clientAction schema are somewhat reference-like yet reasonably placed, giving 'good structure; most content appropriately placed' with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 is distinct and includes an explicit 'Use when' trigger, but its capability language ('Manage data, records, and automate workflows') is generic and the trigger terms lack synonyms. It is recognizable but not vivid about what the skill concretely does.

Suggestions

Replace generic verbs with concrete Truework capabilities (e.g., 'Create and track verification reports, fetch employment and income data, manage credentials').

Add natural synonyms and entity names users would say (e.g., 'verification reports', 'employment records', 'income verification') to broaden trigger coverage.

Tighten the 'when' clause with concrete triggers (e.g., 'Use when the user wants to verify income/employment, pull Truework reports, or query HR data').

Dimension	Reasoning	Score
Specificity	The description names the domain ('Truework integration') but its actions are generic and minimal — 'Manage data, records, and automate workflows' lacks concrete capabilities, fitting the 'names domain but actions are minimal or generic' anchor rather than the 3 which requires 1-2 concrete actions.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Truework data'), so it clears the missing-trigger cap of 3; the 'when' is present but generic, so it sits below the 5 with concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces 'Truework' and 'Truework data' as keywords, but offers few natural variations or synonyms a user would say, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Truework integration' and 'interact with Truework data' carve a clear niche with distinct triggers and minimal overlap with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 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/truework/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.