actblue
Actblue integration. Manage data, records, and automate workflows. Use when the user wants to interact with Actblue data.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/actblue/SKILL.mdQuality
Discovery
67%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 follows the structure with an explicit 'Use when...' clause and identifies the Actblue platform. However, it lacks specific concrete actions (what exactly can be done with Actblue?) and misses natural trigger terms users might say when needing fundraising/donation platform help. The generic verbs 'manage' and 'automate' don't help Claude understand the skill's actual capabilities.
Suggestions
Replace vague actions with specific Actblue capabilities (e.g., 'Query donation records, export contributor lists, sync fundraising data, generate campaign reports').
Add natural trigger terms users would say: 'donations', 'fundraising', 'campaign contributions', 'donor data', 'political fundraising'.
Clarify the unique Actblue context to distinguish from generic CRM/data skills (e.g., 'Democratic fundraising platform' or 'political donation processing').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Actblue) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions. 'Manage data' and 'automate workflows' are vague compared to examples like 'extract text, fill forms, merge documents'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Actblue data'). Has an explicit 'Use when...' clause with trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Actblue' and 'Actblue data' as trigger terms, which are relevant for users who know the platform name. However, it lacks natural variations or related terms users might say (e.g., 'donations', 'fundraising', 'campaign contributions', 'donor management'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Actblue' is a specific platform which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other CRM or data management skills. The description doesn't clarify what makes Actblue-specific tasks unique. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid actionable CLI commands for Membrane-based ActBlue integration, but wastes tokens explaining what ActBlue is (Claude knows this). The workflow lacks validation checkpoints and error handling guidance, and the content could benefit from better progressive disclosure with links to detailed references.
Suggestions
Remove the opening paragraph explaining what ActBlue is - Claude already knows this context
Add validation steps after key commands (e.g., 'Verify connection succeeded by checking output for connectionId')
Include error handling guidance: what to do when membrane commands fail or return unexpected output
Consider linking the 'Actblue Overview' entities to detailed documentation or examples rather than listing them without context
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what ActBlue is wastes tokens on information Claude already knows. The CLI setup and connection instructions are reasonably efficient, but some sections like 'Best practices' contain verbose explanations that could be tightened. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags, JSON output options, and parameter passing examples. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection, but lacks explicit validation checkpoints. No feedback loops for error recovery when commands fail, and the workflow jumps between setup, connection checking, and action discovery without clear sequencing. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The 'Actblue Overview' section lists entities without linking to detailed documentation, and there's no reference to external files for advanced usage or API reference. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
d19a82b
- 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.