# your-org

**Repository Path**: jerryzu/your-org

## Basic Information

- **Project Name**: your-org
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-04-16
- **Last Updated**: 2026-04-16

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# @your-org/your-cli

Your custom CLI tool with skill installation support.

## Overview

This is a minimal implementation of a CLI tool that supports `install --skills` for coding agents (like Claude Code). It demonstrates how `@playwright/cli` works with `playwright-core` to provide skill installation functionality.

## Architecture

```
your-org/
├── your-core/           # Core library with CLI implementation
│   ├── lib/
│   │   └── tools/cli-client/program.js   # Main CLI program
│   ├── skills/          # Skills source (copied during install --skills)
│   │   └── your-skill/
│   └── package.json
│
└── your-cli/            # CLI package (the one users install)
    ├── your-cli.js      # Entry point
    ├── package.json
    └── skills/          # Optional: extra skills
```

### How it works

1. `your-cli.js` calls `your-core`'s `program()` function
2. `program()` handles CLI arguments and commands
3. When `install --skills` is called, it copies skills from `your-core/skills/` to `.claude/skills/`

## Quick Start

### Setup

```bash
cd your-org

# Install dependencies
npm install

# Link packages for local development
npm run link
```

### Usage

```bash
# Show help
your-cli --help

# Show version
your-cli --version

# Initialize workspace
your-cli install

# Install skills for coding agents
your-cli install --skills
```

## Project Structure

### your-core

The core library that provides CLI functionality.

```
your-core/
├── lib/
│   └── tools/cli-client/
│       └── program.js      # CLI program with install --skills
├── skills/                 # Skills source files
│   └── your-skill/
│       ├── SKILL.md
│       └── references/
│           └── tasks.md
└── package.json
```

**Key exports:**
- `program()` - Main CLI entry point

### your-cli

The npm package that users install.

```
your-cli/
├── your-cli.js            # Entry point
├── package.json
└── skills/               # Optional extra skills
```

## Creating Your Own

### 1. Modify the skill content

Edit files in `your-core/skills/your-skill/`:
- `SKILL.md` - Main skill file with YAML frontmatter
- `references/` - Additional reference documents

### 2. Change the skill name

In `your-core/lib/tools/cli-client/program.js`, change:

```javascript
const skillName = 'your-skill';
```

And rename the skill folder:

```bash
mv your-core/skills/your-skill your-core/skills/my-new-skill
```

### 3. Change package names

In `your-core/package.json`:
```json
{
  "name": "@your-org/your-core"
}
```

In `your-cli/package.json`:
```json
{
  "name": "@your-org/your-cli",
  "dependencies": {
    "@your-org/your-core": "1.0.0"
  }
}
```

## Publishing

### Pre-requisites

```bash
# Login to npm
npm login

# Add your org to package.json if needed
```

### Publish packages

```bash
# Publish your-core first
cd your-core
npm publish --access public

# Then publish your-cli
cd ../your-cli
npm publish --access public
```

### Version management

```bash
# Update version in both packages
cd your-core
npm version patch  # or minor, major

cd ../your-cli
npm version patch
```

## SKILL.md Format

```markdown
---
name: your-skill
description: Brief description of your skill
allowed-tools: Bash(your-cli:*) Bash(npm:*)
---

# Your Skill Title

Your skill documentation here...

## Commands

```bash
your-cli command arg
```
```

## License

MIT