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

pledgeling

Pledgeling integration. Manage data, records, and automate workflows. Use when the user wants to interact with Pledgeling 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pledgeling/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 body is a well-structured, actionable guide with concrete commands and a strong connection-state feedback loop. Its weakest point is conciseness, weighed down by marketing language and explanatory padding Claude does not need.

Suggestions

Trim marketing and rationale commentary — drop the Pledgeling platform intro sentence and phrases like 'so you can focus on the integration logic rather than auth plumbing'.

Fix the step numbering so '1b' has a matching '1a' and the referenced 'Step 2' has an explicit labeled header.

Add one fully-resolved example of an action run with a concrete actionId and input payload to lift actionability toward copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with code blocks and a flag table, but retains unnecessary commentary such as the marketing intro, 'so you can focus on the integration logic rather than auth plumbing', and 'burn less tokens and make communication more secure'.	3 / 5
Actionability	It provides concrete, executable CLI commands (install, login, connection ensure, action list/run, request) with a clear flag table; minor gaps are limited to placeholders like CONNECTION_ID and actionId that the user must substitute.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state handling and feedback loops (poll until READY, re-poll after user action, handle CONFIGURATION_ERROR), but step numbering is slightly inconsistent — a '1b' header and references to an unlabeled 'Step 2'.	4 / 5
Progressive Disclosure	Content is organized into clear headed sections (install, auth, connect, search, run, proxy, best practices) in a single appropriately sized file with no need for external references; minor gaps only in that the proxy reference or best practices could optionally be split out.	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 is functional and explicitly covers both what and when, anchored by a distinctive product name. Its main weakness is generic, non-concrete action language that undersells the specific Pledgeling capabilities.

Suggestions

Replace generic verbs with concrete Pledgeling actions, e.g. 'Create and manage campaigns, list donations, and browse causes'.

Expand the trigger clause with natural user phrases such as 'charitable giving', 'donations', or 'Pledgeling campaigns'.

Tighten the 'when' to reference specific intents (e.g. managing campaigns or retrieving donation records) rather than 'interact with Pledgeling data'.

Dimension	Reasoning	Score
Specificity	The description names the domain (Pledgeling) but its actions — 'Manage data, records, and automate workflows' — are generic verbs rather than concrete Pledgeling capabilities like creating campaigns or listing donations.	2 / 5
Completeness	It states both what the skill does ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with Pledgeling data'), though the when clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	It includes relevant keywords ('Pledgeling', 'data', 'records', 'workflows') and a natural trigger phrase, but lacks common variations or synonyms a user might actually say.	3 / 5
Distinctiveness Conflict Risk	The named platform 'Pledgeling' gives it a clear niche with mostly distinct triggers, but the generic data/records framing 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/pledgeling/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.