action-network
Action Network integration. Manage data, records, and automate workflows. Use when the user wants to interact with Action Network data.
61
52%
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/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 names the platform (Action Network) and includes a 'Use when' clause, but is otherwise extremely vague. It fails to describe any specific capabilities of the Action Network platform (e.g., managing petitions, events, fundraising, contacts, email campaigns) and uses generic terms that could apply to virtually any data integration skill.
Suggestions
Replace 'manage data, records, and automate workflows' with specific Action Network capabilities like 'create and manage petitions, events, fundraising pages, email campaigns, and activist contact lists'.
Expand the 'Use when' clause with natural trigger terms users would say, such as 'Use when the user mentions Action Network, activist organizing, petition management, event RSVPs, advocacy campaigns, or fundraising pages'.
Add Action Network-specific terminology (e.g., 'actions', 'tags', 'wrappers', 'forms') to improve distinctiveness from generic CRM or workflow automation skills.
| 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 has a 'Use when' clause, but the trigger is extremely vague ('interact with Action Network data'). The 'what' portion is also weak — 'manage data, records, and automate workflows' doesn't meaningfully describe specific capabilities. The 'when' clause essentially just restates the 'what' rather than providing distinct trigger guidance. | 2 / 3 |
Trigger Term Quality | 'Action Network' is a specific platform name that users would mention, but the description lacks natural trigger terms like 'petitions', 'events', 'fundraising pages', 'activist contacts', 'RSVP', 'advocacy', or 'organizing' that users working with Action Network would naturally use. | 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 automation skill. Without Action Network-specific terminology, the distinction relies entirely on the platform name. | 2 / 3 |
Total | 7 / 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.
The skill provides solid, actionable CLI commands for integrating with Action Network via Membrane, with good coverage of the full workflow from setup to execution. However, it suffers from unnecessary introductory context about what Action Network is, a low-value entity list and actions table (with empty descriptions), and could benefit from clearer sequential workflow steps with validation checkpoints. The content would be stronger if trimmed and restructured with progressive disclosure.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Action Network is — Claude doesn't need this context to use the integration.
Either add descriptions to the popular actions table entries or remove the table entirely, as 'No description' rows waste tokens without adding value.
Add explicit validation/verification steps after running actions (e.g., check output field, handle errors) to create a complete feedback loop.
Move the entity overview list and popular actions table to a separate reference file, keeping SKILL.md focused on the core workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Action Network is (a digital organizing platform for progressive activism) is unnecessary context Claude doesn't need. The entity overview list adds little value without explaining how it maps to actions. The popular actions table with 'No description' entries is low-value padding. However, the CLI commands and workflow sections are reasonably efficient. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, and running actions with parameters. The commands include specific flags (--json, --wait, --connectionId) and clear parameter placeholders. | 3 / 3 |
Workflow Clarity | The workflow follows a logical sequence (install → authenticate → connect → discover → run), but there's no explicit validation or error-handling feedback loop for running actions. The action creation section does include polling and state checking (READY vs CONFIGURATION_ERROR), which is good, but the overall flow lacks numbered sequential steps and verification checkpoints after running actions. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear headers, but it's somewhat monolithic — the entity overview list and popular actions table could be in separate reference files. The link to official docs is good, but there are no references to supplementary files for advanced usage patterns or detailed schema information. | 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
56d7336
- 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.