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.
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-delivery-auditorSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- lead-scorerSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- obsidian-daily-noteSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- release-announcement-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- skill-reviewerSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
- write-evidence-backed-profileSkill
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
- Very specific: line 10
Use this skill to improve marketplace listings through a review-first workflow: audit the current listing, choose keywords, rewrite …
- Very specific: line 15
Read references/listing-constraints.md before writing titles, tags, descriptions, image notes, or attributes.
- Very specific: line 16
Read references/keyword-workflow.md before choosing or rejecting keywords.
- Very specific: line 17
Read references/batch-and-monitoring.md before prioritizing many listings or recommending a refresh cadence.
- Distinctive: line 44
Do not publish or echo private shop exports, raw CSV rows, customer data, order data, revenue, ad data, credentials, API tokens, internal …
- Distinctive: line 45
Do not claim guaranteed ranking, sales, or platform outcomes.
- Distinctive: line 46
Do not recommend keyword stuffing, misleading tags, unrelated trends, trademark misuse, or competitor copying.
- Distinctive: line 47
Do not paste changes into a live marketplace.
- Distinctive: line 48
If using competitor or keyword-tool data, summarize patterns and rationale instead of exposing private exports.
- Distinctive: line 53
Prefer clear buyer language over awkward keyword piles.
- Distinctive: line 54
Keep descriptions natural and scannable.
- Distinctive: line 55
Use all allowed tags only when they are relevant.
≈ “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.
Files
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
- Clarify the product type, buyer intent, marketplace, and whether the user wants a single-listing rewrite, keyword review, shop audit, or batch plan.
- Read
references/listing-constraints.mdbefore writing titles, tags, descriptions, image notes, or attributes. - Read
references/keyword-workflow.mdbefore choosing or rejecting keywords. - Read
references/batch-and-monitoring.mdbefore prioritizing many listings or recommending a refresh cadence. - Produce a concise optimization result with before/after fields, rationale, rejected keywords, review notes, and next steps.
- 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:
- Listing audit summary.
- Buyer intent and positioning.
- Optimized title.
- Up to 13 tags.
- Description rewrite.
- Image, category, and attribute notes.
- Keywords used and keywords rejected.
- Human review checklist before publishing.
For a shop or batch, return:
- Priority logic.
- Batch list using fake or user-approved identifiers.
- Recommended workflow for each listing.
- Data freshness warnings.
- 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.
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
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.

