action-builder
Action Builder integration. Manage data, records, and automate workflows. Use when the user wants to interact with Action Builder data.
61
72%
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-builder/SKILL.mdQuality
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 has a proper structure with an explicit 'Use when' clause, which is good. However, it suffers from vague action descriptions — 'manage data, records, and automate workflows' could apply to dozens of tools. The description would benefit from more specific concrete actions and more distinctive trigger terms tied to Action Builder's unique capabilities.
Suggestions
Replace generic actions with specific concrete operations like 'create/update/query records, configure automated workflows, manage tags and custom fields in Action Builder'.
Add more distinctive trigger terms that users would naturally say, such as specific Action Builder entity types, 'Action Network', or common task phrases like 'look up activist records' or 'set up an Action Builder automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Action Builder) and some actions ('manage data, records, and automate workflows'), but these are fairly generic and not comprehensive — it doesn't specify concrete actions like 'create records', 'update fields', 'trigger automations', or 'query datasets'. | 2 / 3 |
Completeness | Answers both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Action Builder data), with an explicit 'Use when' clause providing trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'Action Builder' as a key trigger term and mentions 'data', 'records', and 'workflows', but misses common variations or natural phrases users might say (e.g., 'Action Builder API', 'AB records', 'action network', specific entity types). The generic terms 'data' and 'workflows' could match many other skills. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Action Builder' name provides some distinctiveness, but terms like 'manage data', 'records', and 'automate workflows' are very generic and could easily overlap with database, CRM, or general automation skills. Without more specific triggers tied to Action Builder's unique features, there's moderate conflict risk. | 2 / 3 |
Total | 9 / 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, actionable skill with well-structured CLI workflows and clear state-handling logic for connections. Its main weakness is some unnecessary verbosity in the introduction and overview sections that explain concepts Claude already knows. The content would benefit from trimming the preamble and potentially splitting the popular actions reference into a separate file.
Suggestions
Remove the introductory paragraph explaining what Action Builder is and what citizen developers are — Claude doesn't need this context.
Either flesh out the Overview section with actionable details about each concept (Action, Step, Variable, etc.) or remove it entirely, as the bare list adds little value.
Consider moving the Popular Actions table to a separate reference file (e.g., ACTIONS.md) to keep the main skill focused on workflow instructions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Action Builder is ('no-code/low-code platform...citizen developers...without extensive coding knowledge') is unnecessary context for Claude. The popular actions table is useful but bulky. The overview section listing concepts (Action, Step, Variable, etc.) without explanation adds little value. Overall mostly efficient but has notable padding. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action search, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and JSON output options. | 3 / 3 |
Workflow Clarity | The connection workflow is well-sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and clear branching logic. The polling/retry loop for BUILDING state and the client action handling provide good feedback loops. The overall flow from install → auth → connect → search → run is clearly sequenced. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's a fairly long monolithic document with no references to supporting files. The popular actions table and proxy request details could be split into separate reference files. However, with no bundle files provided, the inline approach is acceptable though not optimal. | 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.