action-network
Action Network integration. Manage data, records, and automate workflows. Use when the user wants to interact with Action Network data.
52
58%
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/action-network/SKILL.mdQuality
Discovery
40%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 the platform (Action Network) and includes a 'Use when' clause, but it is far too vague about what the skill actually does. The actions listed ('manage data, records, automate workflows') are generic and could describe virtually any integration skill. It fails to mention Action Network's specific domain (advocacy, organizing, activism) or concrete capabilities.
Suggestions
Replace generic terms like 'manage data, records, and automate workflows' with specific Action Network capabilities such as 'create and manage petitions, events, fundraising pages, email campaigns, and activist contact lists'.
Expand the 'Use when' clause with domain-specific trigger terms like 'advocacy', 'organizing', 'petitions', 'activist data', 'fundraising pages', or 'Action Network API'.
Add concrete action verbs describing what the skill does, e.g., 'Query supporter lists, create events, send bulk emails, track petition signatures, and sync contact data with Action Network.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions. It doesn't specify what kinds of data, what records, or what workflows — these are generic terms that could apply to almost any integration. | 1 / 3 |
Completeness | It has a 'what' (manage data, records, automate workflows) and a 'when' clause ('Use when the user wants to interact with Action Network data'), but the 'when' clause is essentially a restatement of the 'what' and doesn't provide explicit, useful trigger guidance beyond the obvious. | 2 / 3 |
Trigger Term Quality | 'Action Network' is a specific platform name that users would mention, which is helpful. However, the description lacks natural trigger terms users might say such as 'petitions', 'events', 'fundraising', 'advocacy', 'email campaigns', 'activist', or 'organizing' — terms associated with Action Network's actual functionality. | 2 / 3 |
Distinctiveness Conflict Risk | 'Action Network' as a platform name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with any CRM, database, or integration skill. Without mentioning Action Network's specific domain (advocacy, organizing, activism), it's not clearly distinguishable. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — the CLI commands are concrete and the connection state machine is well-documented with clear branching logic. The main weaknesses are unnecessary introductory context about Action Network as a platform and a bulky popular actions table with empty descriptions that could be trimmed or moved to a reference file.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Action Network is — Claude doesn't need to know it's for 'progressive activism' or 'grassroots organizers' to use the API.
Either add descriptions to the popular actions table entries or remove the table entirely, since 'No description' repeated 20 times wastes tokens without adding value.
Move the entity overview list and popular actions table to a separate REFERENCE.md file to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Action Network is (progressive activism platform, grassroots organizers, etc.) is unnecessary context Claude doesn't need. The entity overview list and popular actions table with empty descriptions add bulk. However, the CLI commands and workflow steps are reasonably efficient. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and parameter placeholders. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), polling instructions with --wait flag, and clear next steps for each state. The overall flow from install → auth → connect → discover → run is well-structured with validation checkpoints. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the popular actions table (20 rows, most with 'No description') and the entity overview list could be in a separate reference file. There are no bundle files or references to external files for advanced topics, and the document is somewhat long for a single SKILL.md. | 2 / 3 |
Total | 10 / 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.