CtrlK
BlogDocsLog inGet started
Tessl Logo

market-pulse

When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A well-structured, concise market-briefing skill with clear sequencing and a ready output template. Its main weakness is incomplete actionability — data tools are named without parameters or examples and tables are left as blank placeholders.

Suggestions

Add at least one example invocation (with key parameters) for the data-collection tools so Claude knows how to call get_market_movers, get_trending_keywords, etc.

Fill or exemplify the blank template tables (e.g., one sample row) so the expected output shape is unambiguous rather than left empty.

Add an explicit verification checkpoint, such as confirming data freshness/date range and cross-checking that user-category results were actually returned before composing the briefing.

DimensionReasoningScore

Conciseness

Lean sectioned layout using bullets and tables with no teaching of concepts Claude already knows; a few blank template tables and soft prompts add only minor token overhead, so it stays at the lean/efficient anchor.

3 / 3

Actionability

Names concrete data tools (get_market_movers, get_trending_keywords, etc.) and provides a structured output template, but gives no parameter signatures or example invocations and leaves tables as blank placeholders, so guidance is concrete but incomplete.

2 / 3

Workflow Clarity

A clear sequence exists (Initial Assessment -> Data Collection -> Briefing Framework -> Output) with parallel gathering noted, but there are no explicit validation/feedback checkpoints; this read-only analysis task avoids the destructive-operations cap yet still only meets the steps-present-but-checkpoints-implicit anchor.

2 / 3

Progressive Disclosure

A single self-contained, well-organized SKILL.md with no bundle files; per the simple-skills note, clean sectioning of a focused skill earns the top anchor without external references.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly defines a combined market-overview capability, supplies natural trigger phrases, and proactively disambiguates from sibling skills. It answers both what and when without padding.

DimensionReasoningScore

Specificity

Lists multiple concrete signals — "chart movements, trending keywords, featured apps, new releases" combined into a market overview — matching the anchor for naming multiple specific concrete actions.

3 / 3

Completeness

Explicitly states both what (comprehensive App Store market overview combining multiple signals) and when ("Use when the user mentions ..."), with additional disambiguation triggers, satisfying the what-AND-when anchor.

3 / 3

Trigger Term Quality

Includes natural phrasings a user would actually say ("market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", "state of the market"), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (combined market overview) and explicitly disambiguates against adjacent skills ("For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research."), making mis-triggering unlikely.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
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.