AML authoring skill

The AML authoring skill gives a compatible coding agent the project’s current API, composition rules, provider boundaries, and security guidance. It is useful when an agent is creating or reviewing AML code; it is not a runtime dependency and does not install the SDK or provider executables for your application.

Install the skill

Run the project-local install from the repository where you want an agent to use AML:

npx skills add we-are-singular/aml \
  --skill aml-jsx

The Skills CLI detects compatible clients and asks where to install when a choice is required. To target a supported client explicitly, pass its client identifier:

npx skills add we-are-singular/aml \
  --skill aml-jsx \
  --agent codex

Use a global install only when you want the skill available across projects:

npx skills add we-are-singular/aml \
  --skill aml-jsx \
  --global

Verify the installation

List project-local skills as machine-readable output:

npx skills list --json

For a global installation:

npx skills list --global --json

Confirm that the result contains aml-jsx. If you targeted one client, you can also filter the listing with --agent <client>.

The canonical source remains skills/aml-jsx/SKILL.md. Review that file when you need to confirm exactly what an installed copy teaches an agent.

What the skill asks an agent to do

Preflight the project. Confirm Node.js, ESM, TypeScript, JSX runtime configuration, and the public @aml-jsx/sdk package boundary.
Choose explicit providers. Separate the Agent, Sandbox, and Workspace responsibilities and check each provider’s prerequisites.
Author the smallest complete tree. Keep ordinary branching and concurrency in TypeScript while AML owns dependency resolution and resource scopes.
Review authority and lifecycle. Treat Sandbox isolation, credentials, Workspace publication, cancellation, and cleanup as explicit application decisions.
Verify against public contracts. Use public SDK imports, compile the workflow, and distinguish deterministic checks from vendor integration evidence.

The skill routes an agent to focused references for composition, capabilities, resources, providers, and security. It deliberately tells the agent not to invent SDK exports or silently add infrastructure.

What the skill does not do

It does not install AML

Your application still needs npm install @aml-jsx/sdk, an ESM/TSX configuration, and a way to execute or compile TypeScript.

It does not install providers

Codex ACP, GitHub Copilot CLI, OpenCode, Pi, Docker, and remote provider clients remain explicit deployment prerequisites.

It does not grant authority

A skill can guide code generation, but only your selected Sandbox and deployment policy control processes, files, network access, and credentials.

It does not replace these docs

Provider versions and public contracts can change while AML is pre-stable. Use the linked documentation and source as the current authority.

A useful first prompt

After installation, give the agent a concrete provider and safety boundary instead of asking only for “an AML workflow”:

Use the aml-jsx skill to create a credential-free AML workflow first.
Then show the smallest change required to run it with Codex inside Docker.
Keep secrets outside the AML tree and explain the Workspace save policy.

This prompt forces the important choices into the open: deterministic versus live execution, Agent provider, Sandbox authority, and durable state.

Update or remove

Refresh the installed copy when the SDK or docs change:

npx skills update aml-jsx

Remove the project-local skill with the interactive remover, or name it directly:

npx skills remove aml-jsx

For a global installation, add --global to the update or remove command.