adshares
AdShares integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdShares data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill adshares61
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
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description identifies a specific system (AdShares) but fails to describe what concrete capabilities the skill provides. The actions listed are generic placeholders that don't help Claude understand when this skill is more appropriate than other data management skills. The 'Use when' clause is present but too vague to be useful.
Suggestions
Replace generic terms with specific AdShares actions (e.g., 'Create ad campaigns, track impressions, manage publisher accounts, pull revenue reports').
Add specific trigger terms users would naturally say (e.g., 'ad campaigns', 'publisher earnings', 'advertiser dashboard', 'ADS tokens').
Expand the 'Use when' clause with concrete scenarios (e.g., 'Use when the user mentions AdShares, ad campaigns, publisher payouts, or blockchain advertising').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. These are generic terms that could apply to almost any system. | 1 / 3 |
Completeness | Has a 'Use when...' clause which addresses when to use it, but the 'what' portion is extremely vague. The trigger condition 'interact with AdShares data' is present but not specific about what interactions are supported. | 2 / 3 |
Trigger Term Quality | Includes 'AdShares' as a specific keyword users might say, but lacks variations or related terms. 'Data', 'records', and 'workflows' are too generic to serve as effective triggers. | 2 / 3 |
Distinctiveness Conflict Risk | 'AdShares' provides some distinctiveness as a named system, but 'manage data, records, and automate workflows' could overlap with many other integration or data management skills. | 2 / 3 |
Total | 7 / 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 integrating with AdShares via Membrane, with good coverage of connection setup, action discovery, and proxy requests. However, it includes unnecessary introductory content about what AdShares is, has an unhelpful overview section, and lacks validation/error handling guidance that would help Claude recover from common failure scenarios.
Suggestions
Remove or significantly trim the introductory paragraph explaining what AdShares is - Claude already knows this and it wastes tokens.
Either remove the 'AdShares Overview' bullet list or make it actionable by linking each entity to specific actions or documentation.
Add validation steps and error recovery guidance, e.g., 'If connection fails, check `membrane connection list` to verify status' or 'If action run returns an error, use `--verbose` flag to debug'.
Consider adding a troubleshooting section for common issues like authentication failures or expired credentials.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'Adshares is a decentralized advertising marketplace built on blockchain technology' - Claude knows this). The overview section listing entities without actionable content adds little value. However, the CLI commands are reasonably concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection setup, action discovery, and proxy requests are all copy-paste ready with concrete examples and clear flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed for connection setup and action discovery, but there are no validation checkpoints or error recovery guidance. Missing feedback loops for failed connections or action runs, which could leave Claude stuck on errors. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 'AdShares Overview' section with bullet points (Campaign, Targeting, Wallet, etc.) provides no actionable information and isn't linked to detailed docs. The skill is self-contained but could better signal where to find AdShares-specific API documentation. | 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.