adbutler
AdButler integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdButler data.
58
67%
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/adbutler/SKILL.mdQuality
Discovery
57%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 integration target (AdButler) and includes a 'Use when' clause, but the capabilities listed are extremely generic and could apply to virtually any data integration. It fails to mention any AdButler-specific concepts like ad zones, campaigns, publishers, or ad serving, which would help both with specificity and trigger term coverage.
Suggestions
Replace generic terms like 'manage data, records, and automate workflows' with AdButler-specific actions such as 'create and manage ad zones, campaigns, placements, publishers, and banners'.
Add natural trigger terms users would say, such as 'ad serving', 'ad management', 'campaigns', 'zones', 'banners', or 'placements'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions AdButler, ad zones, ad campaigns, ad placements, or needs to manage ad serving configurations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to AdButler. It doesn't mention what kinds of data, records, or workflows (e.g., ad zones, campaigns, publishers, placements). | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with AdButler data), with an explicit 'Use when...' clause. Though both parts are vague, the structure is complete. | 3 / 3 |
Trigger Term Quality | It includes 'AdButler' which is the key brand trigger term, and 'data' and 'workflows' are somewhat relevant. However, it misses natural terms users might say like 'ads', 'ad serving', 'campaigns', 'zones', 'banners', 'placements', or 'publishers'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many integration skills. However, the explicit mention of 'AdButler' as a proper noun provides some distinctiveness that prevents conflicts with non-AdButler skills. | 2 / 3 |
Total | 8 / 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 clear executable commands and a well-structured connection workflow with proper state handling and feedback loops. Its main weakness is moderate verbosity—the introductory paragraph explains what AdButler is (unnecessary for Claude), and some sections could be more concise. The content is well-organized but could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what AdButler is—Claude already knows this, and the official docs link suffices.
Consider moving the detailed proxy request flags table and connection state handling details into a separate reference file to keep SKILL.md leaner.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'AdButler is an ad server platform used to manage and serve online advertisements...') that Claude already knows. The Membrane CLI instructions are reasonably efficient but could be tightened—some sections like the detailed CLIENT_ACTION_REQUIRED breakdown and the best practices section add moderate verbosity. | 2 / 3 |
Actionability | The skill provides concrete, 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 JSON output options. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check state). The progression from install → authenticate → connect → discover actions → run actions is well-structured with validation at each stage. | 3 / 3 |
Progressive Disclosure | The content is organized with clear sections and headers, but it's somewhat monolithic—the detailed connection state handling, proxy request documentation, and best practices could potentially be split into referenced files. However, with no bundle files provided, the single-file approach is acceptable though not optimal for the content volume. | 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.