adshares
AdShares integration. Manage data, records, and automate workflows. Use when the user wants to interact with AdShares data.
68
61%
Does it follow best practices?
Impact
Pending
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 of capabilities. The actions described ('manage data, records, and automate workflows') are generic boilerplate that could apply to virtually any integration skill, providing no meaningful guidance on what this skill actually does with AdShares.
Suggestions
Replace vague actions with specific AdShares operations, e.g., 'Create and manage ad campaigns, track impressions and clicks, configure ad zones and publishers'.
Add more natural trigger terms users might say, such as 'ad campaigns', 'ad network', 'impressions', 'publishers', 'ad zones', or 'blockchain advertising'.
Expand the 'Use when' clause with specific scenarios, e.g., 'Use when the user mentions AdShares, decentralized advertising, ad campaign management, or blockchain-based ad networks'.
| 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 records? What workflows? | 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 'Use when...' clause. However, both parts are quite shallow. | 3 / 3 |
Trigger Term Quality | It includes 'AdShares' as a domain-specific keyword that users would naturally say, but lacks any other natural trigger terms like specific operations, API names, ad campaigns, or related terminology that would help distinguish user intent. | 2 / 3 |
Distinctiveness Conflict Risk | 'AdShares' is a specific enough domain name to reduce conflicts, but 'manage data, records, and automate workflows' is extremely generic and could overlap with many other integration or data management skills. | 2 / 3 |
Total | 8 / 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.
The skill provides solid, actionable CLI commands for integrating with AdShares via Membrane, covering the full lifecycle from installation to running actions. Its main weaknesses are unnecessary introductory context about what Adshares is, a shallow entity overview that adds no value, and missing explicit validation/error-recovery steps in the workflow. The content could be tightened by removing explanatory fluff and adding verification checkpoints.
Suggestions
Remove the opening paragraph explaining what Adshares is and the bare entity overview list — Claude doesn't need this context, and the overview provides no actionable information.
Add explicit validation checkpoints after key steps (e.g., verify connection was created successfully before proceeding to action discovery, verify action run output is valid).
Consider splitting advanced topics like action creation/polling and best practices into a separate reference file if the skill grows, and add clearer navigation signals.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Adshares is (decentralized advertising marketplace, blockchain, etc.) is unnecessary context Claude already knows. The overview section listing entities without detail adds little value. However, the CLI commands themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Each command includes concrete flags and placeholders. | 3 / 3 |
Workflow Clarity | The workflow follows a logical sequence (install → authenticate → connect → discover → create/run), and the action creation flow includes polling with state checking. However, there are no explicit validation checkpoints or error recovery feedback loops for the overall workflow, and the headless auth flow could be more clearly sequenced. | 2 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — all content is inline in a single file. The overview section listing entities (Campaign, Targeting, Wallet, etc.) promises structure but delivers nothing actionable. No references to separate files for advanced topics or detailed schemas. | 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 | |
- Repository
- membranedev/application-skills
- Commit
56d7336
- 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.