You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: elnora/.claude-plugin/plugin.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
{
2
2
"name": "elnora",
3
-
"version": "1.3.5",
3
+
"version": "1.4.0",
4
4
"description": "AI-powered bioprotocol generation and lab workflow management. Connect to the Elnora AI Platform to generate, optimize, and manage bioprotocols for wet-lab experiments.",
- Windows (PowerShell): `irm https://cli.elnora.ai/install.ps1 | iex`
26
-
- Any platform with Node.js: `npm install -g @elnora-ai/cli`
22
+
**Option A — CLI via Bash (preferred)**
27
23
28
-
**CLI is the recommended path** — it uses fewer tokens, is more reliable, and the commands below are ready to copy-paste.
24
+
Run commands via your Bash/Shell tool as `elnora <group> <action> ...`. Verify with `elnora --version`. CLI uses ~5× fewer tokens than MCP.
29
25
30
-
If MCP tools prefixed `mcp__elnora__` are available in your tool list, they work too — use whichever the user prefers or whichever is already configured in your environment.
26
+
**Option B — MCP tools (when CLI isn't installed)**
31
27
32
-
**Never fabricate function names** like `elnora_generate_protocol`. All valid commands are listed under "Commands" in this skill.
28
+
Look for tools prefixed `mcp__elnora__` in your available tools. Call them with structured parameters (camelCase — e.g. `projectId`, not `project-id`). See the "MCP Tool Names" table below for the mapping.
29
+
30
+
**If neither is available, tell the user to install one:**
**Never fabricate tool names.** Valid commands are in the Commands section; their MCP equivalents are in the MCP Tool Names table.
33
38
34
39
## Invocation
35
40
@@ -263,7 +268,7 @@ No auth required. Returns `{"status":"ok","timestamp":"..."}` on success. Exits
263
268
$CLI doctor
264
269
```
265
270
266
-
Runs diagnostic checks: API reachability, authentication, version currency, config permissions, AI server reachability.
271
+
Runs 10 diagnostic checks across three sections: **CLI** (API reachability, authentication, version currency, config permissions, AI server reachability, PATH configured), **Claude Code** (plugin enabled, skills installed, plugin version match), and **MCP** (server reachable). Each check reports pass / fail / warn / skip; the summary line shows the tally.
elnora completion fish >~/.config/fish/completions/elnora.fish
302
307
```
303
308
309
+
## MCP Tool Names
310
+
311
+
All commands in this skill are auto-registered as MCP tools. The mapping is `elnora <group> <action>` → `elnora_<group>_<action>` (camelCase preserved; only dots are replaced with underscores).
or any question about what the Elnora AI Agent can do when you send it a task.
11
12
---
12
13
@@ -16,20 +17,30 @@ The Elnora Agent is a sandboxed Python environment with ~78 core tools + 2,100 T
16
17
17
18
## Tool Access
18
19
19
-
Elnora is a**command-line tool**. Run commands via your Bash/Shell tool.
20
+
This skill documents**what the Elnora Agent can do**. It does not have dedicated CLI commands — interact with the agent through the `elnora-tasks` skill.
20
21
21
-
-**Command:**`elnora`
22
-
-**Verify:**`elnora --version`
23
-
-**If not found:** tell the user to install it. Detect their platform:
- Windows (PowerShell): `irm https://cli.elnora.ai/install.ps1 | iex`
26
-
- Any platform with Node.js: `npm install -g @elnora-ai/cli`
22
+
Elnora is available via two methods. Use whichever is configured.
27
23
28
-
**CLI is the recommended path** — it uses fewer tokens, is more reliable, and the commands below are ready to copy-paste.
24
+
**Option A — CLI via Bash (preferred)**
29
25
30
-
If MCP tools prefixed `mcp__elnora__` are available in your tool list, they work too — use whichever the user prefers or whichever is already configured in your environment.
26
+
Run commands via your Bash/Shell tool as `elnora tasks create ...`or `elnora tasks send ...`. Verify with `elnora --version`.
31
27
32
-
**Never fabricate function names** like `elnora_generate_protocol`. All valid commands are listed under "Commands" in this skill.
28
+
**Tip:** Add `--stream` for real-time agent output:
**Option B — MCP tools (when CLI isn't installed)**
33
+
34
+
Look for tools prefixed `mcp__elnora__` in your available tools — specifically `mcp__elnora__elnora_tasks_create` and `mcp__elnora__elnora_tasks_send`. Call them with structured parameters (camelCase).
35
+
36
+
**If neither is available, tell the user to install one:**
**Never fabricate tool names** like `elnora_generate_protocol`. The agent is interacted with via `tasks.create` and `tasks.send` only — see the `elnora-tasks` skill for full command reference.
- Windows (PowerShell): `irm https://cli.elnora.ai/install.ps1 | iex`
24
-
- Any platform with Node.js: `npm install -g @elnora-ai/cli`
21
+
**Option A — CLI via Bash (preferred)**
25
22
26
-
**CLI is the recommended path** — it uses fewer tokens, is more reliable, and the commands below are ready to copy-paste.
23
+
Run commands via your Bash/Shell tool as `elnora <group> <action> ...`. Verify with `elnora --version`. CLI uses ~5× fewer tokens than MCP.
27
24
28
-
If MCP tools prefixed `mcp__elnora__` are available in your tool list, they work too — use whichever the user prefers or whichever is already configured in your environment.
25
+
**Option B — MCP tools (when CLI isn't installed)**
29
26
30
-
**Never fabricate function names** like `elnora_generate_protocol`. All valid commands are listed under "Commands" in this skill.
27
+
Look for tools prefixed `mcp__elnora__` in your available tools. Call them with structured parameters (camelCase — e.g. `projectId`, not `project-id`). See the "MCP Tool Names" table below for the mapping.
28
+
29
+
**If neither is available, tell the user to install one:**
- Windows (PowerShell): `irm https://cli.elnora.ai/install.ps1 | iex`
22
-
- Any platform with Node.js: `npm install -g @elnora-ai/cli`
17
+
**Option A — CLI via Bash (preferred)**
23
18
24
-
**CLI is the recommended path** — it uses fewer tokens, is more reliable, and the commands below are ready to copy-paste.
19
+
Run commands via your Bash/Shell tool as `elnora <group> <action> ...`. Verify with `elnora --version`. CLI uses ~5× fewer tokens than MCP.
25
20
26
-
If MCP tools prefixed `mcp__elnora__` are available in your tool list, they work too — use whichever the user prefers or whichever is already configured in your environment.
21
+
**Option B — MCP tools (when CLI isn't installed)**
27
22
28
-
**Never fabricate function names** like `elnora_generate_protocol`. All valid commands are listed under "Commands" in this skill.
23
+
Look for tools prefixed `mcp__elnora__` in your available tools. Call them with structured parameters (camelCase — e.g. `projectId`, not `project-id`). See the "MCP Tool Names" table below for the mapping.
24
+
25
+
**If neither is available, tell the user to install one:**
- Windows (PowerShell): `irm https://cli.elnora.ai/install.ps1 | iex`
24
-
- Any platform with Node.js: `npm install -g @elnora-ai/cli`
21
+
**Option A — CLI via Bash (preferred)**
25
22
26
-
**CLI is the recommended path** — it uses fewer tokens, is more reliable, and the commands below are ready to copy-paste.
23
+
Run commands via your Bash/Shell tool as `elnora <group> <action> ...`. Verify with `elnora --version`. CLI uses ~5× fewer tokens than MCP.
27
24
28
-
If MCP tools prefixed `mcp__elnora__` are available in your tool list, they work too — use whichever the user prefers or whichever is already configured in your environment.
25
+
**Option B — MCP tools (when CLI isn't installed)**
29
26
30
-
**Never fabricate function names** like `elnora_generate_protocol`. All valid commands are listed under "Commands" in this skill.
27
+
Look for tools prefixed `mcp__elnora__` in your available tools. Call them with structured parameters (camelCase — e.g. `projectId`, not `project-id`). See the "MCP Tool Names" table below for the mapping.
28
+
29
+
**If neither is available, tell the user to install one:**
0 commit comments