agent-onboarding

Scan repository structure, detect tech stack, and build a .agent/ context.

4|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill agent-onboarding-ryan-nguyen-01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-onboarding
Source: https://github.com/ryan-nguyen-01/agent-platform/tree/main/.claude/Agents/agent-onboarding
Command: npx skills add https://github.com/ryan-nguyen-01/agent-platform --skill agent-onboarding-ryan-nguyen-01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding a new or joining project can be chaotic and error-prone. This skill automates the initial project reconnaissance and .agent/ context setup, reducing manual work and ensuring consistent onboarding.

Core Features & Use Cases

  • Scans project structure to identify root folders, entry points, and package layouts.
  • Detects tech stack and architectural patterns to bootstrap a tailored agent ecosystem.
  • Writes a ready-made .agent/ context and prompts for ambiguities to generate dev agents.

Quick Start

Run onboarding to scan your repo and generate a ready-to-use .agent/ context.

Frequently Asked Questions about agent-onboarding

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

FAQPage Schema
How do I automate project onboarding and generate developer agents?

Automate project onboarding by scanning the repository structure, detecting the tech stack, and building a .agent/ context. This generates production-ready dev agents and orchestrates context management to bootstrap your environment.

What is a .agent/ context and when do I need to set it up?

A .agent/ context is a structured configuration directory generated for onboarding. You need it when joining existing projects or starting new ones to ensure consistent context management and production-ready agent orchestration.

Can I use automated onboarding for an existing repository with an unknown tech stack?

Yes, automated onboarding applies to existing repositories. It scans root folders and package layouts to detect architectural patterns, prompts for ambiguities, and bootstraps a tailored agent ecosystem for the detected tech stack.

What's the best way to bootstrap a development agent ecosystem for a new project?

The best way is running an automated onboarding scan that integrates with an agent-builder and orchestrator. This writes a ready-made .agent/ context, resolving ambiguities and generating dev agents for production-ready orchestration.

Does project onboarding handle ambiguous tech stack detection during repository scanning?

Yes, project onboarding handles ambiguous tech stack detection by prompting the user for clarification. It scans the repository structure and asks questions to accurately resolve architectural patterns before generating dev agents.