actblue
Actblue integration. Manage data, records, and automate workflows. Use when the user wants to interact with Actblue data.
49
53%
Does it follow best practices?
Impact
—
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
57%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 benefits from naming a specific platform (Actblue) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what concrete actions the skill performs. The vague terms 'manage data, records, and automate workflows' could describe virtually any integration skill, and the description misses an opportunity to include domain-relevant trigger terms like donations, fundraising, or donor records.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific actions such as 'query donation records, export donor lists, track fundraising totals, sync contribution data'.
Add domain-specific trigger terms users would naturally say, such as 'donations', 'fundraising', 'donors', 'political contributions', 'campaign finance', or 'contribution data'.
Expand the 'Use when' clause with more specific triggers, e.g., 'Use when the user mentions Actblue, political donations, fundraising data, donor records, or campaign contributions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what kind of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Actblue data). The explicit 'Use when...' clause is present, though both parts are quite vague. | 3 / 3 |
Trigger Term Quality | It includes 'Actblue' which is a strong domain-specific keyword users would naturally say. However, it lacks natural variations or related terms users might use (e.g., 'donations', 'fundraising', 'political contributions', 'donor data', 'campaign finance'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Actblue' is a distinctive product name that helps differentiate this skill, but the generic 'manage data, records, and automate workflows' language could overlap with other integration or data management skills. The Actblue keyword alone provides moderate distinctiveness. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable CLI commands and covers the full workflow from setup to execution, which is its primary strength. However, it is significantly bloated by unnecessary explanations of what ActBlue is and verbose descriptions of connection states that could be condensed. The content would benefit from trimming the introductory context Claude already knows and splitting detailed reference material into separate files.
Suggestions
Remove the entire opening paragraph explaining what ActBlue is — Claude already knows this. Start directly with the Membrane CLI integration instructions.
Condense the CLIENT_ACTION_REQUIRED state documentation into a compact reference table rather than nested bullet descriptions.
Move the proxy request flags table and detailed connection state machine into a separate REFERENCE.md file, keeping only the most common usage patterns inline.
Add a brief validation/error-handling step after `membrane action run` to guide recovery when actions fail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what ActBlue is, who uses it, and what it does — all information Claude already knows. The Membrane CLI setup, authentication flow, and connection state machine are verbose with extensive explanations of concepts like OAuth and state transitions that could be significantly condensed. | 1 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installing the CLI, authenticating, creating connections, searching for actions, running actions, and making proxy requests. The flag reference table and JSON input examples are specific and executable. | 3 / 3 |
Workflow Clarity | The connection setup workflow has a clear sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, errors), but there are no explicit validation checkpoints or feedback loops for error recovery when running actions or making proxy requests. The overall flow from install → auth → connect → discover → run is present but could be more explicitly sequenced. | 2 / 3 |
Progressive Disclosure | The content is structured with headers and sections, but it's a monolithic document with no references to supporting files. The proxy request options table, the full connection state machine documentation, and the detailed CLIENT_ACTION_REQUIRED breakdown could be split into separate reference files to keep the main skill leaner. | 2 / 3 |
Total | 8 / 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
f484c82
- 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.