Name: outfit
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

outfit

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

Quality

62%

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/outfit/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 CLI integration guide with concrete commands and a state-based connection workflow including a feedback loop. Its main weaknesses are minor filler, an orphaned 'Step 2' reference, and a long single-file layout that could benefit from reference splitting.

Suggestions

Fix or remove the broken 'skip to Step 2' reference by adding a labeled Step 2 heading or rewording to point at 'Searching for actions'.

Trim filler ('Use action names and parameters as needed.') and consider collapsing the 26-item Outfit overview tree into the few object types users most commonly act on.

Move the detailed clientAction state machine and proxy flag table into a reference file, leaving SKILL.md as a concise overview that links to it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes filler like 'Use action names and parameters as needed.' and a 26-item nested overview tree that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action search/run, and proxying, with only minor gaps from unfilled placeholders (CONNECTION_ID, QUERY, <agentType>).	4 / 5
Workflow Clarity	The connection flow has a clear state-based sequence (READY/BUILDING/CLIENT_ACTION_REQUIRED) with a poll-again feedback loop, but references a non-existent 'Step 2' heading and repeats the discovery command redundantly under 'Popular actions'.	4 / 5
Progressive Disclosure	There are no bundle files and the section structure is clear with no nested references, but at ~165 lines some inline material (the proxy flag table, the clientAction state machine) could be split into a reference file.	4 / 5
	Total	15 / 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 names the target platform and includes an explicit trigger clause, but its capability verbs are generic and lack concrete, distinctive actions. Tightening the action list with specific Outfit operations would raise specificity and distinctiveness.

Suggestions

Replace generic verbs with concrete Outfit operations (e.g., 'create and export branded documents, manage templates and brand assets, automate approval workflows').

Add natural trigger synonyms users might say (e.g., 'brand content', 'branded materials', 'Outfit templates') alongside 'Outfit data'.

Make the 'when' clause more specific by naming the triggering scenarios (e.g., 'Use when creating or distributing branded marketing content via Outfit').

Dimension	Reasoning	Score
Specificity	The domain (Outfit) is named, but the actions 'Manage data, records, and automate workflows' are minimal and generic rather than concrete operations, matching the anchor for naming a domain with generic actions.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Outfit data') are present, though the trigger is somewhat generic.	4 / 5
Trigger Term Quality	It includes the natural term 'Outfit' / 'Outfit data' a user might say, but offers few synonyms or common variations, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Outfit platform gives it a clear niche with minimal conflict risk, but the generic verbs ('manage', 'automate workflows') leave minor overlap with adjacent integration skills.	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/outfit/SKILL.md
Commit: f484c82

Reviewed: 5 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.