How do I install the Lean Core Usage skill?

Run npx skillmds@latest add leancodepl/lean-core-usage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Lean Core Usage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Lean Core Usage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Lean Core Usage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Lean Core Usage?

leancodepl (@leancodepl) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Lean Core Usage by leancodepl — Agent Skill

Name: Lean Core Usage
Author: leancodepl

Lean Core Usage

Explain what the LeanCode AI plugins marketplace covers, which plugins are available, and how to install them. Use when the user invokes `/lean-core-usage`, asks what this marketplace is, asks which plugins exist, or asks where to begin. Manual-only entry point — does not auto-fire.

leancodepl b29c327 2.8 KB Updated Sep 17, 2026

File contents

LeanCode Core Usage

How to respond

Read the sources of truth first — do not rely on memory or hardcoded lists:
- .claude-plugin/marketplace.json at the repo root for the canonical plugin list (name + description per plugin).
- The root README.md "Supported clients" section for the list of supported clients. Always read it — do not enumerate clients from memory, do not invent client names.
- If the working directory is not the repo, point the user at https://github.com/leancodepl/ai-plugins and read from the GitHub-hosted versions of those files.
Summarize what the marketplace covers in one paragraph, using the descriptions read from the JSON.
Print one bullet per plugin: name + the description from marketplace.json. Do not invent or restate descriptions.
List the supported clients from the root README, in the order they appear there.
Route domain questions to the matching /<plugin>-usage skill rather than answering them here.
When the user wants to contribute, point at /lean-contribute.
Do not reply with filler like "skill loaded" or "ready for the task" before explaining the marketplace.

What the marketplace is

leancodepl/ai-plugins is LeanCode's shared marketplace of AI plugins for Claude Code, focused on Flutter development. Each plugin is small, focused, and independently installable.

lean-core is the meta plugin: an entry point that explains the marketplace (/lean-core-usage) and a contribution helper (/lean-contribute). Nothing else lives in lean-core — every domain capability is its own plugin.

Picking plugins

Install only what the project actually uses. If unsure, install lean-core first, run /lean-core-usage, and pick from the read-from-JSON list.

Installing the marketplace

Each plugin has its own /<plugin>-usage skill (for example /flutter-bloc-usage). Reach for it once the plugin is installed.

Step-by-step install lives in the root README.md under "Install". Walk the user through it. The supported clients are listed in the root README's "Supported clients" section — read it; do not invent client names.

Contributing

When you want to propose a tweak or a new plugin, run /lean-contribute. It walks through the repo structure, the CI checks, and the PR steps.

What this plugin is NOT about

Any domain guidance. Route to the matching /<plugin>-usage.
Running commands or rewriting files for you. This skill only explains.
Restating the plugin or client list from memory. Always read the source of truth.

---name: lean-core-usagedescription: Explain what the LeanCode AI plugins marketplace covers, which plugins are available, and how to install them. Use when the user invokes `/lean-core-usage`, asks what this marketplace is, asks which plugins exist, or asks where to begin. Manual-only entry point — does not auto-fire.---# LeanCode Core Usage## How to respond1. **Read the sources of truth first** — do not rely on memory or hardcoded lists: - `.claude-plugin/marketplace.json` at the repo root for the canonical plugin list (`name` + `description` per plugin). - The root `README.md` "Supported clients" section for the list of supported clients. Always read it — do not enumerate clients from memory, do not invent client names. - If the working directory is not the repo, point the user at https://github.com/leancodepl/ai-plugins and read from the GitHub-hosted versions of those files.2. Summarize what the marketplace covers in one paragraph, using the descriptions read from the JSON.3. Print one bullet per plugin: name + the description from `marketplace.json`. Do not invent or restate descriptions.4. List the supported clients from the root README, in the order they appear there.5. Route domain questions to the matching `/<plugin>-usage` skill rather than answering them here.6. When the user wants to contribute, point at `/lean-contribute`.7. Do not reply with filler like "skill loaded" or "ready for the task" before explaining the marketplace.## What the marketplace is`leancodepl/ai-plugins` is LeanCode's shared marketplace of AI plugins for Claude Code, focused on Flutter development. Each plugin is small, focused, and independently installable.`lean-core` is the meta plugin: an entry point that explains the marketplace (`/lean-core-usage`) and a contribution helper (`/lean-contribute`). Nothing else lives in `lean-core` — every domain capability is its own plugin.## Picking pluginsInstall only what the project actually uses. If unsure, install `lean-core` first, run `/lean-core-usage`, and pick from the read-from-JSON list.## Installing the marketplaceEach plugin has its own `/<plugin>-usage` skill (for example `/flutter-bloc-usage`). Reach for it once the plugin is installed.Step-by-step install lives in the root `README.md` under "Install". Walk the user through it. The supported clients are listed in the root README's "Supported clients" section — read it; do not invent client names.## ContributingWhen you want to propose a tweak or a new plugin, run `/lean-contribute`. It walks through the repo structure, the CI checks, and the PR steps.## What this plugin is NOT about- Any domain guidance. Route to the matching `/<plugin>-usage`.- Running commands or rewriting files for you. This skill only explains.- Restating the plugin or client list from memory. Always read the source of truth.

Frequently asked questions