Name: civicrm
Rating: 52.8 (1 reviews)
Author: membranedev

civicrm

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

Quality

59%

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/civicrm/SKILL.md

Quality

Content

57%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 is highly actionable with executable CLI commands and a clear connection workflow, but it is weighed down by an inlined entity reference list and lacks validation guidance for destructive actions. Splitting reference material into bundled files and adding delete-verification steps would improve it.

Suggestions

Move the long entity enumeration and full action catalog into a bundled reference file (e.g. references/entities.md) and keep SKILL.md as an overview with a one-level link.

Add a validation/verification step for destructive actions (e.g. confirm the contact exists and re-fetch after delete-contact to verify it moved to trash).

Trim duplicated "Entity"-prefixed entries from the overview list to reduce token cost without losing information.

Dimension	Reasoning	Score
Conciseness	The CLI instructions are mostly efficient, but the ~80-item CiviCRM Overview entity enumeration (including duplicated "Entity"-prefixed entries) is inlined padding that does not earn its token cost, fitting the score-3 anchor of mostly efficient with some unnecessary content.	3 / 5
Actionability	Concrete, copy-paste-ready bash commands for install, login, connection ensure, action list/run, and proxy requests plus action and flag tables cover the common cases, with only minor gaps such as omitted inputSchema examples, matching score-4.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints and a poll-after-action feedback loop, but destructive operations (delete-contact, delete-contribution) are listed with no validation/verification step, so workflow clarity is capped at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The body is organized into clear sections, but reference material (the full entity list and the popular-actions table) that belongs in a separate file is inlined and no bundle/reference files exist, matching the score-3 anchor of some structure with content that should be separate kept inline.	3 / 5
	Total	13 / 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 is distinctive and explicitly answers both what and when, but its action language is generic rather than concrete and it lacks trigger synonyms. Tightening the action list and adding natural variations would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete CiviCRM actions such as "create and update contacts, record contributions, manage events and memberships".

Add natural trigger variations and synonyms, e.g. "Use when the user mentions CiviCRM, contacts, contributions, donations, events, or memberships".

Keep the explicit "Use when..." clause but make the trigger list more specific to the CiviCRM domain.

Dimension	Reasoning	Score
Specificity	Names the domain ("CiviCRM integration") but the actions "Manage data, records, and automate workflows" are minimal and generic rather than concrete, matching the score-2 anchor better 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 CiviCRM data"), matching the score-4 anchor where both are present though the when could be more specific.	4 / 5
Trigger Term Quality	"CiviCRM" and "interact with CiviCRM data" are relevant natural terms, but common variations or synonyms are missing, fitting the score-3 anchor rather than the comprehensive coverage of 4.	3 / 5
Distinctiveness Conflict Risk	"CiviCRM" is a clear, narrow niche with distinct triggers and minimal overlap with other skills, matching the score-5 anchor.	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/civicrm/SKILL.md
Commit: f484c82

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