adbutler
AdButler integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdButler data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adbutler75
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 has good structure with explicit 'Use when' guidance and clear product-specific targeting (AdButler). However, it lacks specificity in describing concrete actions (what exactly can be managed?) and could benefit from more natural trigger terms related to advertising workflows that users might mention.
Suggestions
Replace vague actions with specific capabilities like 'create campaigns, manage ad zones, track impressions, configure banners, pull analytics reports'
Add natural trigger terms users might say: 'ad serving', 'campaigns', 'zones', 'banners', 'ad analytics', 'advertising platform'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AdButler) and mentions general actions ('Manage data, records, and automate workflows'), but these are not concrete specific actions. 'Manage data' and 'automate workflows' are vague compared to examples like 'fill forms, merge documents'. | 2 / 3 |
Completeness | Explicitly answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with AdButler data'). Has a clear 'Use when...' clause with trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes 'AdButler' as a key trigger term and 'AdButler data', but lacks natural variations users might say (e.g., 'ad serving', 'ad management', 'campaigns', 'zones', 'banners', specific AdButler features). | 2 / 3 |
Distinctiveness Conflict Risk | 'AdButler' is a specific product name that creates a clear niche. Unlikely to conflict with other skills since it explicitly targets AdButler integration rather than generic ad management. | 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 AdButler integration via Membrane, with good concrete examples. However, it includes unnecessary platform explanations, lacks validation checkpoints in workflows, and could better organize content through progressive disclosure to external references.
Suggestions
Remove the introductory paragraph explaining what AdButler is - Claude already knows this context
Add validation steps after key operations (e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failure scenarios (auth failures, invalid action IDs)
Consider moving the proxy request options table to a separate REFERENCE.md file and linking to it
| 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 setup instructions are reasonably efficient but could be tighter. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands throughout with clear syntax examples. Commands are copy-paste ready with proper flags and JSON output options documented in a useful table format. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack explicit validation checkpoints. The workflow for connecting and running actions is sequential but doesn't include error recovery or verification steps (e.g., confirming connection succeeded before proceeding). | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The AdButler Overview section lists entities without linking to detailed documentation. Could benefit from separating advanced proxy usage or action discovery into referenced files. | 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.