project-onboard

Localize global Claude skills into a project's .skills directory.

9|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/mkSteady/mkSkills --skill project-onboard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-onboard
Source: https://github.com/mkSteady/mkSkills/tree/main/project-onboard
Command: npx skills add https://github.com/mkSteady/mkSkills --skill project-onboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly align a new or legacy codebase with standardized Claude workflows by localizing global skills to a project-specific .skills directory.

Core Features & Use Cases

  • Discover and map existing CLAUDE.md and related conventions in the target project.
  • Compare project norms with global skills and propose adaptation suggestions.
  • Generate a localized .skills manifest and integration plan for the team.

Quick Start

Run the onboarding workflow to localize global Claude skills into the project's .skills directory.

Frequently Asked Questions about project-onboard

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

FAQPage Schema
How do I localize global Claude skills for a new project?

Localizing global Claude skills involves exploring the project structure, comparing existing conventions with global standards, and generating a localized .skills directory output to align the codebase with standardized workflows.

What is the best way to align a legacy codebase with Claude conventions?

Aligning a legacy codebase requires running an onboarding workflow that discovers existing CLAUDE.md norms, detects gaps, proposes adaptations, and produces a localized skill manifest for team integration.

Can I use project onboarding automation for a legacy codebase?

Yes, project onboarding automation applies when starting a new or legacy project, mapping existing conventions, scanning available skills, and generating a localized .skills manifest to align workflows.

How does the skill localization workflow detect convention gaps?

The skill localization workflow detects convention gaps by exploring the project structure, comparing existing project norms against available global skills, and proposing targeted adaptations to bridge any differences.

Do I need an existing .skills directory to run project onboarding?

No, you do not need an existing .skills directory. The onboarding workflow generates the localized .skills output and integration plan by scanning available skills and proposing adaptations for the project.

What limitations exist when localizing skills to a project directory?

Localization relies on discovering existing CLAUDE.md and related conventions; projects lacking established normative files may receive less accurate adaptation proposals during the skill localization workflow.