Name: funraise
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

funraise

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

Quality

64%

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/funraise/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 delivers strong executable guidance with a well-sequenced, checkpointed connection workflow and a useful flag reference, scoring well on actionability and workflow clarity. It loses points mainly on conciseness (platform boilerplate and motivational asides) and could offload the action catalog to a reference file for better progressive disclosure.

Suggestions

Trim the opening platform description and the "so you can focus on the integration logic rather than auth plumbing" aside; Claude does not need motivational framing.

Fix the step numbering: label "Step 1: Connect" and "Step 2: Search and run actions" so the "skip to Step 2" references are unambiguous.

Move the Popular actions / action-listing material into a separate reference file and link to it from the overview to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with code blocks and a flag table, but includes some padding Claude does not need — e.g. "Funraise is a fundraising and donor management platform... Nonprofits of various sizes use Funraise to streamline their fundraising efforts" and "so you can focus on the integration logic rather than auth plumbing" — fitting the "mostly efficient but includes some unnecessary explanation" anchor rather than 4 which expects only minor trim.	3 / 5
Actionability	Concrete, copy-pasteable commands appear throughout (install, login, connection ensure, action list/run, request with a full flag table), matching anchor 4; it is not 5 because several examples rely on placeholder tokens like CONNECTION_ID and omit a worked end-to-end example covering the common case.	4 / 5
Workflow Clarity	The connection setup is a clear sequence with polling checkpoints and explicit state branches (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), placing it at anchor 4; it is not 5 because the numbering is inconsistent ("Step 2" is referenced but no Step 1 is labeled, and "1b" appears without a 1a) and error-recovery feedback loops are only sketched.	4 / 5
Progressive Disclosure	The body is well sectioned with clear headers (Overview, Working with Funraise, Popular actions, Best practices) and an external docs link, with content appropriately kept inline since no bundle files exist; it sits at anchor 4 rather than 5 because nothing is split into reference files and the action-listing material could live in a separate reference.	4 / 5
	Total	15 / 20 Passed

Description

61%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 correctly identifies a distinct, named niche and includes an explicit Use-when clause, but its capability list is generic ("manage data, records, automate workflows") and lacks the natural trigger synonyms users would say. Tightening the action verbs and adding donor/fundraising/donation keywords would raise specificity and trigger quality.

Suggestions

Replace generic verbs with Funraise-specific concrete actions, e.g. "Create and update donors, record donations, build fundraising pages, and pull reports."

Add natural trigger terms users actually say: "Use when the user wants to manage donors, log donations, run fundraising campaigns, or pull Funraise reports."

Avoid repeating "Funraise data" verbatim; vary the trigger phrasing to cover donations, giving, and nonprofit workflows.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain but the actions are generic ("manage", "automate") with no concrete verbs tied to Funraise-specific capabilities, matching the "names the domain but actions are minimal or generic" anchor rather than 3 which requires concrete actions.	2 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Funraise data"), placing it at anchor 4 since both are present though the "what" is somewhat generic; it is not 5 because the trigger phrases lack concrete specificity.	4 / 5
Trigger Term Quality	The only natural keyword is "Funraise" repeated in "interact with Funraise data"; common synonyms a user would actually say (donations, donors, fundraising, nonprofit, giving) are absent, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"Funraise" is a named platform with a narrow, explicit trigger ("interact with Funraise data"), giving it a clear niche with minimal overlap risk against other skills, matching the anchor-5 example.	5 / 5
	Total	14 / 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/funraise/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.