pricing-advisor

Describe your product and target customer, get a pricing strategy with three tiers and rationale.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/gemma/pricing-advisor/SKILL.md

Quality

Content

100%Weight 40%Scale 1-3

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

The content is a tightly written, single-purpose skill with concrete tool/parameter guidance and well-organized sections, appropriately self-contained for its scope.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line intro, five brief examples, and a precise field spec, with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	It mandates the exact tool ('You MUST use the run_js tool') with a complete parameter spec giving type and example for every field, providing concrete, copy-paste-ready guidance for an instruction-only skill.	3 / 3
Workflow Clarity	This is a simple single-action skill (fill the data fields and call run_js) with an unambiguous action, which the simple_skills note allows to score 3; no destructive/batch steps require validation checkpoints.	3 / 3
Progressive Disclosure	Under 50 lines with well-organized sections (## Examples, ## Instructions) and no doc references needed; the bundle files (scripts/index.html, assets/webview.html) are runtime webview assets consumed by run_js, not navigable docs, so the simple-skill note applies.	3 / 3
	Total	12 / 12 Passed

Description

57%Weight 40%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.

The description is concrete and distinctive about pricing strategy generation, but it uses second-person voice and omits an explicit 'Use when' trigger clause, capping completeness and reducing specificity.

Suggestions

Rewrite in third person (e.g., 'Generates a pricing strategy...') to avoid the second-person specificity penalty.

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when the user asks how to price a product, set subscription tiers, or build a pricing model').

Broaden trigger terms to include common phrasings users actually say, like 'how much should I charge' or 'set my price'.

Dimension	Reasoning	Score
Specificity	Names concrete inputs/outputs ('Describe your product and target customer, get a pricing strategy with three tiers and rationale'), which is base-3 specificity, but the second-person voice ('your product') triggers the rubric's -1 voice penalty.	2 / 3
Completeness	Clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines cap at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('pricing strategy', 'three tiers', 'rationale') but lacks common user variations like 'how much should I charge' or 'set my price', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche ('pricing strategy with three tiers and rationale') unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mergisi/awesome-openclaw-agents
Path: skills/gemma/pricing-advisor/SKILL.md
Commit: 05820c5

Reviewed: 8 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.