claude-code-pack 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md ADDED
@@ -0,0 +1,120 @@
1
+ # claude-pack
2
+
3
+ Portable Claude Code setup — installs your plugins, skills, MCP servers, and settings on any machine with a single command.
4
+
5
+ ## Quick Start
6
+
7
+ ```bash
8
+ npx claude-pack install
9
+ ```
10
+
11
+ Or install globally:
12
+
13
+ ```bash
14
+ npm install -g claude-pack
15
+ claude-pack install
16
+ ```
17
+
18
+ ## What It Does
19
+
20
+ `claude-pack` reads `claude-pack.config.json` and sets up your Claude Code environment:
21
+
22
+ | Component | How it installs |
23
+ |-----------|----------------|
24
+ | **Plugins** | Clones from GitHub, registers in `~/.claude/plugins/` |
25
+ | **Skills** | Copies bundled skills or clones from GitHub to `~/.claude/skills/` |
26
+ | **MCP Servers** | Merges config into `~/.claude/settings.json` |
27
+ | **Settings** | Merges model, statusline, and other preferences |
28
+
29
+ Everything is fetched fresh from GitHub, so you always get the latest version.
30
+
31
+ ## Configuration
32
+
33
+ Edit `claude-pack.config.json` to customize your setup:
34
+
35
+ ```json
36
+ {
37
+ "plugins": [
38
+ {
39
+ "name": "claude-mem",
40
+ "marketplace": "thedotmack",
41
+ "repo": "thedotmack/claude-mem",
42
+ "enabled": true
43
+ }
44
+ ],
45
+ "marketplaces": [
46
+ { "name": "thedotmack", "repo": "thedotmack/claude-mem" }
47
+ ],
48
+ "skills": [
49
+ { "name": "my-skill", "source": "bundled" },
50
+ { "name": "remote-skill", "source": "github", "repo": "user/repo" }
51
+ ],
52
+ "mcpServers": {
53
+ "my-server": {
54
+ "command": "npx",
55
+ "args": ["-y", "@some/mcp-server"]
56
+ }
57
+ },
58
+ "settings": {
59
+ "model": "opus"
60
+ }
61
+ }
62
+ ```
63
+
64
+ ### Skill Sources
65
+
66
+ - `"source": "bundled"` — copies from the `skills/` directory in this package
67
+ - `"source": "github", "repo": "user/repo"` — clones from GitHub
68
+
69
+ ## Commands
70
+
71
+ ```bash
72
+ claude-pack install # Install everything
73
+ claude-pack status # Dry run — show what would be installed
74
+ claude-pack help # Show help
75
+
76
+ # Flags
77
+ claude-pack install --force # Overwrite existing installations
78
+ claude-pack install --skip-plugins # Skip plugin installation
79
+ claude-pack install --skip-skills # Skip skill installation
80
+ claude-pack install --skip-settings # Skip settings merge
81
+ claude-pack install --dry-run # Preview without changes
82
+ ```
83
+
84
+ ## Adding New Components
85
+
86
+ ### Add a plugin
87
+
88
+ 1. Add to `claude-pack.config.json` under `plugins` and `marketplaces`
89
+ 2. Run `claude-pack install`
90
+
91
+ ### Add a skill from GitHub
92
+
93
+ ```json
94
+ {
95
+ "name": "my-skill",
96
+ "source": "github",
97
+ "repo": "username/my-skill-repo"
98
+ }
99
+ ```
100
+
101
+ ### Add a bundled skill
102
+
103
+ 1. Create `skills/my-skill/SKILL.md`
104
+ 2. Add to config: `{ "name": "my-skill", "source": "bundled" }`
105
+
106
+ ### Add an MCP server
107
+
108
+ ```json
109
+ "mcpServers": {
110
+ "server-name": {
111
+ "command": "npx",
112
+ "args": ["-y", "@scope/mcp-server"]
113
+ }
114
+ }
115
+ ```
116
+
117
+ ## Requirements
118
+
119
+ - Node.js >= 18
120
+ - git
@@ -0,0 +1,116 @@
1
+ #!/usr/bin/env bash
2
+ # Claude Code status line script
3
+ # Colors: dark background, bold green for labels, bold blue for model/dirs
4
+
5
+ input=$(cat)
6
+
7
+ # ANSI color codes
8
+ BOLD='\033[1m'
9
+ GREEN='\033[01;32m'
10
+ BLUE='\033[01;34m'
11
+ CYAN='\033[01;36m'
12
+ YELLOW='\033[01;33m'
13
+ MAGENTA='\033[01;35m'
14
+ RED='\033[01;31m'
15
+ RESET='\033[00m'
16
+
17
+ # Build a fixed-width progress bar (10 chars, ▓ for filled, ░ for empty)
18
+ build_bar() {
19
+ local pct="$1"
20
+ local width=10
21
+ local FILLED
22
+ FILLED=$(echo "$pct $width" | awk '{printf "%d", int($1 / 100 * $2 + 0.5)}')
23
+ local EMPTY=$(( width - FILLED ))
24
+ local BAR=""
25
+ [ "$FILLED" -gt 0 ] && printf -v FILL "%${FILLED}s" && BAR="${FILL// /▓}"
26
+ [ "$EMPTY" -gt 0 ] && printf -v PAD "%${EMPTY}s" && BAR="${BAR}${PAD// /░}"
27
+ echo "$BAR"
28
+ }
29
+
30
+ # Format seconds-until-reset as "Xh Ym" or "Zm"
31
+ format_reset() {
32
+ local epoch="$1"
33
+ [ -z "$epoch" ] && return
34
+ local now
35
+ now=$(date +%s)
36
+ local diff=$(( epoch - now ))
37
+ [ "$diff" -le 0 ] && echo "now" && return
38
+ local d=$(( diff / 86400 ))
39
+ local h=$(( (diff % 86400) / 3600 ))
40
+ local m=$(( (diff % 3600) / 60 ))
41
+ if [ "$d" -gt 0 ]; then
42
+ echo "${d}d${h}h"
43
+ elif [ "$h" -gt 0 ]; then
44
+ echo "${h}h${m}m"
45
+ else
46
+ echo "${m}m"
47
+ fi
48
+ }
49
+
50
+ # Return a color string based on percentage (green < 50, yellow < 80, red >= 80)
51
+ pct_color() {
52
+ local pct="$1"
53
+ local val
54
+ val=$(printf '%.0f' "$pct" 2>/dev/null) || val=0
55
+ if [ "$val" -ge 80 ]; then
56
+ printf '%b' "$RED"
57
+ elif [ "$val" -ge 50 ]; then
58
+ printf '%b' "$YELLOW"
59
+ else
60
+ printf '%b' "$GREEN"
61
+ fi
62
+ }
63
+
64
+ # --- Extract fields using python3 (jq not available) ---
65
+ eval "$(echo "$input" | python3 -c "
66
+ import sys, json
67
+ d = json.load(sys.stdin)
68
+ m = d.get('model', {})
69
+ print('model=' + repr(m.get('display_name') or m.get('id') or 'unknown'))
70
+ cw = d.get('context_window', {})
71
+ print('used_pct=' + repr(str(cw['used_percentage']) if 'used_percentage' in cw else ''))
72
+ rl = d.get('rate_limits', {})
73
+ fh = rl.get('five_hour', {})
74
+ print('five_pct=' + repr(str(fh['used_percentage']) if 'used_percentage' in fh else ''))
75
+ print('five_reset=' + repr(str(fh['resets_at']) if 'resets_at' in fh else ''))
76
+ sd = rl.get('seven_day', {})
77
+ print('week_pct=' + repr(str(sd['used_percentage']) if 'used_percentage' in sd else ''))
78
+ print('week_reset=' + repr(str(sd['resets_at']) if 'resets_at' in sd else ''))
79
+ " 2>/dev/null)" || {
80
+ model="unknown"; used_pct=""; five_pct=""; five_reset=""; week_pct=""; week_reset=""
81
+ }
82
+
83
+ # --- Build output ---
84
+ out=""
85
+
86
+ # Model name (bold blue, matching directory color in PS1)
87
+ out="${out}$(printf '%b' "${BOLD}${BLUE}")${model}$(printf '%b' "${RESET}")"
88
+
89
+ # Context window segment (always shown; defaults to 0% when data not yet available)
90
+ used_pct_eff="${used_pct:-0}"
91
+ bar=$(build_bar "$used_pct_eff")
92
+ pct_num=$(printf '%.0f' "$used_pct_eff")
93
+ color=$(pct_color "$used_pct_eff")
94
+ out="${out} $(printf '%b' "${BOLD}${CYAN}")ctx$(printf '%b' "${RESET}")[$(printf '%b' "${color}")${bar}$(printf '%b' "${RESET}")|$(printf '%b' "${color}")${pct_num}%$(printf '%b' "${RESET}")]"
95
+
96
+ # 5-hour rate limit segment (always shown; defaults to 0% when data not yet available)
97
+ five_pct_eff="${five_pct:-0}"
98
+ bar=$(build_bar "$five_pct_eff")
99
+ pct_num=$(printf '%.0f' "$five_pct_eff")
100
+ color=$(pct_color "$five_pct_eff")
101
+ reset_str=$(format_reset "$five_reset")
102
+ label="5h"
103
+ [ -n "$reset_str" ] && label="${label}(${reset_str})"
104
+ out="${out} $(printf '%b' "${BOLD}${MAGENTA}")${label}$(printf '%b' "${RESET}")[$(printf '%b' "${color}")${bar}$(printf '%b' "${RESET}")|$(printf '%b' "${color}")${pct_num}%$(printf '%b' "${RESET}")]"
105
+
106
+ # 7-day rate limit segment (always shown; defaults to 0% when data not yet available)
107
+ week_pct_eff="${week_pct:-0}"
108
+ bar=$(build_bar "$week_pct_eff")
109
+ pct_num=$(printf '%.0f' "$week_pct_eff")
110
+ color=$(pct_color "$week_pct_eff")
111
+ reset_str=$(format_reset "$week_reset")
112
+ label="7d"
113
+ [ -n "$reset_str" ] && label="${label}(${reset_str})"
114
+ out="${out} $(printf '%b' "${BOLD}${MAGENTA}")${label}$(printf '%b' "${RESET}")[$(printf '%b' "${color}")${bar}$(printf '%b' "${RESET}")|$(printf '%b' "${color}")${pct_num}%$(printf '%b' "${RESET}")]"
115
+
116
+ printf '%b\n' "$out"
@@ -0,0 +1,48 @@
1
+ #!/usr/bin/env node
2
+
3
+ import { install } from '../src/install.mjs';
4
+
5
+ const args = process.argv.slice(2);
6
+ const command = args[0] || 'install';
7
+
8
+ const flags = {
9
+ dryRun: args.includes('--dry-run'),
10
+ force: args.includes('--force'),
11
+ skipPlugins: args.includes('--skip-plugins'),
12
+ skipSkills: args.includes('--skip-skills'),
13
+ skipSettings: args.includes('--skip-settings'),
14
+ };
15
+
16
+ switch (command) {
17
+ case 'install':
18
+ await install(flags);
19
+ break;
20
+ case 'status':
21
+ await install({ ...flags, dryRun: true });
22
+ break;
23
+ case 'help':
24
+ printHelp();
25
+ break;
26
+ default:
27
+ console.error(`Unknown command: ${command}`);
28
+ printHelp();
29
+ process.exit(1);
30
+ }
31
+
32
+ function printHelp() {
33
+ console.log(`
34
+ claude-pack — Portable Claude Code setup
35
+
36
+ Usage:
37
+ claude-pack install Install all plugins, skills, MCP servers, and settings
38
+ claude-pack status Show what would be installed (dry run)
39
+ claude-pack help Show this help
40
+
41
+ Flags:
42
+ --dry-run Show what would happen without making changes
43
+ --force Overwrite existing installations
44
+ --skip-plugins Skip plugin installation
45
+ --skip-skills Skip skill installation
46
+ --skip-settings Skip settings merge
47
+ `);
48
+ }
@@ -0,0 +1,37 @@
1
+ {
2
+ "plugins": [
3
+ {
4
+ "name": "claude-mem",
5
+ "marketplace": "thedotmack",
6
+ "repo": "thedotmack/claude-mem",
7
+ "enabled": true
8
+ }
9
+ ],
10
+ "marketplaces": [
11
+ {
12
+ "name": "thedotmack",
13
+ "repo": "thedotmack/claude-mem"
14
+ },
15
+ {
16
+ "name": "understand-anything",
17
+ "repo": "Lum1104/Understand-Anything"
18
+ }
19
+ ],
20
+ "skills": [
21
+ { "name": "cloud-devops", "source": "bundled" },
22
+ { "name": "fastapi", "source": "bundled" },
23
+ { "name": "senior-ml-engineer", "source": "bundled" },
24
+ { "name": "technical-writer", "source": "bundled" }
25
+ ],
26
+ "mcpServers": {},
27
+ "settings": {
28
+ "model": "opus",
29
+ "statusLine": {
30
+ "type": "command",
31
+ "command": "bash $HOME/.claude/statusline-command.sh"
32
+ }
33
+ },
34
+ "assets": {
35
+ "statusline": "assets/statusline-command.sh"
36
+ }
37
+ }
package/package.json ADDED
@@ -0,0 +1,31 @@
1
+ {
2
+ "name": "claude-code-pack",
3
+ "version": "1.0.0",
4
+ "description": "Portable Claude Code setup — installs plugins, skills, MCP servers, and statusline on any machine",
5
+ "type": "module",
6
+ "bin": {
7
+ "claude-pack": "bin/claude-pack.mjs"
8
+ },
9
+ "files": [
10
+ "bin/",
11
+ "src/",
12
+ "skills/",
13
+ "assets/",
14
+ "claude-pack.config.json"
15
+ ],
16
+ "keywords": [
17
+ "claude",
18
+ "claude-code",
19
+ "plugins",
20
+ "mcp",
21
+ "developer-tools"
22
+ ],
23
+ "license": "MIT",
24
+ "repository": {
25
+ "type": "git",
26
+ "url": "git+https://github.com/tanle/claude-pack.git"
27
+ },
28
+ "engines": {
29
+ "node": ">=18"
30
+ }
31
+ }
@@ -0,0 +1,235 @@
1
+ ---
2
+ name: cloud-devops
3
+ description: "Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development."
4
+ category: workflow-bundle
5
+ risk: safe
6
+ source: personal
7
+ date_added: "2026-02-27"
8
+ ---
9
+
10
+ # Cloud/DevOps Workflow Bundle
11
+
12
+ ## Overview
13
+
14
+ Comprehensive cloud and DevOps workflow for infrastructure provisioning, container orchestration, CI/CD pipelines, monitoring, and cloud-native application development.
15
+
16
+ ## When to Use This Workflow
17
+
18
+ Use this workflow when:
19
+ - Setting up cloud infrastructure
20
+ - Implementing CI/CD pipelines
21
+ - Deploying Kubernetes applications
22
+ - Configuring monitoring and observability
23
+ - Managing cloud costs
24
+ - Implementing DevOps practices
25
+
26
+ ## Workflow Phases
27
+
28
+ ### Phase 1: Cloud Infrastructure Setup
29
+
30
+ #### Skills to Invoke
31
+ - `cloud-architect` - Cloud architecture
32
+ - `aws-skills` - AWS development
33
+ - `azure-functions` - Azure development
34
+ - `gcp-cloud-run` - GCP development
35
+ - `terraform-skill` - Terraform IaC
36
+ - `terraform-specialist` - Advanced Terraform
37
+
38
+ #### Actions
39
+ 1. Design cloud architecture
40
+ 2. Set up accounts and billing
41
+ 3. Configure networking
42
+ 4. Provision resources
43
+ 5. Set up IAM
44
+
45
+ #### Copy-Paste Prompts
46
+ ```
47
+ Use @cloud-architect to design multi-cloud architecture
48
+ ```
49
+
50
+ ```
51
+ Use @terraform-skill to provision AWS infrastructure
52
+ ```
53
+
54
+ ### Phase 2: Container Orchestration
55
+
56
+ #### Skills to Invoke
57
+ - `kubernetes-architect` - Kubernetes architecture
58
+ - `docker-expert` - Docker containerization
59
+ - `helm-chart-scaffolding` - Helm charts
60
+ - `k8s-manifest-generator` - K8s manifests
61
+ - `k8s-security-policies` - K8s security
62
+
63
+ #### Actions
64
+ 1. Design container architecture
65
+ 2. Create Dockerfiles
66
+ 3. Build container images
67
+ 4. Write K8s manifests
68
+ 5. Deploy to cluster
69
+ 6. Configure networking
70
+
71
+ #### Copy-Paste Prompts
72
+ ```
73
+ Use @kubernetes-architect to design K8s architecture
74
+ ```
75
+
76
+ ```
77
+ Use @docker-expert to containerize application
78
+ ```
79
+
80
+ ```
81
+ Use @helm-chart-scaffolding to create Helm chart
82
+ ```
83
+
84
+ ### Phase 3: CI/CD Implementation
85
+
86
+ #### Skills to Invoke
87
+ - `deployment-engineer` - Deployment engineering
88
+ - `cicd-automation-workflow-automate` - CI/CD automation
89
+ - `github-actions-templates` - GitHub Actions
90
+ - `gitlab-ci-patterns` - GitLab CI
91
+ - `deployment-pipeline-design` - Pipeline design
92
+
93
+ #### Actions
94
+ 1. Design deployment pipeline
95
+ 2. Configure build automation
96
+ 3. Set up test automation
97
+ 4. Configure deployment stages
98
+ 5. Implement rollback strategies
99
+ 6. Set up notifications
100
+
101
+ #### Copy-Paste Prompts
102
+ ```
103
+ Use @cicd-automation-workflow-automate to set up CI/CD pipeline
104
+ ```
105
+
106
+ ```
107
+ Use @github-actions-templates to create GitHub Actions workflow
108
+ ```
109
+
110
+ ### Phase 4: Monitoring and Observability
111
+
112
+ #### Skills to Invoke
113
+ - `observability-engineer` - Observability engineering
114
+ - `grafana-dashboards` - Grafana dashboards
115
+ - `prometheus-configuration` - Prometheus setup
116
+ - `datadog-automation` - Datadog integration
117
+ - `sentry-automation` - Sentry error tracking
118
+
119
+ #### Actions
120
+ 1. Design monitoring strategy
121
+ 2. Set up metrics collection
122
+ 3. Configure log aggregation
123
+ 4. Implement distributed tracing
124
+ 5. Create dashboards
125
+ 6. Set up alerts
126
+
127
+ #### Copy-Paste Prompts
128
+ ```
129
+ Use @observability-engineer to set up observability stack
130
+ ```
131
+
132
+ ```
133
+ Use @grafana-dashboards to create monitoring dashboards
134
+ ```
135
+
136
+ ### Phase 5: Cloud Security
137
+
138
+ #### Skills to Invoke
139
+ - `cloud-penetration-testing` - Cloud pentesting
140
+ - `aws-penetration-testing` - AWS security
141
+ - `k8s-security-policies` - K8s security
142
+ - `secrets-management` - Secrets management
143
+ - `mtls-configuration` - mTLS setup
144
+
145
+ #### Actions
146
+ 1. Assess cloud security
147
+ 2. Configure security groups
148
+ 3. Set up secrets management
149
+ 4. Implement network policies
150
+ 5. Configure encryption
151
+ 6. Set up audit logging
152
+
153
+ #### Copy-Paste Prompts
154
+ ```
155
+ Use @cloud-penetration-testing to assess cloud security
156
+ ```
157
+
158
+ ```
159
+ Use @secrets-management to configure secrets
160
+ ```
161
+
162
+ ### Phase 6: Cost Optimization
163
+
164
+ #### Skills to Invoke
165
+ - `cost-optimization` - Cloud cost optimization
166
+ - `database-cloud-optimization-cost-optimize` - Database cost optimization
167
+
168
+ #### Actions
169
+ 1. Analyze cloud spending
170
+ 2. Identify optimization opportunities
171
+ 3. Right-size resources
172
+ 4. Implement auto-scaling
173
+ 5. Use reserved instances
174
+ 6. Set up cost alerts
175
+
176
+ #### Copy-Paste Prompts
177
+ ```
178
+ Use @cost-optimization to reduce cloud costs
179
+ ```
180
+
181
+ ### Phase 7: Disaster Recovery
182
+
183
+ #### Skills to Invoke
184
+ - `incident-responder` - Incident response
185
+ - `incident-runbook-templates` - Runbook creation
186
+ - `postmortem-writing` - Postmortem documentation
187
+
188
+ #### Actions
189
+ 1. Design DR strategy
190
+ 2. Set up backups
191
+ 3. Create runbooks
192
+ 4. Test failover
193
+ 5. Document procedures
194
+ 6. Train team
195
+
196
+ #### Copy-Paste Prompts
197
+ ```
198
+ Use @incident-runbook-templates to create runbooks
199
+ ```
200
+
201
+ ## Cloud Provider Workflows
202
+
203
+ ### AWS
204
+ ```
205
+ Skills: aws-skills, aws-serverless, aws-penetration-testing
206
+ Services: EC2, Lambda, S3, RDS, ECS, EKS
207
+ ```
208
+
209
+ ### Azure
210
+ ```
211
+ Skills: azure-functions, azure-ai-projects-py, azure-monitor-opentelemetry-py
212
+ Services: Functions, App Service, AKS, Cosmos DB
213
+ ```
214
+
215
+ ### GCP
216
+ ```
217
+ Skills: gcp-cloud-run
218
+ Services: Cloud Run, GKE, Cloud Functions, BigQuery
219
+ ```
220
+
221
+ ## Quality Gates
222
+
223
+ - [ ] Infrastructure provisioned
224
+ - [ ] CI/CD pipeline working
225
+ - [ ] Monitoring configured
226
+ - [ ] Security measures in place
227
+ - [ ] Cost optimization applied
228
+ - [ ] DR procedures documented
229
+
230
+ ## Related Workflow Bundles
231
+
232
+ - `development` - Application development
233
+ - `security-audit` - Security testing
234
+ - `database` - Database operations
235
+ - `testing-qa` - Testing workflows