---
title: "Éclair skills"
description: "The library of 57 Éclair CMS 2.0 skills: shop, online learning, forum, bookings, SEO, WordPress migration. Installation, real status and FAQ."
url: "https://eclaircms.org/en/skills"
lang: "en"
author: "Thierry Gustin"
published: "2026-11-07"
updated: "2026-11-10"
---

# Éclair skills

> **Key takeaways** — Éclair skills are 57 working guides for Claude, Codex or ChatGPT, in eight families. Installed in your project, they tell the AI where to put the code, how to store data, which security rules to follow and which tests to pass before proposing a new feature. Nineteen can be used right now with Éclair 2.0; the others guide the design of shops, online schools or forums for which some core building blocks are not open yet.

## 57 skills that make your AI an expert

Éclair skills turn Claude, Codex or ChatGPT into a developer who knows Éclair 2.0 inside out. You describe what your site needs, a shop, an online school, a directory or a WordPress migration, and the AI follows precise rules: where to put the code, how to protect data, which tests to pass. **Nothing is activated without you.**

[See the library on GitHub](https://github.com/Jacckisback/eclair-skills)

> **Note** — **A skill is not a ready-made extension.** It is a working guide for the agent: it produces a design, permitted code and tests, which a person approves before anything is activated. Commerce, learning and forum skills describe features that rely on core building blocks not yet open: they are for design, not for production deployment.

## The library in numbers

### 57

skills, each in its own folder with its references

### 8

families, from foundations to business apps

### 19

skills usable right now with Éclair 2.0

### AGPL

free software license, like Éclair CMS

## What is an Éclair skill?

A skill is a folder containing a `SKILL.md` file and its references. Coding assistants such as Claude Code or Codex read it when your request matches its description. The skill gives them the context they lack: Éclair 2.0’s architecture, the `eclair-extension/1` extension contract, the permitted locations, the security invariants and the acceptance criteria.

### 📋 A manual for the AI

Diagnosis, procedure, deliverables and acceptance criteria, written for an agent.

### 🛡️ Non-negotiable rules

Never touch the core, rights checked on every object, no private data in a shared cache.

### 🧪 Proof before going live

Package validation, full test suite, performance measurement and human review.

## How it works, in 4 steps

1. **You install the skills** your project needs, by family or one by one.
2. **You describe your need** to your assistant: “a directory of craftspeople with filters by city”.
3. **The AI picks the relevant skills**, reads your site’s real capabilities and prepares a design, the code in `site/extensions/` or `site/themes/`, and its tests.
4. **You approve**: the package passes the official validator, the tests and the performance check, then a person activates it from the admin.

## The 57 skills, family by family

Each skill carries an honest status. ✅ means it relies on capabilities already in Éclair 2.0. 🧭 means it guides the design, but part of the journey (customer accounts, payment, public writing) depends on core building blocks not yet open.

### Foundations (8)

The native v2 contract, tests and security: the base for every other skill.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-architecture` | Decide where a feature belongs: setting, theme, extension or core RFC | ✅ Usable with Éclair 2.0 |
| `eclair-extension-builder` | Build a native `eclair-extension/1` extension that survives updates | ✅ Usable with Éclair 2.0 |
| `eclair-storage` | Choose storage, migrations and backups for data | ✅ Usable with Éclair 2.0 |
| `eclair-auth-roles` | Design accounts, roles and rights: members, students, customers, moderators | ✅ Usable with Éclair 2.0 |
| `eclair-routing` | Create public and admin routes, keep exact URLs | ✅ Usable with Éclair 2.0 |
| `eclair-cache-contract` | Decide what is cached, invalidated or kept dynamic | ✅ Usable with Éclair 2.0 |
| `eclair-security-audit` | Audit each feature before it goes live | ✅ Usable with Éclair 2.0 |
| `eclair-test-suite` | Write regression, security and performance tests | ✅ Usable with Éclair 2.0 |

### Commerce Pro (10)

Transactional shop and payment: design before deployment.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-commerce-pro` | Design a full shop, from catalogue to delivered order | 🧭 Design: core capabilities to check |
| `eclair-product-catalog` | Build a fast, indexable public catalogue | 🟡 Public read-only prototype |
| `eclair-product-variants` | Model sizes, colours and options without price errors | 🧭 Design: core capabilities to check |
| `eclair-cart-checkout` | Design a multi-line cart with consistent prices and stock | 🧭 Design: core capabilities to check |
| `eclair-orders-payments` | Handle order states and payment providers | 🧭 Design: core capabilities to check |
| `eclair-tax-invoicing` | Prepare VAT and invoicing for each jurisdiction | 🧭 Design: core capabilities to check |
| `eclair-inventory` | Keep real stock in sync across products, variants and orders | 🧭 Design: core capabilities to check |
| `eclair-shipping` | Handle shipping zones, rates, tracking and status | 🧭 Design: core capabilities to check |
| `eclair-discounts` | Create discounts and coupons that don’t stack by mistake | 🧭 Design: core capabilities to check |
| `eclair-commerce-analytics` | Track sales and conversions without exposing customers | 🧭 Design: core capabilities to check |

### Online learning (LMS) (7)

Courses, enrolments, progress and certificates.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-lms` | Structure a modular online school | 🧭 Design: core capabilities to check |
| `eclair-course-builder` | Compose versioned courses, sections and lessons | 🧭 Design: core capabilities to check |
| `eclair-lessons-media` | Serve protected course videos and documents | 🧭 Design: core capabilities to check |
| `eclair-enrollment-access` | Link a purchase or approval to an enrolment | 🧭 Design: core capabilities to check |
| `eclair-progress` | Track progress with no loss or inconsistency | 🧭 Design: core capabilities to check |
| `eclair-quizzes-certificates` | Create quizzes, pass marks and verifiable certificates | 🧭 Design: core capabilities to check |
| `eclair-lms-analytics` | Analyse completion and engagement without intrusive tracking | 🧭 Design: core capabilities to check |

### Forum and community (6)

Discussions, moderation, profiles and notifications.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-forum` | Design moderated public and private discussions | 🧭 Design: core capabilities to check |
| `eclair-discussions-topics` | Handle topic creation, editing and status | 🧭 Design: core capabilities to check |
| `eclair-community-profiles` | Offer public profiles kept apart from private data | 🧭 Design: core capabilities to check |
| `eclair-moderation` | Build reporting, removal and appeals | 🧭 Design: core capabilities to check |
| `eclair-notifications` | Notify members without spam or data leaks | 🧭 Design: core capabilities to check |
| `eclair-community-search` | Search topics and posts according to permissions | 🧭 Design: core capabilities to check |

### Business apps (8)

Bookings, memberships, directories, events and business tools.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-bookings` | Manage a bookable resource without double bookings | 🧭 Design: core capabilities to check |
| `eclair-appointments-calendar` | Take appointments and connect external calendars | 🧭 Design: core capabilities to check |
| `eclair-memberships` | Manage membership levels, renewals and access rights | 🧭 Design: core capabilities to check |
| `eclair-directory` | Create a directory with indexable listings and filters | 🟡 Public read-only prototype |
| `eclair-events-ticketing` | Sell seats, tickets and admissions | 🧭 Design: core capabilities to check |
| `eclair-job-board` | Publish job offers and receive applications | 🧭 Design: core capabilities to check |
| `eclair-real-estate` | Build a property catalogue with search and contact | 🧭 Design: core capabilities to check |
| `eclair-forms-crm` | Collect requests and track how they are handled | 🧭 Design: core capabilities to check |

### Design and UX (7)

Themes, blocks, accessibility and speed.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-design` | Create an art direction consistent with the native theme | ✅ Usable with Éclair 2.0 |
| `eclair-theme-builder` | Produce an Éclair 2 theme that survives updates | ✅ Usable with Éclair 2.0 |
| `eclair-blocks-library` | Compose editable content blocks | ✅ Usable with Éclair 2.0 |
| `eclair-accessibility` | Audit and fix accessibility (WCAG) | ✅ Usable with Éclair 2.0 |
| `eclair-design-system` | Build a consistent, maintainable visual language | ✅ Usable with Éclair 2.0 |
| `eclair-responsive-ux` | Optimise mobile navigation, forms and layouts | ✅ Usable with Éclair 2.0 |
| `eclair-performance-ux` | Measure and reduce page weight and layout shift | ✅ Usable with Éclair 2.0 |

### SEO, GEO and migration (5)

Indexability, structured data, multilingual and WordPress.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-seo-audit` | Check indexability, canonicals, robots, links and speed | ✅ Usable with Éclair 2.0 |
| `eclair-geo-optimization` | Make pages readable for search engines and AI assistants | ✅ Usable with Éclair 2.0 |
| `eclair-wordpress-migration` | Migrate from WordPress while keeping URLs, content and traffic | ✅ Usable with Éclair 2.0 |
| `eclair-structured-data` | Add or check Schema.org data that matches the content | 🟠 Partly blocked by the core |
| `eclair-multilingual-seo` | Handle several languages without duplicates or wrong canonicals | ✅ Usable with Éclair 2.0 |

### Integrations and automation (6)

APIs, webhooks, e-mails, AI and monitoring.

| Skill | What it does | Status |
| --- | --- | --- |
| `eclair-webhooks` | Connect external apps through secure events | 🧭 Design: core capabilities to check |
| `eclair-email-automation` | Send reliable confirmations and reminders | 🧭 Design: core capabilities to check |
| `eclair-api-integration` | Build robust, rate-limited API connectors | 🧭 Design: core capabilities to check |
| `eclair-crm-integration` | Sync leads and customers with a CRM without duplicates | 🧭 Design: core capabilities to check |
| `eclair-ai-workflows` | Automate editorial help without unwanted publishing | 🧭 Design: core capabilities to check |
| `eclair-observability` | Monitor module health, costs and incidents | 🧭 Design: core capabilities to check |

## What can you build with Éclair 2.0 today?

The table below follows the capability matrix published with the library. It avoids bad surprises: a feature can only ship to production if the core provides its contract.

| Feature | Éclair 2.0 contract | What the skills let you do |
| --- | --- | --- |
| Public pages, SEO and GEO | Yes | Build and audit fast, well-ranked pages |
| Custom themes and blocks | Yes | Create a theme or blocks that survive updates |
| Admin screens | Yes | Build protected admin modules |
| Scheduled tasks | Yes | Automate imports, reports or syncs |
| WordPress import and old URLs | Yes, native feature | Prepare and check a migration without losing URLs |
| Public sign-up and login | Not yet | Design, test, prepare the RFC |
| Cart, payment, orders | Not yet | Specifications and design tests, no production shop |
| Forum or LMS with writing | Not yet | Journeys, data and tests ready for when the core opens them |

## How do you install the skills?

You need Python 3 and a copy of the library. Download it from [GitHub](https://github.com/Jacckisback/eclair-skills), then, in its folder:

```bash
python3 scripts/validate_skills.py
python3 scripts/install_skills.py --list
python3 scripts/install_skills.py --project /path/to/my-site --category foundation
python3 scripts/install_skills.py --project /path/to/my-site --skill eclair-wordpress-migration
python3 scripts/install_skills.py --project /path/to/my-site --all
```

Skills are copied into your project’s `.agents/skills/` folder, the one Codex reads. For Claude Code, copy the folders you want into `.claude/skills/`. The installer never replaces an existing skill unless you add `--force` after review. The families are called `foundation`, `commerce`, `lms`, `community`, `business`, `design`, `seo` and `integrations`.

[Follow the step-by-step guide](https://eclaircms.org/en/documentation/skills)

## Create your own skills

The foundations family also serves as a model: a skill is a `skills/eclair-<name>/` folder with a `SKILL.md` (name, description, procedure, acceptance criteria) and its `references/`. You can write your own for your trade, validate it with `python3 scripts/validate_skills.py` and propose it to the library. The whole method is in [the article on the core and the skills](https://eclaircms.org/blog/eclair-2-core-skills-features-on-demand).

## Frequently asked questions about Éclair skills

### Are the skills free?

Yes. The library is published under the AGPL-3.0 free software license, like Éclair CMS. Only your AI assistant may cost something, depending on your subscription.

### Does a skill install a shop or a forum on its own?

No. A skill guides the agent: it produces a design, code and tests, which a person approves and activates. Commerce, learning and forum journeys still depend on core building blocks (public accounts, payment): they are not ready for production.

### Which AI assistants can use the skills?

Those that read `SKILL.md` folders: Claude Code, Codex and other compatible agents. With a chat assistant such as ChatGPT, you can also give it the content of the relevant `SKILL.md`.

### Do I need to know how to code?

Not to describe your need. You do need someone able to review what the agent proposes, run the tests and activate the feature knowingly.

### Do the skills modify Éclair’s core?

Never. Everything they produce lives in `site/extensions/` or `site/themes/`, which updates never touch. A missing core capability leads to an RFC, not a workaround.

### Can I create my own skills?

Yes: a folder, a `SKILL.md`, references and the library’s check scripts. The guide and the article explain the method.

## Give your AI the Éclair manual

Download Éclair 2.0, install the skills your project needs and describe what you want to build.

[Download Éclair 2.3.0](https://eclaircms.org/en/download)