CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

product-feed-optimizer

Use when the user asks to "optimize my Shopping feed", "fix product disapprovals", "improve product titles/attributes", or "build feed-driven PMax asset groups"; audits and rewrites the Shopping/Performance Max product feed — title/description patterns, required and recommended attributes, GTIN/availability/price hygiene, disapproval triage, and feed-driven asset-group / listing-group structure — informing the ROAS O (Offer) dimension. Not for text ad copy — use ad-creative-builder; not for scoring the account or the RQS — use ad-account-auditor. 商品Feed优化/购物广告Feed/商品标题优化/商品禁投修复

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 delivers a well-sequenced, validated workflow with concrete attribute-level guidance and a properly disclosed reference pack. Its main weakness is token efficiency: boundary statements and cross-skill routing are repeated across multiple sections, and navigation depends on many files outside this bundle.

Suggestions

State the not-for boundaries once (either the intro or the Scope guard) and have Next Best Skill reference that statement instead of restating it, saving repeated tokens in conciseness.

Consolidate the multiple ad-account-auditor citations (Skill Contract, Instructions step 6/7, Scope guard, Reference Materials, Next Best Skill) into one routing pointer plus the Next Best Skill entry.

Inline a compact example of the disapproval triage table (item → cause → fix) in the Skill Contract, since the output shape is central to the deliverable and currently has no concrete example in the bundle.

DimensionReasoningScore

Conciseness

The body avoids explaining known concepts and stays information-dense, but systematically repeats itself: the not-for boundaries are stated three times (intro paragraph, Scope guard, and Next Best Skill) and ad-account-auditor is cited roughly six times. This fits the level-3 anchor (mostly efficient but could be tightened); it is not level 2 because the padding is repetition of genuinely useful routing rather than padded explanation, and not level 4 because the repetition is more than minor.

3 / 5

Actionability

The instructions are concrete and executable for an instruction-only skill: named attributes to check ("id, title, description, link, image_link, availability, price, brand, gtin/mpn, condition, google_product_category"), a front-loading rule tied to platform character limits, per-item '[needs source]' flagging, and verified reference patterns in references/feed-title-patterns.md. Minor gaps keep it at level 4: the triage-table output shape and handoff-summary format are deferred to files outside the bundle.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit priority ordering ("Triage disapprovals first... a rewritten title on a disapproved item still does not serve"), explicit validation (feed price/availability reconciled against the landing page), feedback loops (NEEDS_INPUT path; "If any item fails, fix it or report it in the handoff — do not ship silently"), and both a 'Done when' contract and a 5-item quality-bar checklist. This matches the level-5 anchor with validation steps, error recovery, and checklists.

5 / 5

Progressive Disclosure

The single bundle reference is well handled: it is signaled inline ("Use the patterns in references/feed-title-patterns.md"), listed with descriptions in Reference Materials, one level deep, and points back to SKILL.md; the split (templates/limits in the reference, overview in SKILL.md) is appropriate. Level 4 rather than 5 because the body leans heavily on cross-links to files outside the bundle (../../../references/skill-contract.md, ../../../CONNECTORS.md, ../../../SECURITY.md, sibling SKILL.md paths) that cannot be verified from this bundle.

4 / 5

Total

16

/

20

Passed

Description

92%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.

A strong description: it states concrete capabilities comprehensively, gives explicit 'Use when' trigger phrases (in both English and Chinese), and draws sharp boundaries against sibling skills. The only gap is a few natural trigger synonyms such as "Merchant Center".

DimensionReasoningScore

Specificity

The description names multiple concrete actions — 'audits and rewrites the Shopping/Performance Max product feed — title/description patterns, required and recommended attributes, GTIN/availability/price hygiene, disapproval triage, and feed-driven asset-group / listing-group structure' — with comprehensive coverage of the skill's capability surface. This matches the level-5 anchor (multiple specific concrete actions, comprehensive coverage); it goes beyond level 4 because no meaningful capability is left out.

5 / 5

Completeness

Explicitly answers both questions: "Use when the user asks to 'optimize my Shopping feed', 'fix product disapprovals'..." (when, with concrete trigger phrases) and "audits and rewrites the Shopping/Performance Max product feed..." (what), plus explicit exclusions. This matches the level-5 anchor exactly; level 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say — "optimize my Shopping feed", "fix product disapprovals", "improve product titles/attributes", "build feed-driven PMax asset groups" — plus Chinese synonyms. However "Merchant Center" (the most common user phrasing for disapproval work) and other common synonyms are absent, fitting the level-4 anchor (good coverage, a few natural terms missing) rather than level 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (Shopping/PMax product feed data) and actively de-conflicts with named siblings: "Not for text ad copy — use ad-creative-builder; not for scoring the account or the RQS — use ad-account-auditor." Minimal conflict risk, matching the level-5 anchor.

5 / 5

Total

19

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 20 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/research/product-feed-optimizer/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.