@yapita-health/agentic-skills 🚀

Automatically add shared SKILLS and AGENTS to all your repositories

What is this?

A lightweight npm package that distributes a shared AW folder (containing SKILLS and AGENTS) across all your repositories. Install once globally, then automatically add the folder to any repository with a single command.

Features

✨ Global Installation - Install once, use everywhere
📦 Zero Dependencies - Uses only Node.js built-in modules
🚀 One Command - Simple aw-setup command to add AW folder
🔄 Easy Updates - Update SKILLS and AGENTS in one place
📝 Smart Copy - Won't overwrite existing AW folders
💻 Cross-Platform - Works on macOS, Linux, and Windows

Quick Start

1. Install Globally

npm install -g @yapita-health/agentic-skills

2. Navigate to Your Repository

cd /path/to/your/repository

3. Run Setup

aw-setup

Done! Your repository now has the AW folder with SKILLS and AGENTS.

Usage

Basic Commands

# Add AW folder to current directory
aw-setup

# Add AW folder to a specific directory
aw-setup /path/to/my/repo

# Check AW folder status
aw-setup --status

# Show help
aw-setup --help

Using SKILLS and AGENTS

// CommonJS
const { skill1, skill2 } = require('./AW/SKILLS');
const { agent1, agent2 } = require('./AW/AGENTS');

// ES6
import { skill1, skill2 } from './AW/SKILLS';
import { agent1, agent2 } from './AW/AGENTS';

Installation Methods

Method 1: Global (Recommended)

npm install -g @yapita-health/aw-setup
aw-setup

Perfect for quick setup in any repository.

Method 2: Local Dev Dependency

npm install --save-dev @yapita-health/aw-setup
npx aw-setup

Add to package.json:

{
  "scripts": {
    "setup": "aw-setup"
  }
}

Then run: npm run setup

Method 3: Batch Setup Script

#!/bin/bash
for repo in ~/projects/*/; do
  cd "$repo" && aw-setup
done

Structure

AW/
├── SKILLS/
│   ├── index.js
│   ├── skill-1/
│   ├── skill-2/
│   └── ...
├── AGENTS/
│   ├── index.js
│   ├── agent-1/
│   ├── agent-2/
│   └── ...
└── README.md

Updating

When new SKILLS or AGENTS are released:

# Update the package
npm install -g @yapita-health/aw-setup@latest

# In each repository
rm -rf AW/
aw-setup

Configuration

Add to .gitignore

# Don't version control auto-generated AW folder
AW/

Or if you prefer to version it, just remove from .gitignore and commit.

CI/CD Integration

GitHub Actions:

- name: Setup AW folder
  run: |
    npm install -g @yapita-health/aw-setup
    aw-setup

GitLab CI:

setup_aw:
  script:
    - npm install -g @yapita-health/aw-setup
    - aw-setup

Troubleshooting

"AW folder already exists"

Delete and regenerate:

rm -rf AW/
aw-setup

"Permission denied" (macOS/Linux)

sudo chown -R $(whoami) ~/.npm
npm install -g @yapita-health/aw-setup

Verify Installation

which aw-setup
npm list -g @yapita-health/aw-setup
aw-setup --version

API Usage (Programmatic)

const { copyAWFolder, getAWFolderPath } = require('@yapita-health/aw-setup');

// Get path to AW template
const awPath = getAWFolderPath();
console.log('AW template at:', awPath);

// Copy to a directory
const success = copyAWFolder('/path/to/repo');
if (success) {
  console.log('✅ AW folder added!');
}

Development

Publishing Updates

1. Update SKILLS/AGENTS in aw-template/
2. Update version in package.json
3. Publish to npm:

npm publish

Local Testing

mkdir test-repo
cd test-repo
npm install -g ../aw-package
aw-setup
ls -la AW/

Best Practices

1. Don't modify AW folder - Changes will be lost on update
2. Add to .gitignore - Avoid committing auto-generated files
3. Keep updated - Regularly update the package
4. Document usage - Help teammates understand how to use SKILLS/AGENTS
5. Version carefully - Use semantic versioning for releases

Contributing

Found a bug or have a feature request? Please open an issue!

License

MIT © Your Organization

Support

• 📖 Full Setup Guide
• 📂 AW Folder README
• 💬 Contact your development team

Happy coding! 🎉