EE-commerce Index
ECINDEX ACADEMY · INSTALLATION GUIDE

Bring the ECIndex
method into your AI.

One open instruction package, with different setup paths depending on the assistant you use. Review the files first, choose your platform, then begin with a bounded storefront review.

Choose your AI →Direct ZIP download ↓
“Install” does not mean the same thing everywhere.

Native skill hosts understand the package structure. Other assistants can still use its written method, but may not load files, triggers or metadata in exactly the same way.

01 · CHOOSE A SETUP

Use the path that
matches your workspace.

Interface labels and plan availability can change. Each route below links to the provider’s current official guidance.

NATIVE01

Codex

Place the skill folder in a recognized local or repository scope.

Setup steps ↓ NATIVE02

ChatGPT desktop

Use the standalone skill through the desktop Skills experience.

Setup steps ↓ ADAPTED03

Claude

Use project instructions and knowledge files to reproduce the method.

Setup steps ↓ ADAPTED04

Gemini

Create a Gem with the core instructions and supporting references.

Setup steps ↓
NATIVE SKILL01

Codex

Download and extract the package. For a project-specific skill, copy the complete ecindex-store-improvement folder into .agents/skills/ at the repository root. For a personal skill available across projects, use ~/.agents/skills/.

  1. Keep SKILL.md, references/, assets/ and agents/ together.
  2. Open the repository in Codex. Changes are normally detected automatically; restart Codex if the skill does not appear.
  3. Open the skill selector or type $ecindex-store-improvement in your prompt.
Download package ↓Official OpenAI skill guide ↗
NATIVE SKILL02

ChatGPT desktop

Standalone skills are supported in the ChatGPT desktop app. Download and review the package, then open Skills in the desktop sidebar and use the available import or creation flow for your version of the app.

  1. Confirm that the imported skill is named ECIndex Store Improvement.
  2. Start a new chat and select it with @, or ask for an evidence-led storefront review that matches its purpose.
  3. If Skills is unavailable in your account, use the manual method below rather than assuming the package is active.
Download package ↓Official OpenAI skill guide ↗
ADAPTED METHOD03

Claude Projects

This route applies the ECIndex method through Claude’s project instructions and knowledge base. It is an adaptation, not a guarantee that Claude will interpret OpenAI-specific metadata or invocation rules.

  1. Create a project named ECIndex Store Improvement.
  2. Open SKILL.md, copy its instruction body into the project instructions, and keep the evidence boundaries intact.
  3. Upload both files from references/ to project knowledge.
  4. Begin with the ready-to-copy prompt below and verify every finding against public evidence.
Official Claude Projects guide ↗
ADAPTED METHOD04

Gemini Gems

This route uses a custom Gem’s instructions and knowledge files. It carries the workflow into Gemini, but does not install the package as a native ECIndex integration.

  1. In the Gemini web app, create a new Gem named ECIndex Store Improvement.
  2. Copy the instruction body from SKILL.md into the Gem’s instructions.
  3. Under Knowledge, add the two files in references/.
  4. Preview the Gem with the starting prompt, check the output structure, then save.
Official Gemini Gems guide ↗
02 · MANUAL METHOD

For any other
AI assistant.

If an assistant accepts persistent instructions and files, copy the instruction body from SKILL.md into its workspace instructions and attach the two reference documents. If it accepts neither, attach the files to each relevant conversation.

REQUIREDSKILL.md

Purpose, workflow, boundaries and activation guidance.

REFERENCEevidence-and-integrity.md

Rules for separating observation, merchant claims, inference and recommendations.

REFERENCEoutput-template.md

A consistent structure for findings, priorities and validation steps.

OPTIONALopenai.yaml + icon

Display metadata for compatible OpenAI interfaces; other assistants may ignore it.

03 · FIRST RUN

Start with a bounded review.

Share only public storefront evidence and approved merchant facts. Ask the assistant to identify uncertainty before recommending changes.

Use the ECIndex Store Improvement method to review:

Store URL: [PUBLIC URL]
Country and market: [COUNTRY]
Business goal: [GOAL]
Approved merchant facts: [FACTS OR NONE]

Separate observed evidence, merchant-supplied facts,
inferences and recommendations. Prioritize actions by
impact, effort and confidence. Do not invent missing facts.
End with human review and post-publish validation checks.
04 · TRUST BOUNDARIES

Review before
you rely on it.

Inspect the package

Read every instruction and reference before adding it to an AI workspace. Download only from the official ecindex.org page.

Protect private data

Do not upload customer records, orders, payment data, credentials, unpublished commercial information or regulated personal data.

No automatic authority

The skill does not authorize publishing, purchasing, contacting third parties or changing a live store. A responsible person approves every material action.

Verify current guidance

Provider interfaces, availability and policies can change. Use the linked official documentation when a setup step differs from this guide.

UPDATES

Download the newest package and replace the existing skill folder or uploaded reference files after reviewing the changes.

REMOVE

Delete the ECIndex skill folder from its local skills location, or remove its instructions and files from the relevant Project or Gem.