Menu

Individual skill

aai-merkys

0upvotes

Use aai-cli to ask Merkys questions and get grounded answers with cited sources, run deep research, and read its conversations, documents, data sources, and corpora.

api/domains/agents/aai_cli_skills/bundled/skills/aai-merkys/SKILL.md

Read pinned source

Source commit 724a8ace26035d19f64cc707fbc0b4ba110cbc95

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
111
Repository last updated
Nov 9, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# aai-cli Merkys

Use this skill when the answer should come from the organization's Merkys knowledge base (uploaded documents, connected Jira/Confluence/Drive/email sources, and the legal or medical corpora) instead of from your own memory or the web.

Before running commands, confirm the active profile or pass `--profile`. A Merkys profile uses a **user API key** sent in the `X-API-Key` header (`auth_type = "api_key_header"`) and needs a `base_url`. Everything you do is done as the key's owner: you only see what that user's role and access rules allow, and your questions appear in that user's conversation history.

## Which command

- `merkys ask "<question>"` — start here. One command creates a conversation, asks, and returns `{answer, sources, conversation_id, ...}`. Takes roughly 5–30 seconds.
- `merkys research start "<question>" --wait` — for broad questions that need several searches and a written report (about 1–5 minutes). It returns the finished run with `final_report`, `sources`, and `plan`. Without `--wait` it returns a `run_id` at once; check it later with `research get <run-id>`. If `--wait` times out the run keeps going: the error includes the `run_id`.
- `merkys conversations list|search|messages`, `documents list`, `sources list`, `assistants list` — look around: what was asked before, what is uploaded or connected.
- `merkys request GET <path>` — anything else read-only (legal corpus, case law, law commentary, medical corpus, statistics). See [the endpoint reference](references/api-endpoints.md).

## Reading an answer
Back to top