adshares
AdShares integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdShares 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/adshares/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 benefits from naming a specific platform (AdShares) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what concrete actions the skill performs. The generic phrases 'manage data, records, and automate workflows' could apply to virtually any integration skill, making it hard for Claude to confidently select this skill over others.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific actions (e.g., 'create ad campaigns, track impressions, manage publisher accounts, query blockchain transactions').
Add more natural trigger terms users might say, such as 'ad campaigns', 'ADS token', 'decentralized advertising', 'ad network', or 'publisher/advertiser management'.
Clarify the domain context—mention that AdShares is a decentralized ad network (if applicable) to help distinguish it from other integration skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. There are no specific capabilities listed—what kind of data? What workflows? What does 'manage' entail? | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with AdShares data) with an explicit trigger clause, even though both parts are vague in substance. | 3 / 3 |
Trigger Term Quality | It includes 'AdShares' as a relevant keyword, which is domain-specific and useful. However, it lacks natural variations or specific terms users might say (e.g., ad campaigns, ad inventory, publisher, advertiser, blockchain ads, ADS token). | 2 / 3 |
Distinctiveness Conflict Risk | 'AdShares' is a specific platform name which helps distinguish it, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many integration or data management 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 skill provides solid, actionable CLI-based guidance for integrating with AdShares via Membrane, with a well-structured connection workflow including state handling and error recovery. The main weaknesses are unnecessary introductory context about what Adshares is, a stub overview section that adds no value, and a somewhat monolithic structure that could benefit from splitting detailed reference material into separate files.
Suggestions
Remove the introductory paragraph explaining what Adshares is — Claude already knows this, and the description frontmatter covers it.
Either flesh out the 'AdShares Overview' section (Campaign, Wallet, Transaction, User) with actionable details or remove it entirely, as the current stub adds no value.
Consider extracting the proxy request options table and connection state machine details into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adshares is (decentralized advertising marketplace, blockchain, etc.) is unnecessary context Claude already knows. The Membrane CLI instructions are mostly efficient but include some redundant explanations like 'so you can focus on the integration logic rather than auth plumbing.' The proxy section and best practices are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands throughout — from installation, authentication, connection setup, action discovery, action execution, to proxy requests. Commands are copy-paste ready with clear flag descriptions and a useful options table for proxy requests. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state-based branching (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR). There are clear polling/retry loops for BUILDING state, and the workflow handles error states with guidance on what to check. The overall flow from install → auth → connect → discover actions → run actions is well-structured. | 3 / 3 |
Progressive Disclosure | The content is reasonably organized with clear sections, but it's somewhat monolithic — the proxy request details, connection state machine documentation, and best practices could potentially be split into separate files. The 'AdShares Overview' section listing Campaign/Targeting/Wallet/Transaction/User entities is a stub that adds no value without further content or references. No bundle files are provided to offload detail. | 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.