onboard-me

Synthesize onboarding briefings from project knowledge vaults using salvador_core operations.

6|3|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/adrozdenko/soleri --skill onboard-me
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard-me
Source: https://github.com/adrozdenko/soleri/tree/main/agents/salvador-filetree/skills/onboard-me
Command: npx skills add https://github.com/adrozdenko/soleri --skill onboard-me

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and immediate introduction to a project's knowledge, patterns, decisions, and conventions, eliminating the need for lengthy manual onboarding or tribal knowledge transfer.

Core Features & Use Cases

  • Project Overview: Delivers a concise summary of the project's identity, rules, and conventions.
  • Knowledge Landscape: Maps out the project's documented knowledge across domains and tags.
  • Critical Information: Highlights essential rules, key architectural decisions, proven patterns, and anti-patterns to avoid.
  • Contextual Links: Shows connections to other projects and shared patterns.
  • Knowledge Gap Identification: Points out areas where documentation is lacking, guiding further inquiry.
  • Use Case: A new developer joins a project and, by invoking this Skill, receives a comprehensive 5-minute briefing covering all essential aspects of the project's architecture, best practices, and potential pitfalls.

Quick Start

Use the onboard-me skill to get a structured tour of the project's knowledge.

Frequently Asked Questions about onboard-me

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

FAQPage Schema
How do I automate developer onboarding for a new software project?

Automate developer onboarding by synthesizing project identity, rules, conventions, and architectural decisions from a knowledge vault to deliver a comprehensive project briefing. This eliminates manual knowledge transfer by providing new members with an immediate, structured introduction to critical project information.

What is the best way to document architectural decisions and anti-patterns for new team members?

Documenting architectural decisions and anti-patterns is best handled by centralizing them in a knowledge vault for automated retrieval. This ensures new developers receive a consistent briefing on proven patterns, critical rules, and pitfalls to avoid without relying on tribal knowledge.

Can I get an instant project overview covering conventions and knowledge gaps?

You can get an instant project overview that maps documented knowledge across domains while highlighting knowledge gaps. It synthesizes project rules, conventions, and connections to other projects to guide further inquiry where documentation is lacking.

Does developer onboarding work without manually transferring tribal knowledge?

Developer onboarding works without tribal knowledge by retrieving critical information from a knowledge vault using automated operations. It provides a 5-minute briefing covering architecture, best practices, and potential pitfalls, bypassing the need for lengthy manual onboarding sessions.

How do I map out a project's knowledge landscape and shared patterns?

Map a project's knowledge landscape by retrieving documented knowledge across domains and tags from a central vault. This process outlines essential rules, architectural decisions, and contextual links to shared patterns and other connected projects.

What are the limitations of automated project intelligence tours?

Automated project intelligence tours are limited by the contents of the underlying knowledge vault, meaning they can only highlight knowledge gaps where documentation is lacking. They rely on available synthesized data and cannot provide insights into undocumented conventions.