--- name: elnora-platform description: > Use when the user asks about "Elnora platform", "elnora CLI", "platform API", "elnora projects", "elnora tasks", "elnora files", "protocol generation", "platform search", "elnora orgs", "elnora folders", "elnora admin", "API keys", "elnora health", "elnora auth", or any task involving the Elnora AI Platform. Routes to domain-specific sub-skills for token-efficient guidance. --- # Elnora Platform CLI Route Elnora Platform queries to the correct sub-skill. Load only what is needed. ## Tool Access Elnora is a **command-line tool**. Run commands via your Bash/Shell tool. - **Command:** `elnora` - **Verify:** `elnora --version` - **If not found:** tell the user to install it. Detect their platform: - macOS/Linux: `curl -fsSL https://cli.elnora.ai/install.sh | bash` - Windows (PowerShell): `irm https://cli.elnora.ai/install.ps1 | iex` - Any platform with Node.js: `npm install -g @elnora-ai/cli` **CLI is the recommended path** — it uses fewer tokens, is more reliable, and the commands below are ready to copy-paste. 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. **Never fabricate function names** like `elnora_generate_protocol`. All valid commands are listed under "Commands" in this skill. ## Invocation ```bash CLI="elnora" ``` Global flags go BEFORE the subcommand (recommended, always works): ```bash $CLI --compact projects list # recommended $CLI projects list --compact # also works for most commands ``` ## Global Flags | Flag | Effect | |------|--------| | `--compact` | Minified JSON — always use for agent workflows | | `--output ` | Output format (default: json) | | `--fields "id,name"` | Return only these fields | | `--profile ` | Named profile (default: `default`). Set with `auth login --api-key --profile ` | | `--json` | Force JSON output | ## Updates On first use in a session, run `elnora update` to check for updates. If an update is available, inform the user and follow the printed instructions to update. ## Auth Requires `ELNORA_API_KEY` environment variable (prefix: `elnora_live_`), `ELNORA_MCP_API_KEY`, or a saved profile in `~/.elnora/profiles.toml`. ```bash $CLI --compact auth status # -> {"profile":"default","authenticated":true,"projectCount":N} ``` Get keys: platform.elnora.ai > Settings > API Keys ## Routing Table | Need | Sub-skill | Trigger keywords | |------|-----------|------------------| | List/get/create/update/archive projects, manage members | `elnora-projects` | project, workspace, create project, members, add member | | Create/manage/message tasks, protocol generation | `elnora-tasks` | task, protocol, send message, conversation, generate | | Browse/read/upload/create/version/fork files | `elnora-files` | file, content, version history, upload, download, fork, working copy | | Find tasks or files by keyword | `elnora-search` | search, find, query | | Manage project folder trees | `elnora-folders` | folder, create folder, move folder | | Org management, members, billing, invitations, shared library | `elnora-orgs` | organization, org, billing, invite, library | | Auth, API keys, account, health, diagnostics | `elnora-admin` | login, logout, profiles, api key, health, account, feedback, audit, completion | | Feature flags (SystemAdmin) | `elnora-admin` | feature flag, flags, set flag, list flags | | What can the Elnora Agent do? (tools, search, memory) | `elnora-agent` | agent capabilities, agent tools, what can agent do | ## Positional Argument Convention Required string fields ending in `Id` (e.g. `taskId`, `projectId`, `fileId`) become positional arguments. Everything else becomes a flag. ```bash elnora tasks get # taskId -> positional elnora tasks list --project # project -> flag (doesn't end in "Id") elnora files fork --target-project # fileId -> positional, targetProject -> flag ``` **Rule:** positional if and only if the field is: required + not boolean + no enum choices + key ends in "Id". ## ID Format All IDs are UUIDs: `bfdc6fbd-40ed-4042-9ea7-c79a5ec90085`. Invalid format exits 1 with a validation error to stderr. Exception: `account get` and `account update` use `userId` which accepts any string (typically an integer like `42`). ## Pagination List endpoints return: ```json {"items":[...],"page":1,"pageSize":25,"totalCount":N,"totalPages":N,"hasNextPage":true,"hasPreviousPage":false} ``` Use `--page N --page-size N` (max 100). Check `hasNextPage` to paginate. Message endpoints use cursor-based pagination: check `hasMore` and pass `--cursor `. ## Error Contract Errors -> stderr, exit code > 0: ```json {"error":"message","code":"AUTH_FAILED","suggestion":"how to fix"} ``` | Code | Exit | Action | |------|------|--------| | `AUTH_FAILED` | 3 | Check ELNORA_API_KEY env var or profile | | `NOT_FOUND` | 4 | Verify the UUID | | `VALIDATION_ERROR` | 2 | Check parameters | | `RATE_LIMITED` | 5 | Wait and retry (see Rate Limits below) | | `SERVER_ERROR` | 6 | Retry later | | `ELNORA_ERROR` | 1 | Unexpected — report bug | ## Rate Limits HTTP 429 on limit. Check the `Retry-After` header for seconds to wait. | Context | Limit | Window | |---------|-------|--------| | API key (CLI/agent default) | 200 req | 1 min | | Agent processing endpoints | 100 req per task | 1 min | | AI processing (tasks send, protocol generate) | 20 req | 1 min | | Auth endpoints (login, register) | 5 req | 1 min | | Global fallback (per IP) | 1000 req | 1 min | **Agent strategy:** On exit code 5, read `Retry-After` from stderr if available, otherwise wait 60 seconds before retrying. Do not retry in a tight loop. ## File Upload Limits | Constraint | Value | |-----------|-------| | Max file size | 100 MB | | Max filename length | 255 characters | | Max files per batch upload | 50 | | Accepted MIME types | Unrestricted (any type) | | Upload presigned URL expiry | 15 minutes | | Download presigned URL expiry | 5 minutes | ## Common Workflow Projects contain tasks and files. Typical flow: 1. `--compact --fields "id,name" projects list` -> list projects, pick one by name 2. `tasks create --project --message "..." --stream` -> create task and stream the agent response 3. `tasks send --message "..." --stream` -> send follow-up and stream response 4. `tasks messages ` -> read conversation history (or use `--wait` instead of `--stream` in steps 2-3) 5. `files list --project ` -> browse generated outputs 6. `files content ` -> read a protocol file **Project ID:** List projects once (step 1), pick the one matching the user's context, and reuse the ID for all subsequent commands. Don't re-list projects for every task. See `elnora-tasks` skill for full response retrieval details (`--stream`, `--wait`, MCP behavior). ## All Command Groups ``` elnora account Manage user account, agreements, and legal docs elnora api-keys Manage API keys and creation policy elnora audit View audit logs elnora auth Manage authentication elnora completion Generate shell completion script elnora doctor Run diagnostics (API, auth, version, config checks) elnora feedback Submit feedback elnora files Manage project files (incl. batch upload) elnora flags Manage global feature flags (SystemAdmin) elnora folders Manage project folders elnora health Check platform reachability elnora library Manage organization library elnora mcp Run as MCP server (--http or --stdio) elnora open Open platform pages in browser elnora orgs Manage organizations (incl. set-default, delete, list-all) elnora projects Manage projects elnora search Search tasks, files, and file content elnora setup Configure AI coding tools (Claude Code, Cursor, VS Code, Codex) elnora tasks Manage tasks elnora update Check for updates (use --install to apply) elnora whoami Show current profile and org ```