action-builder
Action Builder integration. Manage data, records, and automate workflows. Use when the user wants to interact with Action Builder data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill action-builder72
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
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 adequately identifies the Action Builder integration and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are quite generic ('manage data, records, automate workflows') and don't convey the specific actions or features unique to Action Builder. The description would benefit from more concrete examples of what can be done.
Suggestions
Add more specific concrete actions unique to Action Builder (e.g., 'create supporter records, manage campaigns, build activist lists, track engagement metrics')
Expand trigger terms to include natural variations users might say (e.g., 'Action Network', 'campaign management', 'supporter database', 'activist CRM')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Action Builder) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what kinds of data, records, or workflows. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Action Builder data') with a clear trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'Action Builder' as a key term users would say, plus generic terms like 'data', 'records', 'workflows'. Missing variations or more specific trigger terms that users might naturally use (e.g., campaign data, supporter records, specific Action Builder features). | 2 / 3 |
Distinctiveness Conflict Risk | 'Action Builder' is a specific product name which helps distinctiveness, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other CRM or data management skills. | 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 Action Builder integration with good concrete examples. However, it wastes tokens on introductory explanations Claude doesn't need, and lacks validation/error handling guidance for the multi-step connection and action workflows. The structure is adequate but could benefit from splitting reference content into separate files.
Suggestions
Remove the opening paragraph explaining what Action Builder is - Claude doesn't need this context
Add validation steps after key operations (e.g., 'Verify connection succeeded by running membrane connection list' or 'Check output.success field before proceeding')
Move the popular actions table to a separate ACTIONS_REFERENCE.md file and link to it
Add error handling guidance for common failures (auth timeout, invalid connection ID, action not found)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Action Builder is and who uses it is unnecessary context Claude doesn't need. The rest is reasonably efficient but could be tightened - the overview section with bullet points adds little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax, specific flags, and copy-paste ready examples. The action table with keys and descriptions, plus the proxy request options table, give concrete guidance. | 3 / 3 |
Workflow Clarity | Steps are listed clearly for setup and connection, but lacks 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 organized with clear sections, but the popular actions table could be in a separate reference file. Links to external docs exist but no internal file references for advanced topics or detailed 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 | |
- 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.