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

kindful

Kindful integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kindful 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/kindful/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 a strong, command-driven integration guide with copy-paste Membrane CLI examples and a clear connection workflow including state-based validation. Its main weakness is token bloat from the oversized entity overview list and background intro paragraph.

Suggestions

Trim the 'Kindful Overview' list to the entities actually exposed as actions (drop Logout, Settings, Profile, Billing, Support, SEO, Blogs, etc.), or move the full list to a references/ file.

Tighten the intro paragraph to one sentence stating Kindful is a nonprofit CRM/fundraising platform, removing the redundant second and third sentences.

Fix the dangling 'Step 2' reference by adding an explicit numbered 'Step 2' header or rewording to 'skip to Searching for actions'.

Dimension	Reasoning	Score
Conciseness	The operational CLI sections are lean, but the intro background paragraph and the ~60-item 'Kindful Overview' list (including irrelevant entries like Logout, Billing, SEO, and Blogs) add noticeable padding; not a 4 because of that bloat.	3 / 5
Actionability	Copy-paste-ready commands with real flags cover the full workflow (login, connection ensure, polling, action list/run with JSON input, proxy, and a flag table), matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	Clear sequence with an explicit state-polling validation loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-poll); not a 5 due to a dangling 'Step 2' reference and no error-recovery loop for action execution.	4 / 5
Progressive Disclosure	No bundle files exist, so this is a single-file skill with well-organized headers and logical flow; the oversized inline overview list is a minor organization gap that keeps it at 4 rather than 5.	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 is structurally sound: it states the domain, lists a few actions, and includes an explicit 'Use when' trigger. Its main weakness is generic action language and missing domain-specific trigger terms (donors, donations, fundraising) that would aid recall.

Suggestions

Replace generic verbs with concrete Kindful capabilities, e.g. 'Manage donors, track donations, run campaigns, and automate fundraising workflows.'

Add natural domain trigger terms to the 'Use when' clause, e.g. 'Use when the user wants to manage donors, donations, campaigns, or fundraising data in Kindful.'

Mention the CRM/fundraising/nonprofit niche in the description to improve distinctiveness and trigger recall.

Dimension	Reasoning	Score
Specificity	Names the domain ('Kindful integration') but the actions 'Manage data, records, and automate workflows' are generic verbs over generic nouns with no concrete capabilities; not a 3 because the actions are not concrete like 'extracts content'.	2 / 5
Completeness	Explicitly answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Kindful data'); the 'when' could be more concrete, so it is not a 5.	4 / 5
Trigger Term Quality	'Kindful' is a strong natural keyword and an explicit trigger is present, but the description omits the domain terms users actually say (donors, donations, fundraising, CRM, nonprofit); missing common synonyms keeps it at 3 rather than 4.	3 / 5
Distinctiveness Conflict Risk	The unique product name 'Kindful' gates the trigger, giving low conflict risk, while the generic 'manage data, records' phrasing creates only minor overlap with related CRM 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/kindful/SKILL.md
Commit: f484c82

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