aios-onboard-client

Drives a client's 11-step onboarding run and seals access credentials into an encrypted vault.

1|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/codesofadan/danyals-aios --skill aios-onboard-client-codesofadan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aios-onboard-client
Source: https://github.com/codesofadan/danyals-aios/tree/main/.claude/skills/aios-onboard-client
Command: npx skills add https://github.com/codesofadan/danyals-aios --skill aios-onboard-client-codesofadan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agency operators lose track of where each new client stands during onboarding and often confuse a typed-in credential with one that actually works. This Skill drives a client's onboarding run through its 11 defined steps, seals collected GBP, CMS, analytics, and Search Console logins into the encrypted vault, and keeps the sealed-versus-verified distinction honest so untested access is never reported as working. ## Core Features & Use Cases - Run lifecycle management: Create or read a client's onboarding run, advance individual steps, and complete the run only when no steps remain unresolved. - Credential sealing with verification tracking: Seal secrets into the vault on the four collect_* steps while enforcing that verified flips only after a human explicitly confirms a successful sign-in. - Status reporting: Render a pinned output summarizing run progress, per-step status, and credential verification state, with secrets never echoed back. - Use Case: An operator onboards a new local SEO client, records their Google Business Profile login, and asks what onboarding work is still outstanding before the first report is due. ## Quick Start Start onboarding for client "Acme Dental" and show me which steps are still outstanding.

Frequently Asked Questions about aios-onboard-client

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start onboarding a new client?▼

Resolve the client name to a client_id, then POST to /client-onboarding/runs with that id to create a run using the local_seo_default template. If the client already has an active run, the API returns 409 and you read the existing run instead.

How do I record a client's GBP or CMS login during onboarding?▼

Advance one of the four collect_* steps (collect_gbp, collect_website_cms, collect_analytics, collect_search_console) with a credential object containing a label and secret. The secret is sealed into the encrypted vault and can never be read back.

Does a sealed credential mean the client's access works?▼

No. Sealing only proves someone typed a secret into the vault; it says nothing about whether the login works. The verified flag flips to true only when a human explicitly confirms they signed in successfully.

Why can't I attach a credential to the brand_assets step?▼

Only steps whose key starts with collect_ may carry a credential, and brand_assets does not match that prefix despite its label. The API returns 400 "Only a collect_* step may carry a credential" if you try.

Why does completing an onboarding run return a 422 error?▼

A 422 from the complete endpoint means steps remain unresolved, and the response lists their labels. Resolve or deliberately skip those steps; only use the force option if the operator explicitly accepts closing an incomplete onboarding.

Can I read back a sealed credential to confirm it?▼

No. The secret field exists only on the request model and appears in no response, and there is no reveal path in this module. Secrets go into the vault and are never displayed or echoed.