agent-app-store

Agent skill for app-store - invoke with $agent-app-store

2.85x

Quality

11%

Does it follow best practices?

Impact

97%

2.85x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-app-store/SKILL.md

Quality

Content

22%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is heavily weighted toward persona definition and abstract guidance rather than actionable instructions. While the MCP tool call examples provide some concrete value, the majority of the content consists of verbose category lists, quality standards, and philosophical guidance that Claude already understands or doesn't need spelled out. The skill lacks clear workflows, validation steps, and practical decision-making guidance for common marketplace operations.

Suggestions

Remove the generic category lists, quality standards, and marketplace features sections — replace with concise decision trees for common operations (e.g., 'When user wants to publish: 1. validate source → 2. publish → 3. verify listing').

Add explicit multi-step workflows with validation checkpoints for key operations like publishing an app (including error handling and retry logic).

Cut the persona description and abstract responsibilities to 2-3 lines maximum, focusing only on information Claude wouldn't already know.

Add concrete examples showing expected outputs from the MCP tool calls and how to handle common error cases.

Dimension	Reasoning	Score
Conciseness	Extremely verbose with extensive explanations of concepts Claude already knows (what app categories are, what quality standards mean, what marketplace features do). The lists of categories, quality standards, and marketplace features are largely generic knowledge that doesn't add actionable value. The persona description and philosophical guidance ('foster a vibrant ecosystem') waste tokens.	1 / 3
Actionability	The JavaScript code examples showing MCP tool calls are concrete and provide specific function signatures with parameters, which is useful. However, much of the content is abstract guidance ('Curate and manage the marketplace', 'Ensure quality standards') rather than executable instructions. The code examples are helpful but incomplete — no error handling, no workflow showing how to chain operations.	2 / 3
Workflow Clarity	There are no clear multi-step workflows with sequencing or validation checkpoints. The numbered 'marketplace management approach' list describes abstract responsibilities, not actionable steps. Publishing an app, deploying a template, and handling errors are all operations that would benefit from explicit step-by-step workflows with validation, but none are provided.	1 / 3
Progressive Disclosure	The content is a monolithic document with no references to external files, but it does have some structural organization with headers and bold labels. However, the lengthy inline lists of categories, quality standards, and marketplace features could be split into separate reference files. No bundle files exist to support progressive disclosure.	2 / 3
	Total	6 / 12 Passed

Description

0%Scale 1-3

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 triggers should activate it. It reads more like an invocation instruction than a functional description.

Suggestions

Add concrete actions describing what the skill does (e.g., 'Searches app store listings, publishes apps, manages app metadata and reviews').

Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks about publishing to the App Store, managing app listings, or searching for apps').

Replace the invocation instruction ('invoke with $agent-app-store') with functional capability descriptions — invocation syntax belongs elsewhere, not in the description field.

Dimension	Reasoning	Score
Specificity	The description provides 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's an 'agent skill' and how to invoke it, providing no functional or trigger information.	1 / 3
Trigger Term Quality	The only keyword is 'app-store', which is somewhat relevant but lacks any natural language terms a user would say. No variations or contextual terms are provided.	1 / 3
Distinctiveness Conflict Risk	The description is so vague that it's impossible to distinguish it from other skills. 'App-store' could mean many things — publishing apps, searching app stores, managing listings — creating high conflict risk.	1 / 3
	Total	4 / 12 Passed

Validation

100%

Warnings & errors only

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
Path: .agents/skills/agent-app-store/SKILL.md
Commit: 913f9ea

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.