action-network
Action Network integration. Manage data, records, and automate workflows. Use when the user wants to interact with Action Network data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill action-network75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 successfully identifies a specific platform (Action Network) and includes an explicit 'Use when' clause, making it complete and distinctive. However, it lacks specific concrete actions beyond generic terms like 'manage data' and 'automate workflows', and could benefit from more natural trigger terms that users familiar with Action Network would use.
Suggestions
Replace generic actions with specific capabilities like 'create events, manage petitions, sync contact lists, export donation records, send email campaigns'
Add natural trigger terms users might say such as 'activist database', 'organizing tool', 'petition signatures', or 'advocacy campaigns'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Action Network) and mentions general actions ('Manage data, records, and automate workflows'), but lacks specific concrete actions like 'create events', 'sync contacts', or 'export donation records'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Action Network data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Action Network' as a key trigger term, but misses natural variations users might say like 'activist database', 'organizing platform', 'petition management', or specific Action Network features. | 2 / 3 |
Distinctiveness Conflict Risk | 'Action Network' is a specific platform name that creates a clear niche; unlikely to conflict with other skills since it explicitly targets this particular integration. | 3 / 3 |
Total | 10 / 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 Action Network integration via Membrane, with a useful quick-reference table of popular actions. However, it wastes tokens explaining what Action Network is, lacks validation checkpoints in workflows, and could benefit from better progressive disclosure by splitting reference content into separate files.
Suggestions
Remove the opening paragraph explaining what Action Network is - Claude already knows this context
Add validation steps after connection creation (e.g., 'Verify connection: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failures like authentication timeout or invalid action IDs
Move the entity overview and popular actions table to a separate REFERENCE.md file with a clear link
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Action Network is wastes tokens on context Claude doesn't need. The entity overview list and some explanatory text could be trimmed, though the CLI commands and action tables are appropriately concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, a useful action reference table, and concrete examples for running actions with JSON parameters. The proxy request section includes practical flag documentation. | 3 / 3 |
Workflow Clarity | Steps for setup and connection are listed but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded before proceeding. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but the skill is somewhat monolithic. The entity overview and popular actions table could be split to separate reference files, and there are no links to external detailed documentation within the skill. | 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 | |
- 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.