by ReflexioAI
Turns corrections into Preferences, Project-specific skills, and Shared skills for Claude Code, Codex, and OpenCode.
# Add to your Claude Code skills
git clone https://github.com/ReflexioAI/claude-smartGuides for using ai agents skills like claude-smart.
Last scanned: 5/22/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-22T07:44:33.995Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": true
}See how claude-smart compares with popular alternatives.
claude-smart is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by ReflexioAI. Turns corrections into Preferences, Project-specific skills, and Shared skills for Claude Code, Codex, and OpenCode. It has 795 GitHub stars.
Yes. claude-smart passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/ReflexioAI/claude-smart" and add it to your Claude Code skills directory (see the Installation section above).
claude-smart is primarily written in Python. It is open-source under ReflexioAI on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh claude-smart against similar tools.
No comments yet. Be the first to share your thoughts!
From $49 · 30 days · terms & refunds
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
Automated security scan — not a certification.
Requires Node.js 20+ (for npx) and the host CLI you're installing into (claude, codex, or opencode) on PATH.
npx claude-smart install
Choose one or more detected coding agents with the arrow keys and Space, then press Enter. Single-choice settings use the arrow keys and Enter. Esc or Ctrl+C cancels before configuration is saved.
The guide asks where to store and process your data:
In local mode, Claude Code learning defaults to the sonnet alias, which Claude
Code resolves independently of the coding model. Codex and OpenCode keep their
provider-configured defaults. An explicit supported model ID overrides these
choices. For unattended installs, use
--model <model-id> with --provider. The chosen model is applied to extraction
and optimizer calls. Managed mode reports the server-configured model when
available, otherwise explicitly reports that its default model is not exposed.
After install, update, or setup, the summary includes the Claude-smart version,
learning provider, provider CLI version when available, and model selection.
Configured aliases/defaults are distinguished from a reported model version;
unknown versions are shown as “not reported.” Run npx claude-smart setup to
change the learning settings.
When local learning is already configured, Keep current learning configuration
is selected by default. It preserves cloud generation, custom executables and the
current native model; selecting a native provider entry explicitly changes that
setup and opens its model choices. Supported caller overrides still apply, and
--provider explicitly replaces a cloud/custom configuration with that native
provider. Installing a different coding integration does not select its model.
The dashboard's Data source dropdown selects Local or Managed Reflexio. It defaults to the saved runtime mode. Its endpoint, overview totals, preferences, skills, and backend sessions follow the selected source; viewing another source does not change learning/storage settings. The header shows the selected endpoint as a read-only connection label, with an Open cloud dashboard link in Managed mode. Change connection settings in Configure. Overview metrics use backend summary counts for the last 30 days, rather than list limits. Connection failures are shown explicitly. Older skill citations without a project/shared identity remain visible under Legacy skill usage; exact per-skill counts use identified citations. A backend must be configured and reachable to view its data. The dashboard follows the managed Reflexio workspace style: neutral light/dark surfaces, green accents, flat metric bands, and consistent page spacing. The theme switch applies across dashboard, sessions, preferences, skills, and settings. Previously configured connections are retained privately when changing modes. The dashboard currently trusts local OS users: other accounts on a shared machine can access its configured backend connections. Per-user dashboard authentication requires a separate change.
This device lists local session buffers and hook activity separately. Those counts can differ between machines connected to the same managed account.
Review the configuration before installation starts. Saved settings and installed
agents are preselected on subsequent runs. Preparation and service startup show
phase and elapsed progress; detailed logs live in ~/.claude-smart/install-logs/.
If an integration fails, the others still install and the summary reports each result.
Runtime environments remain separate so an agent's rollback cannot break another.
For an unattended first install, specify the backend. Multiple agents can be installed in one command:
npx claude-smart install --host claude-code,codex --backend local --provider codex
npx claude-smart install --host opencode --backend local --provider opencode --global
For managed mode, supply the API key through a named environment variable rather than a command-line argument:
npx claude-smart install --host claude-code,codex --backend managed \
--url https://www.reflexio.ai/ --api-key-env REFLEXIO_API_KEY
Existing --host codex and --host opencode commands still work. Without a terminal,
saved backend/provider settings are reused; a fresh install requires --backend.
Use --yes to skip interactive questions when all required settings are supplied
or saved. For multiple local agents, specify --provider unless one is already saved.
Use --read-only to retrieve memories without publishing interactions, or --learn
to resume learning. The interactive guide offers both modes for either backend.
Setup reads legacy duplicate settings with the same field rules as the runtime:
shared connection/learning fields use the last assignment (including empty), while
caller-overridable execution flags use the first nonempty saved assignment.
Legacy connection fallback treats the endpoint and API key as a pair. If the
current settings contain either assignment, even empty, setup does not borrow
the other from ~/.reflexio/.env. An incomplete managed connection needs its own
key. Legacy read-only and other runtime preferences still migrate independently.
Setup, Codex hooks, the dashboard, and the shell/Python readers all accept plain
assignments and export followed by spaces or tabs.
Explicit caller and setup choices retain their existing precedence. Reading or
cancelling setup does not rewrite the file or prepare a settings publisher.
Legacy migration preserves the selected original value text, including Windows
path quoting; only the assignment prefix is normalized.
Confirmation uses the same native lock and private atomic settings owner as the dashboard and dependency repair. One captured preview drives the save; concurrent edits require a fresh preview. Setup prepares a small temporary Python writer from locked dependencies before changing settings. A preparation failure leaves settings unchanged. Confirmed settings remain available if a later integration install fails. Publisher child processes, including UV installation, have a two-minute deadline. On timeout, setup stops their owned process trees. If publication cannot be confirmed, setup stops before installing integrations; reload settings before retrying.
Migration completion is recorded as a fixed first-line comment in that same atomic settings write, after an optional UTF-8 BOM. Matching text inside a value is not migration metadata. Existing migration sidecars are still recognized without rewriting them. Later setup runs do not reimport deleted legacy preferences after migration has completed.
The confirmed guide owns connection, learning, sharing, and read-only choices. Host workers consume those saved choices; installing or removing another agent does not rewrite a shared learning host. Each prepared runtime uses the same Python repair owner to supply only missing local defaults, with native locking