CtrlK
BlogDocsLog inGet started
Tessl Logo

givingfuel

GivingFuel integration. Manage Campaigns, Donors, Funds. Use when the user wants to interact with GivingFuel data.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/givingfuel/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 skill body is highly actionable with executable commands and a clear sequenced workflow including feedback loops for connection state, supported by good structural organization with only minor conciseness and disclosure gaps.

Suggestions

Tighten the opening overview paragraph and "Best practices" prose to remove minor padding.

Move the long "Popular actions" table into a separate reference file and link to it from the body to improve progressive disclosure.

Add an explicit validation/checkpoint note for proxy and write operations (create/update/delete) to strengthen workflow clarity on destructive paths.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and little over-explanation of known concepts, though the overview paragraph and best-practices prose contain minor padding that could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready `membrane` commands with flags and `--json` appear throughout and cover the common install/auth/connect/search/run/proxy cases.

5 / 5

Workflow Clarity

A clear sequenced flow (install → auth → connect → search → run → proxy) with explicit state handling and polling feedback loops for the connection build, with only minor validation gaps on the proxy/destructive path.

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested references; the inlined "Popular actions" table is the main content that could be split into a separate reference file, leaving minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

66%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 clear and explicitly pairs a what-and-when structure around a distinct named platform, but the verbs and trigger-term coverage are somewhat generic and could be enriched with more natural synonyms.

Suggestions

Replace the generic verb "Manage" with more specific actions (e.g., "Create and manage Campaigns, list and segment Donors, reconcile Funds").

Add natural trigger terms users would say, such as "donations", "fundraising", "donors", or "nonprofit campaigns".

Tighten the "Use when" clause with concrete scenarios (e.g., "Use when the user wants to query donors, pull donation transactions, or manage GivingFuel campaigns").

DimensionReasoningScore

Specificity

The description names the domain and three concrete entities ("Manage Campaigns, Donors, Funds") but the verb is generic ("Manage") and coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than a higher level.

3 / 5

Completeness

It has both a clear "what" ("Manage Campaigns, Donors, Funds") and an explicit "when" clause ("Use when the user wants to interact with GivingFuel data"), though the when is slightly generic, fitting the level-5 below threshold for full explicitness.

4 / 5

Trigger Term Quality

The trigger term "GivingFuel data" / "GivingFuel" is a relevant proper-noun keyword a user would say, but common natural variations (donations, fundraising, campaigns) and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Niched to a named platform (GivingFuel) with distinct, platform-specific triggers, giving minimal conflict risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.