gsync-onboarding

Draft and initialize a repo-local .gsync setup with config.json and collection docs.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/nwang783/gsync --skill gsync-onboarding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsync-onboarding
Source: https://github.com/nwang783/gsync/tree/main/skills/gsync-onboarding
Command: npx skills add https://github.com/nwang783/gsync --skill gsync-onboarding

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gsync onboarding creates a repo-local context by establishing a minimal .gsync structure and drafting initialization docs, enabling fast, repeatable onboarding.

Core Features & Use Cases

  • Initializes or extends .gsync/ in the current repository
  • Drafts the initial .gsync/config.json, .gsync/GSYNC.md, and first collection docs
  • Provides a repeatable onboarding flow that hands over to the steady-state GSYNC skill

Quick Start

Run this skill to draft and apply the initial .gsync setup, including config.json and documentation, for the current project.

Frequently Asked Questions about gsync-onboarding

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

FAQPage Schema
How do I initialize a local repo setup for gsync?

To initialize a local gsync setup, run this skill to draft and apply a minimal .gsync directory structure, including config.json and initial collection docs, for your current project repository.

What is the purpose of the .gsync directory and collection docs?

The .gsync directory houses config.json, GSYNC.md, and collection docs to establish repo-local context. It captures initial conventions, enabling fast and repeatable onboarding before handing over to steady-state operations.

Can I extend an existing gsync configuration if a .gsync directory already exists?

Yes, you can extend an existing gsync configuration. This skill applies to projects lacking a .gsync directory or those needing extension of the current setup by drafting and applying additional initialization docs.

What files are generated when setting up gsync onboarding?

Setting up gsync onboarding generates the initial .gsync/config.json for configuration, .gsync/GSYNC.md for conventions, and the first collection docs to establish a repeatable onboarding flow for the repository.

When do I need to draft collection docs for my repository?

You need to draft collection docs when initializing or extending a .gsync setup in your current repository. This ensures initial conventions are captured, providing a repeatable onboarding flow that hands over to steady-state operations.