agentleFS
jqaisystemsjqaisystems/jqai-ai-skills/skills/etsy-listing-optimizer/SKILL.md

etsy-listing-optimizer

Skill3 starsChanged 6 months agoMITView on GitHub

Audit, rewrite, prioritize, and monitor Etsy or marketplace listings using public-safe product data. Use when the user asks to optimize an Etsy listing, improve product titles, tags, descriptions, keyword fit, marketplace SEO, listing batches, shop audits, eRank-style keyword review, competitor notes, or listing refresh workflows without exposing shop exports, private metrics, customer data, credentials, raw CSVs, or live shop configuration.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to improve marketplace listings through a review-first workflow: audit the current listing, choose keywords, rewrite …

    line 10
  2. Very specific:

    Read references/listing-constraints.md before writing titles, tags, descriptions, image notes, or attributes.

    line 15
  3. Very specific:

    Read references/keyword-workflow.md before choosing or rejecting keywords.

    line 16
  4. Very specific:

    Read references/batch-and-monitoring.md before prioritizing many listings or recommending a refresh cadence.

    line 17
  5. Distinctive:

    Do not publish or echo private shop exports, raw CSV rows, customer data, order data, revenue, ad data, credentials, API tokens, internal …

    line 44
  6. Distinctive:

    Do not claim guaranteed ranking, sales, or platform outcomes.

    line 45
  7. Distinctive:

    Do not recommend keyword stuffing, misleading tags, unrelated trends, trademark misuse, or competitor copying.

    line 46
  8. Distinctive:

    Do not paste changes into a live marketplace.

    line 47
  9. Distinctive:

    If using competitor or keyword-tool data, summarize patterns and rationale instead of exposing private exports.

    line 48
  10. Distinctive:

    Prefer clear buyer language over awkward keyword piles.

    line 53
  11. Distinctive:

    Keep descriptions natural and scannable.

    line 54
  12. Distinctive:

    Use all allowed tags only when they are relevant.

    line 55

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Etsy Listing Optimizer

Overview

Use this skill to improve marketplace listings through a review-first workflow: audit the current listing, choose keywords, rewrite title/tags/description, prioritize batches, and define a monitoring cadence. Use fake sample data in public examples and keep private shop data out of shared outputs.

Workflow

  1. Clarify the product type, buyer intent, marketplace, and whether the user wants a single-listing rewrite, keyword review, shop audit, or batch plan.
  2. Read references/listing-constraints.md before writing titles, tags, descriptions, image notes, or attributes.
  3. Read references/keyword-workflow.md before choosing or rejecting keywords.
  4. Read references/batch-and-monitoring.md before prioritizing many listings or recommending a refresh cadence.
  5. Produce a concise optimization result with before/after fields, rationale, rejected keywords, review notes, and next steps.
  6. Require human review before anything is pasted into a live listing, shop dashboard, ad system, or scheduling tool.

Default Output

For a single listing, return:

  1. Listing audit summary.
  2. Buyer intent and positioning.
  3. Optimized title.
  4. Up to 13 tags.
  5. Description rewrite.
  6. Image, category, and attribute notes.
  7. Keywords used and keywords rejected.
  8. Human review checklist before publishing.

For a shop or batch, return:

  1. Priority logic.
  2. Batch list using fake or user-approved identifiers.
  3. Recommended workflow for each listing.
  4. Data freshness warnings.
  5. Monitoring cadence.

Safety Rules

  • Do not publish or echo private shop exports, raw CSV rows, customer data, order data, revenue, ad data, credentials, API tokens, internal paths, or live shop configuration.
  • Do not claim guaranteed ranking, sales, or platform outcomes.
  • Do not recommend keyword stuffing, misleading tags, unrelated trends, trademark misuse, or competitor copying.
  • Do not paste changes into a live marketplace. The user must review and apply.
  • If using competitor or keyword-tool data, summarize patterns and rationale instead of exposing private exports.

Style Rules

  • Match the actual product, material, format, and use case.
  • Prefer clear buyer language over awkward keyword piles.
  • Keep descriptions natural and scannable.
  • Use all allowed tags only when they are relevant.
  • Explain tradeoffs when a strong keyword is rejected for mismatch, trademark risk, weak intent, or poor fit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.