Example requests

Discover before creating

Find capabilities that can summarize a support ticket and return structured JSON. Show what is executable now and what would need to be created.

Use this when you want to understand reuse options without immediately authorizing a mutation.

Create a read-only capability

Create a reusable capability that answers questions about the active product catalog. It must be read-only and return the product IDs used in the answer.

Likely follow-ups include the catalog source, required Settings, and approved model. Elyxis uses the Environment already selected in your session. Review any creation confirmation.

Execute with a concrete payload

Run the support-ticket urgency capability with this input:
{"ticket":"Checkout fails after customers enter their card details."}

Providing the exact payload reduces ambiguity. Match the capability's displayed input contract.

Check working context

/context

Requests use the selected Environment unless you explicitly name another one. See Environments when you need to switch.

Refine an active result

Keep the same capability, but return the matched source IDs and exclude archived records.

Use a short refinement only when the current session clearly identifies the capability.

Verify a completed change

Show the capability you just created, including its current readiness and whether it can execute now.

A follow-up read distinguishes successful creation from readiness and execution.

Ask for safe recovery

Explain which non-secret configuration is still missing, where it should be configured in Elyxis, and what I can verify after it is added.

This asks for an actionable next step without requesting internal diagnostics or secret values.