agent-app-store
Agent skill for app-store - invoke with $agent-app-store
47
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/skillEvaluation — 97%
↑ 2.85xAgent success when using this skill
Validation for skill structure
Discovery
0%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 is critically deficient across all dimensions. It provides only a name and invocation command without any explanation of capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Search app stores, check app availability, retrieve app metadata and reviews, compare pricing across platforms')
Include an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user asks about finding apps, checking app store listings, app reviews, or app availability on iOS/Android')
Specify which app stores are supported (Apple App Store, Google Play, etc.) to create clear distinctiveness and reduce conflict with other potential skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for app-store' is completely abstract and does not describe what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides an invocation command ($agent-app-store) with no functional description or usage guidance. | 1 / 3 |
Trigger Term Quality | The only potential trigger term is 'app-store' which is vague and doesn't reflect natural user language. No keywords like 'download apps', 'publish app', 'iOS', 'Android', or specific app store actions are included. | 1 / 3 |
Distinctiveness Conflict Risk | 'App-store' is extremely generic and could conflict with any skill related to mobile apps, app publishing, app reviews, or marketplace functionality. There are no distinguishing characteristics. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable overview of app store functionality with useful MCP tool examples, but lacks concrete workflows and validation steps for critical operations like publishing and deployment. The content is padded with descriptive lists of categories and features that don't add actionable value, while missing the step-by-step guidance needed for complex marketplace operations.
Suggestions
Add explicit step-by-step workflows for common operations (e.g., 'Publishing an App' with validation checkpoints before final submission)
Complete the code examples with realistic values and show expected outputs/responses
Remove or condense the verbose category and feature lists - Claude understands these concepts
Add validation/verification steps for deployment operations (e.g., 'Verify deployment status before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Contains some unnecessary padding like the extensive category lists and quality standards that Claude already understands. The marketplace features section is verbose and describes concepts rather than providing actionable guidance. | 2 / 3 |
Actionability | Provides concrete JavaScript code examples for the MCP tools which is good, but the examples are incomplete (sourceCode variable undefined) and the rest of the content is descriptive rather than instructive. Missing specific workflows for common tasks. | 2 / 3 |
Workflow Clarity | No clear multi-step workflows are defined. The 'marketplace management approach' lists abstract concepts (Content Curation, Quality Assurance) without concrete steps. No validation checkpoints for publishing or deployment operations which are potentially destructive. | 1 / 3 |
Progressive Disclosure | Content is reasonably organized with sections, but everything is inline in one file. No references to external documentation for detailed API specs, examples, or advanced features. The extensive category and feature lists could be moved to reference files. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.