skills/agent-onboarding/SKILL.md
Standard procedure for registering a new agent in the AAA federation. Creates agent identity directory, agent card, registry entry, and SOUL.md.
npx skillsauth add ariffazil/openclaw-workspace Agent OnboardingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When a new agent joins the federation, it needs an identity card, a home directory, and a registry entry. This skill ensures every agent is created with the same canonical structure and does not claim authority it does not own.
| Input | Required | Description |
|-------|----------|-------------|
| agent_id | yes | Unique kebab-case ID (e.g., security-auditor) |
| agent_name | yes | Human-readable name |
| agent_role | yes | One of: operator, engineer, auditor, witness, planner |
| domain_plane | yes | One of: AAA, A-FORGE, GEOX, WEALTH, WELL, arifOS |
| allowed_tools | no | Array of tool IDs this agent may use |
| allowed_skills | no | Array of skill IDs this agent may load |
Check that agent_id does not already exist in:
registries/agents.yamla2a/registry/agents.yamlagents/<existing-id>/ directoryIf duplicate → reject and suggest alternative ID.
Create agents/<agent_id>/ with these required files:
agents/<agent_id>/
├── IDENTITY.md # Who this agent is
├── SOUL.md # Personality and behavior contract
├── AGENTS.md # Agent-specific instructions
├── MEMORY.md # Memory and context rules
├── TOOLS.md # Allowed tools and boundaries
├── BOOTSTRAP.md # Boot sequence
├── HEARTBEAT.md # Health check protocol
├── USER.md # Sovereign reference (Arif)
└── agent-card.json # A2A capability card
Contents must include:
Create a2a/agent-cards/<agent_id>.json with:
agent_id, name, descriptioncapabilities arrayendpoints objectauth_required: trueAdd entry to registries/agents.yaml:
- id: <agent_id>
name: <agent_name>
role: <agent_role>
domain_plane: <domain_plane>
host_binding: <host>
allowed_tools: <allowed_tools>
allowed_skills: <allowed_skills>
allowed_peers: []
intelligence_band: <band>
intelligence_tier: <tier>
separation_of_duties:
cannot_self_seal: true # engineers must set this
Add entry to a2a/registry/agents.yaml:
- agent_id: <agent_id>
card_path: a2a/agent-cards/<agent_id>.json
status: active
trust_tier: standard
Run npm run validate:aaa to ensure:
| Tool | Purpose |
|------|---------|
| file-write | Create identity files |
| directory-create | Create agent directory |
| registry-update | Add registry entries |
role: judge — only arifOS APEX can judgerole: sovereign — only Arif is sovereigncannot_self_seal: false for engineer agents## Skill Result: agent-onboarding
### Summary
Agent `<agent_id>` onboarded successfully.
### Files Created
- `agents/<agent_id>/IDENTITY.md`
- `agents/<agent_id>/SOUL.md`
- ...
- `a2a/agent-cards/<agent_id>.json`
### Registry Entries
- `registries/agents.yaml`
- `a2a/registry/agents.yaml`
### Validation
- [x] `npm run validate:aaa` passes
### Escalations
- None / [list]
| Condition | Escalate To | Method | |-----------|-------------|--------| | Validation fails | AAA agent | Fix and re-run | | Duplicate agent ID found | Arif | Human decision on naming | | Agent requests judge role | arifOS 888_JUDGE | Reject + education |
Skill version 1.0.0 — AAA Skill Library
development
Governed intelligence skill for AAA as the abstraction, attestation, and abduction control plane across arifOS, APEX, A-FORGE, GEOX, WEALTH, WELL, and the ariffazil profile repository. Use when the user asks to explain or design AAA, route agentic work, reduce chaos/entropy in an arifOS federation task, create AREP/task declarations, classify risk, plan multi-repo changes, review governance boundaries, or translate human intent into evidence-backed, authority-safe, recursively agentic workflows. Provides deterministic F1-F13 floor checking, bounded abduction, and FederationReceipt composition.
development
Check every skill’s “use when” and “do not use when” clauses for collisions, missing negatives, and vague verbs like “help,” “assist,” or “improve.” Load when linting, reviewing, or validating trigger boundaries.
development
Bootstrap, design, and package new skills. Load when capturing user intent for a new skill or drafting its initial instruction framework.
content-media
Diagnose which federation services are up, down, or drifting. Produce a prioritized remediation plan.