agentleFS
Sign inStart free
khadinakbarlabskhadinakbarlabs/shopify-app-builder/skills/app-listing-optimization/SKILL.md

app-listing-optimization

Skill2 starsChanged 38 days agoMITView on GitHub

Draft or audit Shopify App Store listing copy, screenshots, support, and policy links.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask only for missing information that changes this task.

    line 13
  2. Distinctive:

    Check current listing rules, naming and trademark constraints before writing claims.

    line 18
  3. Distinctive:

    Write benefit-led title/description, a clear setup promise, honest pricing and support/policy links.

    line 19
  4. Distinctive:

    Never invent testimonials, rankings, certifications or approval guarantees.

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Explain the app honestly in its listing

Start here

A listing should explain the merchant outcome and show the app actually doing it.

First useful outcome: Draft a listing from verified features and real screenshots. Ask only for missing information that changes this task. Inspect the existing project and use synthetic data before touching a merchant store. Explain the next action and its expected result in plain language; offer a recommended default with its tradeoff.

Guided workflow

  1. Collect the target merchant, verified benefits, limitations, supported integrations and pricing.
  2. Check current listing rules, naming and trademark constraints before writing claims.
  3. Write benefit-led title/description, a clear setup promise, honest pricing and support/policy links.
  4. Plan screenshots around first value, workflow and result; scrub secrets and customer records; review the draft before submission.

Check it worked

Trace every claim to product evidence and check all links and screenshot states; distinguish draft from accepted listing. Report what was changed, what was tested, and what still needs account access or live verification. Do not claim production readiness or approval from generated code alone.

If you get stuck

Never invent testimonials, rankings, certifications or approval guarantees. Give one safe next step and a redacted error example, not a list of speculative fixes.

Safety and optional depth

Use only the user's selected project/accounts. Never read credential caches or request secrets in chat; the operator configures the application's approved secret store. Ask before live deployment, store mutations, billing, publication or paid runs unless that exact action is already authorized. No MCP service is required by this plugin.

For concrete examples in an existing project, read only the relevant section of technical-guide.md. These retained v1.x examples are version-sensitive, not the default template. Verify SDKs, schema fields, CLI flags and platform rules with official documentation before using them.

Example request: "Use app-listing-optimization to help me with this task. Explain each change and verify it before moving on."

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.

Check your setup, free