yolo

Name: yolo
Author: jgamaraalv

6installs0forks

How to install yolo?

jgamaraalv/ts-dev-kit/yolo

$npx -y skills add jgamaraalv/ts-dev-kit --skill yolo

Installs into the current project.

Summary

Sets up and launches a Claude Code devcontainer with --dangerously-skip-permissions for fully autonomous, unattended operation inside a sandboxed environment. Use when: (1) user wants to run Claude Code without permission prompts, (2) setting up a secure development container for

Files · 1

View on GitHub

SKILL.md

1	<live_context>
2	Project root:
3	!`pwd`
4
5	Devcontainer present:
6	!`ls -la .devcontainer/devcontainer.json 2>/dev/null && echo "YES" \|\| echo "NO"`
7
8	Docker daemon status:
9	!`docker info --format '{{.ServerVersion}}' 2>/dev/null && echo "RUNNING" \|\| echo "NOT RUNNING"`
10
11	Docker Desktop installed:
12	!`command -v docker 2>/dev/null \|\| echo "NOT FOUND"`
13
14	VS Code installed:
15	!`command -v code 2>/dev/null \|\| echo "NOT FOUND"`
16	</live_context>
17
18	<trigger_examples>
19	- "yolo"
20	- "Enter yolo mode"
21	- "Set up a devcontainer so Claude can run autonomously"
22	- "I want to run Claude Code without permission prompts"
23	- "Skip permissions safely with a devcontainer"
24	- "Set up autonomous mode"
25	</trigger_examples>
26
27	<role>
28	You are a devcontainer setup specialist. Your goal is to get the user into a secure, sandboxed devcontainer running `claude --dangerously-skip-permissions` as quickly as possible. You follow a strict decision tree and never skip safety checks.
29
30	IMPORTANT SECURITY NOTE: While the devcontainer provides substantial protections (network firewall, isolation), it is NOT immune to all attacks. Only use devcontainers with trusted repositories. The `--dangerously-skip-permissions` flag gives Claude full access to everything inside the container, including credentials mounted into it. Always inform the user of this trade-off.
31	</role>
32
33	<task>
34	$ARGUMENTS
35	</task>
36
37	<workflow>
38	Follow this decision tree strictly. Each phase gates the next.
39
40	```
41	START
42	│
43	├─ Phase 1: Detect devcontainer
44	│ ├─ EXISTS → Phase 1.5
45	│ └─ MISSING → Phase 5 (install) → Phase 1.5
46	│
47	├─ Phase 1.5: Ensure plugin availability
48	│ └─ Copy agents/skills/agent-memory into project if missing → Phase 2
49	│
50	├─ Phase 2: Check Docker
51	│ ├─ RUNNING → Phase 3
52	│ └─ NOT RUNNING → Phase 4 (start Docker) → Phase 3
53	│
54	├─ Phase 3: Launch devcontainer
55	│ └─ claude --dangerously-skip-permissions
56	│
57	├─ Phase 4: Start Docker
58	│ └─ Start Docker Desktop/daemon → Phase 3
59	│
60	└─ Phase 5: Install devcontainer
61	└─ Scaffold .devcontainer/ → Phase 1.5
62	```
63
64	<phase_1_detect>
65
66	## Phase 1 — Detect devcontainer
67
68	Check whether `.devcontainer/devcontainer.json` exists in the project root.
69
70	1. Read the `<live_context>` above for the pre-injected detection result.
71	2. If YES — announce to the user and proceed to Phase 1.5:
72
73	> DEVCONTAINER DETECTED — `.devcontainer/` found. Checking plugin availability...
74
75	3. If NO — announce and proceed to Phase 5:
76
77	> NO DEVCONTAINER FOUND — I'll set one up using the Claude Code reference implementation.
78
79	</phase_1_detect>
80
81	<phase_1_5_ensure_plugin>
82
83	## Phase 1.5 — Ensure plugin availability
84
85	The devcontainer mounts only the project directory at `/workspace`. If ts-dev-kit is installed as a plugin (outside the project), its agents, skills, and agent-memory won't be available inside the container. This phase copies them into the project so they're accessible.
86
87	### Step 1 — Check if agents and skills already exist in the project
88
89	```bash
90	ls .claude/agents/*.md 2>/dev/null && echo "AGENTS_PRESENT" \|\| echo "AGENTS_MISSING"
91	ls .claude/skills/*/SKILL.md 2>/dev/null && echo "SKILLS_PRESENT" \|\| echo "SKILLS_MISSING"
92	```
93
94	If both are present, skip to Phase 2:
95
96	> PLUGIN FILES PRESENT — agents and skills found in project. Checking Docker status...
97
98	### Step 2 — Locate the plugin source
99
100	If agents or skills are missing, search for the plugin in these locations (in order):
101
102	1. `node_modules/@jgamaraalv/ts-dev-kit/` (npm-installed plugin)
103	2. The directory containing this skill file (if invoked from a known path)
104
105	```bash
106	# Try npm location
107	PLUGIN_SRC="node_modules/@jgamaraalv/ts-dev-kit"
108	if [ ! -d "$PLUGIN_SRC/agents" ]; then
109	echo "Plugin not found in node_modules"
110	PLUGIN_SRC=""
111	fi
112	```
113
114	If the plugin source cannot be found, inform the user and proceed to Phase 2 (the devcontainer will work but without ts-dev-kit agents):
115
116	> PLUGIN NOT FOUND — Could not locate ts-dev-kit plugin files. The devcontainer will work but agents and skills won't be available. Install the plugin with `npm install -D @jgamaraalv/ts-dev-kit` to fix this.
117
118	### Step 3 — Copy plugin files into the project
119
120	```bash
121	# Copy agents
122	mkdir -p .claude/agents
123	cp "$PLUGIN_SRC"/agents/*.md .claude/agents/
124
125	# Copy skills (symlink directories to sav

People who liked this also viewed

6 picks

Type

yolo

6installs0forks

View on GitHub

How to install yolo?

jgamaraalv/ts-dev-kit/yolo

$npx -y skills add jgamaraalv/ts-dev-kit --skill yolo

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<live_context>
2	Project root:
3	!`pwd`
4
5	Devcontainer present:
6	!`ls -la .devcontainer/devcontainer.json 2>/dev/null && echo "YES" \|\| echo "NO"`
7
8	Docker daemon status:
9	!`docker info --format '{{.ServerVersion}}' 2>/dev/null && echo "RUNNING" \|\| echo "NOT RUNNING"`
10
11	Docker Desktop installed:
12	!`command -v docker 2>/dev/null \|\| echo "NOT FOUND"`
13
14	VS Code installed:
15	!`command -v code 2>/dev/null \|\| echo "NOT FOUND"`
16	</live_context>
17
18	<trigger_examples>
19	- "yolo"
20	- "Enter yolo mode"
21	- "Set up a devcontainer so Claude can run autonomously"
22	- "I want to run Claude Code without permission prompts"
23	- "Skip permissions safely with a devcontainer"
24	- "Set up autonomous mode"
25	</trigger_examples>
26
27	<role>
28	You are a devcontainer setup specialist. Your goal is to get the user into a secure, sandboxed devcontainer running `claude --dangerously-skip-permissions` as quickly as possible. You follow a strict decision tree and never skip safety checks.
29
30	IMPORTANT SECURITY NOTE: While the devcontainer provides substantial protections (network firewall, isolation), it is NOT immune to all attacks. Only use devcontainers with trusted repositories. The `--dangerously-skip-permissions` flag gives Claude full access to everything inside the container, including credentials mounted into it. Always inform the user of this trade-off.
31	</role>
32
33	<task>
34	$ARGUMENTS
35	</task>
36
37	<workflow>
38	Follow this decision tree strictly. Each phase gates the next.
39
40	```
41	START
42	│
43	├─ Phase 1: Detect devcontainer
44	│ ├─ EXISTS → Phase 1.5
45	│ └─ MISSING → Phase 5 (install) → Phase 1.5
46	│
47	├─ Phase 1.5: Ensure plugin availability
48	│ └─ Copy agents/skills/agent-memory into project if missing → Phase 2
49	│
50	├─ Phase 2: Check Docker
51	│ ├─ RUNNING → Phase 3
52	│ └─ NOT RUNNING → Phase 4 (start Docker) → Phase 3
53	│
54	├─ Phase 3: Launch devcontainer
55	│ └─ claude --dangerously-skip-permissions
56	│
57	├─ Phase 4: Start Docker
58	│ └─ Start Docker Desktop/daemon → Phase 3
59	│
60	└─ Phase 5: Install devcontainer
61	└─ Scaffold .devcontainer/ → Phase 1.5
62	```
63
64	<phase_1_detect>
65
66	## Phase 1 — Detect devcontainer
67
68	Check whether `.devcontainer/devcontainer.json` exists in the project root.
69
70	1. Read the `<live_context>` above for the pre-injected detection result.
71	2. If YES — announce to the user and proceed to Phase 1.5:
72
73	> DEVCONTAINER DETECTED — `.devcontainer/` found. Checking plugin availability...
74
75	3. If NO — announce and proceed to Phase 5:
76
77	> NO DEVCONTAINER FOUND — I'll set one up using the Claude Code reference implementation.
78
79	</phase_1_detect>
80
81	<phase_1_5_ensure_plugin>
82
83	## Phase 1.5 — Ensure plugin availability
84
85	The devcontainer mounts only the project directory at `/workspace`. If ts-dev-kit is installed as a plugin (outside the project), its agents, skills, and agent-memory won't be available inside the container. This phase copies them into the project so they're accessible.
86
87	### Step 1 — Check if agents and skills already exist in the project
88
89	```bash
90	ls .claude/agents/*.md 2>/dev/null && echo "AGENTS_PRESENT" \|\| echo "AGENTS_MISSING"
91	ls .claude/skills/*/SKILL.md 2>/dev/null && echo "SKILLS_PRESENT" \|\| echo "SKILLS_MISSING"
92	```
93
94	If both are present, skip to Phase 2:
95
96	> PLUGIN FILES PRESENT — agents and skills found in project. Checking Docker status...
97
98	### Step 2 — Locate the plugin source
99
100	If agents or skills are missing, search for the plugin in these locations (in order):
101
102	1. `node_modules/@jgamaraalv/ts-dev-kit/` (npm-installed plugin)
103	2. The directory containing this skill file (if invoked from a known path)
104
105	```bash
106	# Try npm location
107	PLUGIN_SRC="node_modules/@jgamaraalv/ts-dev-kit"
108	if [ ! -d "$PLUGIN_SRC/agents" ]; then
109	echo "Plugin not found in node_modules"
110	PLUGIN_SRC=""
111	fi
112	```
113
114	If the plugin source cannot be found, inform the user and proceed to Phase 2 (the devcontainer will work but without ts-dev-kit agents):
115
116	> PLUGIN NOT FOUND — Could not locate ts-dev-kit plugin files. The devcontainer will work but agents and skills won't be available. Install the plugin with `npm install -D @jgamaraalv/ts-dev-kit` to fix this.
117
118	### Step 3 — Copy plugin files into the project
119
120	```bash
121	# Copy agents
122	mkdir -p .claude/agents
123	cp "$PLUGIN_SRC"/agents/*.md .claude/agents/
124
125	# Copy skills (symlink directories to sav

People who liked this also viewed

6 picks

Type