CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coupang-product-search

Operator-only local Coupang MCP tool layer. Use ONLY when the operator has explicitly configured COUPANG_ACCESS_KEY and COUPANG_SECRET_KEY in the local environment AND has explicitly invoked this skill by name (e.g. "coupang-product-search로 검색해줘"). Do NOT use for general user shopping requests — those must always go to the shopping-copilot skill which uses the hosted backend at a.retn.kr without requiring local credentials.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./coupang_product_search_skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a strong example of an executable skill: concrete commands for every capability, a sensible decision workflow, and accurate pre-flight failure documentation. The main flaw is redundancy — the operator-only routing warning is repeated four times and padded onto every purpose bullet, which wastes tokens without adding information.

Suggestions

State the operator-only/shopping-copilot routing rule once (in Hard rules) and delete the duplicate bold warning and second paragraph at the top.

Drop the "(operator use)" suffix from all six purpose bullets since the section title and skill title already establish operator-only scope.

Fold the credential pre-flight check into the Suggested workflow as step 0 so the validation checkpoint sits inside the sequence rather than only in Hard rules.

DimensionReasoningScore

Conciseness

The operator-only routing rule is stated four separate times ("This skill requires local Coupang API credentials. It is not for end-user shopping requests.", "Use `shopping-copilot` for all user-facing shopping queries...", "NEVER invoke this skill for general user shopping requests", plus the frontmatter), and all six purpose bullets redundantly append "(operator use)" when the section heading and title already establish it. This is anchor 3 (mostly efficient but could be tightened) rather than 4, since the repetition is noticeable rather than minor.

3 / 5

Actionability

Six fully executable, copy-paste-ready commands with realistic arguments cover the common cases: search "생수", rocket "에어팟", budget "키보드" --max-price 100000, compare "아이패드 vs 갤럭시탭", goldbox, and a tools contract check. This matches anchor 5 exactly — specific examples covering the common cases with no gaps.

5 / 5

Workflow Clarity

The five-step suggested workflow maps query shapes to commands ("If the query is too broad, narrow by use case, budget, or rocket-delivery preference", "Use `budget` when the user gives a price ceiling"), and Hard rules document a pre-flight checkpoint ("will fail with `RuntimeError: Coupang credentials are required` ... check env before invoking"). Anchor 4 rather than 5 because the env validation and `tools` contract check live in Hard rules instead of being integrated as explicit checkpoints in the workflow sequence, and there is no error-recovery loop.

4 / 5

Progressive Disclosure

The body is short and cleanly sectioned (purpose, hard rules, commands, workflow) with nothing that belongs in a separate file, and every command references the single real bundle script (scripts/openclaw-coupang-mcp.py, verified to exist). Per the simple-skill note, a short skill with no need for external references and well-organized sections scores 5.

5 / 5

Total

17

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 outstanding on routing and conflict avoidance — the operator-only gating and explicit shopping-copilot disambiguation are models of clarity. Its weakness is that it says almost nothing about what the skill actually does, leaving concrete capabilities (search, rocket, budget, compare, goldbox) undocumented and narrowing natural trigger coverage to a single invocation phrase.

Suggestions

Add 1-2 concrete capabilities to the description, e.g. "Searches Coupang products with rocket-delivery filtering, budget constraints, and product comparison" so the 'what' matches the explicitness of the 'when'.

Include the natural trigger keywords operators would use (rocket delivery/로켓배송, budget/price ceiling, product comparison, goldbox deals) alongside the explicit-by-name invocation example.

Keep the excellent negative-scope guidance but trim it slightly to make room for the positive capability statement without growing the description.

DimensionReasoningScore

Specificity

The description names the domain ("Operator-only local Coupang MCP tool layer") and credential/invocation conditions ("explicitly configured COUPANG_ACCESS_KEY and COUPANG_SECRET_KEY"), but lists no concrete capabilities — search, rocket-delivery filtering, budget constraints, comparison, or goldbox deals are never mentioned. This matches anchor 2 (domain named, actions minimal/generic) rather than 3, since the conditions described are scope rules rather than actions the skill performs.

2 / 5

Completeness

The "when" is exceptionally explicit with concrete trigger conditions ("Use ONLY when the operator has explicitly configured ... AND has explicitly invoked this skill by name"), but the "what" is abstract — "Coupang MCP tool layer" never states what operations are performed. This sits between anchor 4 (both present, one could be more explicit) and anchor 5 (both clearly and concretely answered), so 4.

4 / 5

Trigger Term Quality

It includes one genuine natural trigger phrase ("coupang-product-search로 검색해줘") plus the domain term "Coupang", but misses the common natural variations an operator would say — rocket delivery (로켓배송), budget/price ceiling, compare, deals. Anchor 3 (some relevant keywords, missing common variations) fits better than 4 because synonym coverage is thin.

3 / 5

Distinctiveness Conflict Risk

It carves out a clear operator-only niche and explicitly disambiguates against the nearest competing skill ("Do NOT use for general user shopping requests — those must always go to the shopping-copilot skill"), which is exactly anchor 5's clear-niche-with-distinct-triggers pattern with minimal conflict risk.

5 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

retention-corp/coupang_partners

Path

coupang_product_search_skill/SKILL.md

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.