agent-app-store
Agent skill for app-store - invoke with $agent-app-store
42
11%
Does it follow best practices?
Impact
97%
2.85xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-app-store/SKILL.mdQuality
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 no information about what the skill does, when it should be used, or what domain it operates in. It reads as a placeholder rather than a functional description.
Suggestions
Add concrete actions describing what this skill does (e.g., 'Searches app store listings, retrieves app metadata, checks app availability and pricing').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about finding apps, checking app reviews, app pricing, or app store listings').
Specify which app store(s) this skill targets (e.g., iOS App Store, Google Play, internal catalog) to reduce ambiguity and conflict risk.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Agent skill for app-store' is entirely vague and does not describe what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states it is an 'agent skill' and how to invoke it, providing no functional or contextual information. | 1 / 3 |
Trigger Term Quality | The only keyword is 'app-store', which is ambiguous and not a natural phrase users would say when requesting a specific task. No natural trigger terms are present. | 1 / 3 |
Distinctiveness Conflict Risk | 'App-store' is vague and could refer to many different things (iOS App Store, Google Play, internal app catalogs, etc.). There is no specificity to distinguish this from other potential skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is primarily a persona description and feature catalog rather than actionable operational guidance. While it provides useful MCP tool call examples, the majority of the content is verbose descriptions of responsibilities, categories, and aspirational quality standards that don't help Claude execute specific tasks. It lacks concrete workflows, validation steps, error handling, and expected outputs.
Suggestions
Replace the abstract responsibility lists and category catalogs with concrete workflows: e.g., step-by-step 'How to publish an app' and 'How to deploy a template' sequences with validation checkpoints.
Add expected output examples for each MCP tool call so Claude knows what success and failure look like.
Remove the lengthy app category list, quality standards enumeration, and marketplace features list — these describe the system rather than instruct Claude on how to operate it.
Add error handling guidance and feedback loops, especially for publishing (what if validation fails?) and deployment (what if variables are missing?).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Heavily padded with information Claude already knows or can infer. The lengthy lists of app categories, quality standards, marketplace features, and vague responsibility descriptions add little actionable value. Phrases like 'Foster a vibrant ecosystem of developers and users' and 'Revenue Optimization' are filler. | 1 / 3 |
Actionability | The JavaScript code examples showing MCP tool calls are concrete and provide specific function signatures with parameters, which is useful. However, there's no guidance on when to use which tool, no error handling, no expected outputs, and the surrounding content is descriptive rather than instructive. | 2 / 3 |
Workflow Clarity | There are no clear multi-step workflows with sequencing or validation checkpoints. The numbered list under 'marketplace management approach' describes abstract principles, not actionable steps. Publishing an app, deploying a template, and handling errors have no defined sequences or feedback loops. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers and bold labels, providing some structure. However, it's a monolithic file with no references to external documentation, and content like the full category list and quality standards could be split out. No bundle files exist to reference. | 2 / 3 |
Total | 6 / 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.
- Repository
- ruvnet/claude-flow
- Commit
9d4a9ea
- 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.