Name: faceup
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

faceup

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

Quality

66%

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/faceup/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 body is highly actionable with ready-to-run Membrane commands and a clear connection-state workflow, but carries some trimmable prose and lacks validation guidance around action execution. It is well-structured for a single-file skill.

Suggestions

Trim editorial asides ('so you can focus on the integration logic rather than auth plumbing', the agent-types tail sentence) to improve token efficiency.

Add a brief validation/check step before running or proxying actions (e.g. confirm connection state is READY, dry-run parameter schema) to strengthen workflow clarity.

Resolve the contradictory framing — the intro calls FaceUp a financial planning tool while the Overview lists social-style features (Posts, Friends, Messages) — so Claude acts on accurate context.

Dimension	Reasoning	Score
Conciseness	Commands are dense and concrete, but several prose asides ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', the agent-types sentence) are padding that could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Copy-paste-ready commands cover install, login, connection ensure/poll, action list/run, and proxy requests with a full flag table, matching the 'fully executable; copy-paste ready commands covering common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a poll-and-retry feedback loop, but running actions and proxy requests lack explicit validation checkpoints before execution.	4 / 5
Progressive Disclosure	Content is organized into clearly headed sections (Install, Auth, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files to split out; structure is good with only minor organization gaps given the single-file scope.	4 / 5
	Total	16 / 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 clearly identifies the FaceUp niche and includes an explicit 'Use when' trigger, but its capability list is generic rather than concrete. Tightening the action verbs would lift specificity and distinctiveness.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete FaceUp actions (e.g. 'pull reports, sync transactions, trigger forecasts').

Add a few natural trigger synonyms or feature terms users might say beyond just 'FaceUp data'.

Keep the explicit 'Use when...' clause but pair it with more specific capability phrasing to reach the top anchor.

Dimension	Reasoning	Score
Specificity	Names the FaceUp domain but the listed actions ('Manage data, records, and automate workflows') are generic categories rather than concrete operations, matching the 'names domain but actions minimal or generic' anchor.	2 / 5
Completeness	Both a 'what' ('FaceUp integration. Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with FaceUp data') are present, though the 'what' is vague enough to keep it below a 5.	4 / 5
Trigger Term Quality	The natural keyword 'FaceUp' / 'FaceUp data' is present and users would say it, but coverage is limited to the one proper noun with no synonyms or variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The FaceUp-specific trigger makes it mostly distinct with minimal conflict risk, but the generic capability phrasing ('manage data, records') leaves minor overlap risk with other data-management 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/faceup/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.