exeora-setup
/exeora-setup
Connect Exeora and discover authorized remote projects and workspaces. Use for Exeora onboarding, missing access or offline machines.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.
What it does and when to use it
Connect Exeora and discover authorized remote projects and workspaces. Use for Exeora onboarding, missing access or offline machines.
Original author description
Connect Exeora and discover authorized remote projects and workspaces. Use for Exeora onboarding, missing access or offline machines.
How it works
SKILL.md has no level-two headings · 13 lines, 280 words
SKILL.md preview
--- name: exeora-setup description: Connect Exeora and discover authorized remote projects and workspaces. Use for Exeora onboarding, missing access or offline machines. --- # Set up Exeora Use only the Exeora MCP tools actually exposed by the host. The fixed remote endpoint is `https://exeora.dev/mcp`. Authentication is managed by the host; package installation alone does not establish access. Never request passwords, tokens or client secrets in chat. 1. If tools are missing, use the host's documented plugin/MCP connection workflow. Cursor can discover an extracted plugin in its allowed local plugin directory or an approved marketplace. Grok Bot documents catalog installation and provider authorization only; do not invent custom ZIP import or assume Cursor installation carries over. 2. Call `list_projects`, using the advertised names and schemas, including any namespace. Show returned names and states. Use the returned project slug or ID, then call `list_workspaces` and select the requested workspace. If selection is ambiguous, ask the user; never silently fall back to main after an error. 3. If there are no projects, explain adding a project at https://exeora.dev/dashboard/ or with `exeora project add /path/to/project` on the user's machine. Existing access may be restricted to authorized projects. Do not create projects, expand grants or change persistent approvals just for setup. 4. Keep the project/workspace selectors on every subsequent call; selection is not a persistent server setting. For offline machines explain that `exeora connect` must remain running on the machine holding the project. A waking Cloud executor permits at most two retries of the same read; never silently change location. 5. Report only tool-observed access, selected location and next useful request. Onboarding does not authorize edits, workspace creation, commands, commits or publication. Respect the user's scope, the host's approval prompts and Exeora's enforced project policy. Missing tools or `FORBIDDEN`, `APPROVAL_DECLINED` and `APPROVAL_TIMEOUT` are not permission to bypass restrictions.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · leynier/exeora | 86 | AGPL-3.0 |
| leynier/exeora | 86 | AGPL-3.0 |
| leynier/exeora | 86 | AGPL-3.0 |
| leynier/exeora | 86 | AGPL-3.0 |
| leynier/exeora | 86 | AGPL-3.0 |
Database snapshot: 13.11.2026 · package version 4faacf9c010c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86exeora-project
Explore, diagnose, edit and test code through Exeora remote project tools. Use for authorized coding work on Exeora machines or Cloud workspaces. - 86exeora-project
Explore, diagnose, edit and test code through Exeora remote project tools. Use for authorized coding work on Exeora machines or Cloud workspaces.