skills/utility-skills/skill-arsenal-builder/SKILL.md
# Skill Arsenal Builder Build unified, organized skill arsenals with discovery systems, shared utilities, meta-skill orchestration, and cross-terminal deployment. --- ## When to Use This Skill - Building a collection of 10+ related skills - Organizing existing skills into a unified system - Creating skill discovery and composition systems - Building meta-skills that orchestrate workflows - Deploying skills across multiple Manus terminals - Setting up cross-terminal skill synchronization ---
npx skillsauth add abcnuts/manus-skills skills/utility-skills/skill-arsenal-builderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Build unified, organized skill arsenals with discovery systems, shared utilities, meta-skill orchestration, and cross-terminal deployment.
Goal: Understand what you have and organize it
Scripts to use:
scripts/audit_skills.py - Audit all skills, generate quality reportscripts/categorize_skills.py - Organize into categoriesscripts/reorganize_skills.py - Restructure directoriesOutput:
Time: 2-3 days
Goal: Create foundation layer to prevent code duplication
Templates to use:
templates/skill_utils.py - Common utilitiestemplates/skill_registry.py - Discovery systemtemplates/skill_composer.py - Workflow orchestrationtemplates/skill_validator.py - Quality assuranceOutput:
Time: 2 days
Goal: Make skills discoverable and composable
Scripts to use:
scripts/generate_manifest.py - Create skills.jsonscripts/enhance_manifest.py - Add metadata and relationshipsOutput:
Time: 2-3 days
Goal: Expand arsenal with additional skills
Process:
Time: Variable (depends on skill count)
Goal: Create orchestration layer
Templates to use:
templates/README_template.md - Arsenal documentationtemplates/ARCHITECTURE_template.md - Technical docstemplates/meta_skill_template.py - Meta-skill orchestratorOutput:
Time: 3 days
Step 1: Build the arsenal (Phases 1-5)
Step 2: Create sync scripts
Use the provided sync script templates:
templates/skill-install - First-time setuptemplates/skill-sync - Update scripttemplates/skill-check - Update checkertemplates/skill-status - Status displayStep 3: Commit to GitHub
cd /path/to/arsenal
git add -A
git commit -m "feat: complete unified skill arsenal"
git push origin main
Step 1: Setup PATH
echo 'export PATH="$PATH:/home/ubuntu/skill-sync-system"' >> ~/.bashrc
source ~/.bashrc
Step 2: Create skill-install script
mkdir -p /home/ubuntu/skill-sync-system && cd /home/ubuntu/skill-sync-system
cat > skill-install << 'SCRIPT_END'
[Get complete script content from references/skill-install-template.sh]
SCRIPT_END
chmod +x skill-install
Step 3: Handle existing installation
# If /home/ubuntu/skills exists:
rm -rf /home/ubuntu/skills
Step 4: Install
skill-install
Expected output:
🚀 Installing Manus Skill Arsenal...
📥 Cloning repository from GitHub...
✅ Cloned repository
✅ Installed X skills across Y categories
✅ Registry loaded: X skills
🎯 Skills ready to use!
Time: 8 seconds per terminal
Layer 5: Meta-Skills (Orchestration)
↓
Layer 4: Discovery & Dependency System
↓
Layer 3: Individual Skills
↓
Layer 2: Shared Utilities
↓
Layer 1: Foundation (Standards & Patterns)
arsenal/
├── lib/ # Shared utilities
│ ├── skill_utils.py
│ ├── skill_registry.py
│ ├── skill_composer.py
│ └── skill_validator.py
├── meta-skills/ # Orchestrators
│ └── full-stack-builder/
├── skills/ # All skills
│ ├── tier1-foundation/
│ ├── tier2-automation/
│ ├── workflow-skills/
│ ├── design-skills/
│ └── [other categories]/
├── tools/ # Maintenance scripts
├── docs/ # Documentation
├── skills.json # Registry
├── README.md
└── ARCHITECTURE.md
from lib.skill_registry import SkillRegistry
registry = SkillRegistry('skills.json')
# Find by tag
db_skills = registry.find_by_tag("database")
# Get workflow suggestion
workflow = registry.suggest_workflow("build a SaaS app")
# Find complementary skills
complements = registry.get_complements("api-endpoint-builder")
The system automatically orders skills based on dependencies:
database-schema-generator → api-endpoint-builder → testing-framework
# Terminal 1: Learn new skill
cd /home/ubuntu/skills
git add skills/new-skill/
git commit -m "feat: add new-skill"
git push origin main
# Terminal 2: Get new skill
skill-sync
# New skill immediately available
Every installation tracks:
See the references/ directory for:
Always audit existing skills before building. Understand what you have.
Don't duplicate code. Put common functionality in lib/.
Every skill needs comprehensive SKILL.md with examples.
Use the 4-phase verification methodology:
Commit after each phase. Use semantic versioning for releases.
Always do fresh install (not merge) when setting up new terminals.
When deploying to new terminals, provide complete script content (not file references).
Cause: PATH not set
Fix:
export PATH="$PATH:/home/ubuntu/skill-sync-system"
Cause: Old installation exists
Fix:
rm -rf /home/ubuntu/skills && skill-install
Cause: Python imports not working
Fix: Non-critical, skills still work. Verify manually:
python3 -c "import sys; sys.path.insert(0, '/home/ubuntu/skills'); from lib.skill_registry import SkillRegistry"
| Phase | Time | Deliverables | |-------|------|--------------| | Phase 1 | 2-3 days | Audit report, organized structure | | Phase 2 | 2 days | 4 utility modules, tests | | Phase 3 | 2-3 days | skills.json, discovery API | | Phase 4 | Variable | New skills integrated | | Phase 5 | 3 days | Meta-skills, documentation | | Total | 2-3 weeks | Complete arsenal |
Cross-terminal deployment: 8 seconds per terminal
Starting point: 55 scattered skills
Goal: Unified, discoverable, cross-terminal arsenal
Process:
Result:
Time: 2 weeks (with Phase 4)
Built by: Manus AI Agent
Date: February 12, 2026
Status: Production Ready
Quality: ⭐⭐⭐⭐⭐ (5/5)
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code