Menu

Individual skill

aident-loadout

Coordinate multi-step work across services the user has authorized through Aident Loadout, using live action schemas, connection checks, cost preflight, and explicit approval for side effects.

plugins/Aident-AI/aident-skill/skills/aident-loadout/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 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)
1,531
Repository last updated
Nov 6, 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

# Aident Loadout

Use this Skill when a user asks to discover or perform work across connected services supported by Aident Loadout. Do not invoke it for unrelated questions or when the user only needs an answer from the current conversation.

## Workflow

1. Identify the concrete outcome and the services involved.
2. If the exact canonical Action name is unknown, call `capabilities_search` with a concise description of the operation.
3. Call `capabilities_get` before the first use of an Action to inspect its current input schema, side effects, account requirements, and approval behavior.
4. Use `vault` to check connection status. If a connection is missing, give the user the returned Aident-hosted connection URL. Never request credentials, API keys, MFA codes, or authentication secrets in chat.
5. Call `capabilities_preflight` before a dynamically priced or metered Action. Explain the returned cost or approval requirement before proceeding.
6. Before a side-effecting Action, state the target, effect, and important inputs. Obtain any user acknowledgement required by the Action and preserve the exact acknowledged request.
7. Call `capabilities_execute` with the exact canonical Action name and schema-valid input. Report the result without exposing internal identifiers or private provider data that the user did not request.