Name: piggy
Rating: 64 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

piggy

Piggy integration. Manage Accounts, Budgets, Goals. Use when the user wants to interact with Piggy data.

Quality

76%

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/piggy/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.

A highly actionable CLI-integration skill with copy-paste commands and a well-validated connection workflow. The main weaknesses are minor intro padding that assumes Claude lacks context, and the absence of verification steps before destructive action execution.

Suggestions

Trim the introductory paragraph ("Piggy is a personal finance app...") and the "so you can focus on the integration logic rather than auth plumbing" clause; Claude does not need Piggy's marketing context.

Add a verification/check step before running actions that mutate Accounts, Budgets, or Goals (e.g. confirm the action's inputSchema and dry-run intent before `membrane action run`) to satisfy the destructive-operation workflow cap.

Consider moving the proxy flags table and extended connection-state handling into a reference file, keeping SKILL.md as a lean overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but includes unnecessary padding Claude does not need ("Piggy is a personal finance app that helps users track their spending..." and "so you can focus on the integration logic rather than auth plumbing"); not a 4 because these explanatory sentences are noticeable rather than minor.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run", "membrane request") with a flags table and JSON-output guidance covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has explicit validation checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop (poll again after user action); not a 5 because running actions that can modify Accounts, Budgets, or Goals lacks a pre-flight verification step for destructive operations.	4 / 5
Progressive Disclosure	Single-file skill (~90 lines) with well-organized sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no need for external bundle files; not a 5 because it exceeds the under-50-lines simple-skill threshold and a few subtopics (e.g. the proxy flag table) could optionally live in a reference file.	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A concise, well-structured description that states both capability and an explicit use-when trigger in third person. Specificity and trigger coverage are solid but rely on one generic verb ("Manage") and a single app name, leaving minor room for more concrete action verbs and synonyms.

Dimension	Reasoning	Score
Specificity	"Manage Accounts, Budgets, Goals" names the domain plus three concrete entities, matching the anchor that lists several specific actions with only minor generic-verb gaps; not a 5 because "Manage" is a single generic verb rather than distinct CRUD-style actions.	4 / 5
Completeness	It answers both "what" ("Piggy integration. Manage Accounts, Budgets, Goals.") and "when" ("Use when the user wants to interact with Piggy data.") in third person; not a 5 because the "when" trigger ("interact with Piggy data") is broad rather than enumerating concrete user phrasings.	4 / 5
Trigger Term Quality	Natural terms "Piggy", "Accounts, Budgets, Goals", and "Piggy data" cover the app's entity vocabulary users would actually say; not a 5 because no synonyms or surface variations beyond the single app name are offered.	4 / 5
Distinctiveness Conflict Risk	"Piggy integration" ties the skill to a specific named app with distinct entity triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 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/piggy/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.