onboard

Orchestrates end-to-end frndOS workspace onboarding from bootstrap to environment provisioning.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/alva-intelligence/agentic-workflows --skill onboard-alva-intelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/alva-intelligence/agentic-workflows/tree/main/skills/onboard
Command: npx skills add https://github.com/alva-intelligence/agentic-workflows --skill onboard-alva-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Onboard new frndOS workspaces by configuring GitHub access, service wiring, dependencies, editor config, and MCP setup so teams start with a ready-to-use development environment after bootstrap.

Core Features & Use Cases

  • End-to-end onboarding covering GitHub access, service provisioning, environment setup, editor configuration, and MCP registration.
  • STEP-driven guidance with STOP markers to collect user input before proceeding, ensuring safe, customized setups.
  • Centralized references and templates to speed up repeated workspace initializations across API, web, ai-service, and data-service contexts.

Quick Start

Run the bootstrap sequence after bootstrap to initialize your frndOS workspace and begin onboarding.

Frequently Asked Questions about onboard

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

FAQPage Schema
How do I set up a multi-service development workspace after bootstrap?

Workspace onboarding for multi-service environments coordinates GitHub access, service provisioning, dependency wiring, editor configuration, and MCP registration. It applies stepwise guidance with mandatory prompts for user input to ensure safe, customized setups across API, web, ai-service, and data-service contexts.

How do I provision a development environment for API, web, and ai-service components?

To provision a development environment for API, web, and ai-service components, apply a stepwise plan that coordinates service wiring, dependencies, and editor config. The process validates readiness and maintains a persistent onboarding state before enabling workflow start.

What is the best way to wire MCP connections during workspace initialization?

The best way to wire MCP connections during workspace initialization is through a centralized onboarding sequence that registers MCP configurations alongside GitHub access and editor setup. This ensures all services are correctly provisioned before the workflow begins.

Does the onboarding process require manual user input during environment provisioning?

Yes, the onboarding process requires manual user input during environment provisioning. It implements STEP-driven guidance with STOP markers to collect user input before proceeding, ensuring safe and customized setups for your specific multi-service workspace.

Can I reuse onboarding configurations for repeated workspace initializations across different services?

Yes, you can reuse onboarding configurations for repeated workspace initializations. The process utilizes centralized references and templates to speed up repeated initializations across API, web, ai-service, and data-service contexts.