Aient
Use this skill when a user asks for Aient operational context from Codex. The
plugin exposes the production Aient MCP server at https://aient.ai/mcp.
The MCP server is the source of truth for tool schemas; discover/use the live
tools rather than relying on a memorized subset.
First Call
Start with verify_connection when checking whether the plugin is available.
It confirms the organisation, granted scopes, token expiry, and live tool count.
MCP Tool Surface
Prefer the current granular tools over the retired early-preview names
telemetry_overview, log_search, and trace_timeline.
Connection and discovery:
verify_connection: confirm auth and available MCP tools.
describe_telemetry: discover services, operations, and attributes.
service_health_summary: get an at-a-glance service health overview.
Telemetry:
query_traces: aggregate trace metrics such as count, error rate, and latency.
query_logs: aggregate log metrics by service, severity, or time.
get_spans: fetch raw spans for a trace or filtered operation set.
get_logs: fetch raw log entries and attributes.
detect_anomalies: detect statistical deviations in trace/log metrics.
Problems and lifecycle:
list_problems: list detected problems with status, severity, priority, and
environment filters.
get_problem: inspect a problem, recent occurrences, and triage context.
acknowledge_problem, mute_problem, unmute_problem,
dismiss_problem, resolve_problem, restore_problem_status,
update_problem_priority, and batch_problem_action: apply lifecycle
actions to one or more problems.
Remediation:
request_fix: spawn an AI remediation agent for a problem.
get_problem_fix: inspect a remediation attempt.
list_problem_fixes: list remediation attempts for a problem.
list_active_fixes: list in-progress remediation work across the
organisation.
Threads:
get_thread: inspect a thread journal and current agent activity.
send_thread_message: send a message to a thread's agent.
respond_to_interaction: answer an agent interaction/awakeable.
Environment and key management:
list_environments: inspect deployment environments.
list_environment_keys, create_environment_key, revoke_environment_key:
manage publishable telemetry ingest keys.
list_api_keys, create_api_key: manage secret API keys for sourcemaps or
complete API access. create_api_key returns the full key exactly once.
Operating Rules
- Prefer the MCP tools for live Aient telemetry and key-management tasks.
- Do not use local development MCP endpoints unless the user explicitly asks for
a local/dev environment.
- Never copy secrets or local credentialed MCP configuration into responses,
plans, or plugin files.
- Read-only tools require
aient.mcp.read; mutating tools require
aient.mcp.write.
- For
create_api_key, tell the user that the returned key is shown once and
should be stored immediately.
- For telemetry queries, prefer
environmentSlug over environmentId when the
user names an environment, and never pass the all-zero UUID placeholder.
- Treat
401 as missing or expired OAuth, 403 as insufficient scope, and a
missing organisation claim as an auth-context issue.
1---2name: aient3description: Use when the user asks Codex to inspect Aient telemetry, search logs, explain traces, create/list Aient API keys, or use the Aient MCP server.4license: Proprietary5metadata:6 source: https://skillmd.com/skills/hashgraph-online/aient7---89# Aient1011Use this skill when a user asks for Aient operational context from Codex. The12plugin exposes the production Aient MCP server at `https://aient.ai/mcp`.13The MCP server is the source of truth for tool schemas; discover/use the live14tools rather than relying on a memorized subset.1516## First Call1718Start with `verify_connection` when checking whether the plugin is available.19It confirms the organisation, granted scopes, token expiry, and live tool count.2021## MCP Tool Surface2223Prefer the current granular tools over the retired early-preview names24`telemetry_overview`, `log_search`, and `trace_timeline`.2526Connection and discovery:27- `verify_connection`: confirm auth and available MCP tools.28- `describe_telemetry`: discover services, operations, and attributes.29- `service_health_summary`: get an at-a-glance service health overview.3031Telemetry:32- `query_traces`: aggregate trace metrics such as count, error rate, and latency.33- `query_logs`: aggregate log metrics by service, severity, or time.34- `get_spans`: fetch raw spans for a trace or filtered operation set.35- `get_logs`: fetch raw log entries and attributes.36- `detect_anomalies`: detect statistical deviations in trace/log metrics.3738Problems and lifecycle:39- `list_problems`: list detected problems with status, severity, priority, and40 environment filters.41- `get_problem`: inspect a problem, recent occurrences, and triage context.42- `acknowledge_problem`, `mute_problem`, `unmute_problem`,43 `dismiss_problem`, `resolve_problem`, `restore_problem_status`,44 `update_problem_priority`, and `batch_problem_action`: apply lifecycle45 actions to one or more problems.4647Remediation:48- `request_fix`: spawn an AI remediation agent for a problem.49- `get_problem_fix`: inspect a remediation attempt.50- `list_problem_fixes`: list remediation attempts for a problem.51- `list_active_fixes`: list in-progress remediation work across the52 organisation.5354Threads:55- `get_thread`: inspect a thread journal and current agent activity.56- `send_thread_message`: send a message to a thread's agent.57- `respond_to_interaction`: answer an agent interaction/awakeable.5859Environment and key management:60- `list_environments`: inspect deployment environments.61- `list_environment_keys`, `create_environment_key`, `revoke_environment_key`:62 manage publishable telemetry ingest keys.63- `list_api_keys`, `create_api_key`: manage secret API keys for sourcemaps or64 complete API access. `create_api_key` returns the full key exactly once.6566## Operating Rules6768- Prefer the MCP tools for live Aient telemetry and key-management tasks.69- Do not use local development MCP endpoints unless the user explicitly asks for70 a local/dev environment.71- Never copy secrets or local credentialed MCP configuration into responses,72 plans, or plugin files.73- Read-only tools require `aient.mcp.read`; mutating tools require74 `aient.mcp.write`.75- For `create_api_key`, tell the user that the returned key is shown once and76 should be stored immediately.77- For telemetry queries, prefer `environmentSlug` over `environmentId` when the78 user names an environment, and never pass the all-zero UUID placeholder.79- Treat `401` as missing or expired OAuth, `403` as insufficient scope, and a80 missing organisation claim as an auth-context issue.