distribute

Copy dotfiles paragon skills, hooks, and CLAUDE.md into a shared team repository.

8|1|Updated Jan 21, 2024
One-click install
npx skills add https://github.com/azigler/dotfiles --skill distribute-azigler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distribute
Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/distribute
Command: npx skills add https://github.com/azigler/dotfiles --skill distribute-azigler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git.

What problem does it solve?

This Skill keeps a teammate’s shared ~/.claude-style setup in sync with your latest dotfiles paragon set, avoiding slow manual copying and drift between repos.

Core Features & Use Cases

  • Distributes paragon skills and hooks: Copies and cleans dotfiles/agents/skills/ into <dest>/.claude/skills/ and dotfiles/agents/hooks/ into <dest>/.claude/hooks/.
  • Publishes team-facing CLAUDE entry content: Copies dotfiles/agents/AGENTS.md to <dest>/CLAUDE.md for the destination’s CLAUDE interface.
  • Manages destination settings safely: Copies dotfiles/claude/settings.json into <dest>/.claude/settings.json only when missing by default, with optional overwrite via --settings.

Quick Start

Run the distribution command to mirror your current dotfiles paragon skills into the LinearB team shared repo (by default ~/linearb/skills).

Frequently Asked Questions about distribute

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

FAQPage Schema
How do I sync dotfiles into a shared CLAUDE configuration tree for my team?

To sync dotfiles into a shared CLAUDE configuration tree, this Skill mirrors paragon skills, hooks, and CLAUDE.md from your central dotfiles directory into a destination repository resembling ~/.claude for team members to pull.

What is the best way to distribute CLAUDE skills and hooks to multiple coworkers?

Distributing CLAUDE skills and hooks to coworkers involves copying cleaned agents/skills and agents/hooks directories from your dotfiles into a shared destination tree, preventing manual copying drift between repositories.

Can I overwrite settings.json when syncing my .claude directory to a team repo?

Yes, you can overwrite settings.json during .claude directory syncing by passing the --settings flag; by default, the destination settings.json is only copied when missing to protect existing configurations.

Do I need bash and git to automate dotfiles distribution for CLAUDE.md?

Yes, bash and git are required dependencies to automate dotfiles distribution for CLAUDE.md, as the process executes a shell script to manage file copying and repository synchronization.

How does copying CLAUDE.md and .claude/skills into a shared repository work?

Copying CLAUDE.md and .claude/skills into a shared repository works by executing a distribution script that cleans and copies your paragon dotfiles directly into a coworker-friendly destination tree structure.

What are the limitations of automatic dotfiles syncing for team CLAUDE setups?

A limitation of automatic dotfiles syncing for team CLAUDE setups is that settings.json is protected from overwriting by default, requiring explicit flags to force updates and avoid clobbering teammate configurations.