casabot 1.1.13 → 1.2.0

package/README.md

@@ -57,7 +57,8 @@ User ↔ TUI (Terminal UI) ↔ Base Agent (terminal access)
 │   ├── config/SKILL.md   # CasAbot configuration
 │   ├── chat/SKILL.md     # Conversation management
 │   ├── service/SKILL.md  # System service registration
-│   └── memory/SKILL.md   # Memory management
+│   ├── memory/SKILL.md   # Memory management
+│   └── subskills/SKILL.md # Sub-agent skill attachment and management
 ├── workspaces/           # Per-agent workspaces
 ├── history/              # Full conversation logs (raw)
 └── memory/               # Agent-authored notes (.md)
@@ -83,6 +84,7 @@ User ↔ TUI (Terminal UI) ↔ Base Agent (terminal access)
 | `chat` | Conversation session management and search |
 | `service` | systemd service registration and automation |
 | `memory` | Write, query, and search agent notes |
+| `subskills` | Attach and manage skills available to sub-agents |
 
 ## Adding Skills
 

package/dist/agent/base.js

@@ -24,6 +24,8 @@ export function buildSystemPrompt(skills) {
 2. Refer to skill documents first. Read the relevant SKILL.md and follow the instructions.
 3. Delegate to an appropriate sub-agent if one exists; otherwise, create a new one and delegate.
 4. Only perform orchestration (agent creation/delegation/management) directly.
+5. Try to solve problems independently using all available information before asking the user. Only ask the user when you truly need information you cannot obtain on your own (e.g. API keys, sudo passwords, personal preferences).
+6. When you encounter information worth remembering (e.g. user preferences, API keys, system details), use the memory skill to persist it for future sessions.
 
 ## Available Tools
 - \`run_command\`: Executes a command in the terminal. Use this single tool to read skills, manage sub-agents, and perform all orchestration.

package/dist/cli/setup.js

@@ -101,7 +101,8 @@ ls ~/casabot/workspaces/<agent-name>/output/
 │   ├── config/
 │   ├── chat/
 │   ├── service/
-│   └── memory/
+│   ├── memory/
+│   └── subskills/
 ├── workspaces/           # Per-agent workspaces
 ├── history/              # Full conversation logs (raw logs)
 └── memory/               # Agent-written memos (.md)
@@ -270,6 +271,63 @@ grep -rl "keyword" ~/casabot/memory/
 
 # Read specific memory file
 cat ~/casabot/memory/<filename>.md
+\`\`\``,
+        },
+        subskills: {
+            name: "Sub-Agent Skills (subskills)",
+            description: "Manual for attaching and managing skills available to sub-agents",
+            content: `# Sub-Agent Skills (subskills)
+
+## What is /subskills?
+Each skill directory can contain a \`/subskills\` subdirectory holding skill documents intended for sub-agents.
+
+\`\`\`
+~/casabot/skills/
+├── agent/
+│   ├── SKILL.md
+│   └── subskills/
+│       ├── python-dev/SKILL.md
+│       └── web-scraper/SKILL.md
+└── subskills/
+    └── SKILL.md
+\`\`\`
+
+## Who can add subskills?
+- **Agents**: Search for tools/techniques and write subskill documents autonomously.
+- **Users**: Place skill documents directly into any \`/subskills\` directory.
+
+\`\`\`bash
+# Create a subskill
+mkdir -p ~/casabot/skills/agent/subskills/python-dev
+cat > ~/casabot/skills/agent/subskills/python-dev/SKILL.md << 'EOF'
+---
+name: Python Development
+description: Guidelines for Python-based sub-agents
+metadata:
+  casabot:
+    requires:
+      bins: [python3]
+---
+# Python Development
+Instructions for sub-agents...
+EOF
+\`\`\`
+
+## Passing subskills to sub-agents
+\`\`\`bash
+# Mount subskills into container
+podman run -d --name <agent-name> --label casabot=true \\
+  -v ~/casabot/skills/agent/subskills:/subskills:ro \\
+  -v ~/casabot/workspaces/<agent-name>:/workspace \\
+  node:20-slim sleep infinity
+\`\`\`
+
+## Listing and searching
+\`\`\`bash
+# List all subskills
+find ~/casabot/skills/*/subskills -name "SKILL.md" 2>/dev/null
+# Search by keyword
+grep -rl "keyword" ~/casabot/skills/*/subskills/ 2>/dev/null
 \`\`\``,
         },
     };

package/dist/config/manager.js

@@ -9,7 +9,7 @@ export const PATHS = {
     history: join(CASABOT_HOME, "history"),
     memory: join(CASABOT_HOME, "memory"),
 };
-const SKILL_DIRS = ["agent", "config", "chat", "service", "memory"];
+const SKILL_DIRS = ["agent", "config", "chat", "service", "memory", "subskills"];
 export function getDefaultConfig() {
     return {
         providers: [],

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "casabot",
-  "version": "1.1.13",
+  "version": "1.2.0",
   "description": "CasAbot — Skill-driven multi-agent orchestrator system",
   "type": "module",
   "main": "dist/index.js",

package/skills/agent/SKILL.md

@@ -15,7 +15,7 @@ This manual explains how the base agent creates and manages podman-based sub-age
 
 ## 1. Install podman
 
-podman must be installed before creating sub-agents.
+podman is needed before creating sub-agents.
 
 ### Step 1: Check if podman is already installed
 
@@ -25,27 +25,21 @@ which podman && podman --version
 
 If podman is found, skip to Section 2.
 
-### Step 2: Gather requirements from the user
+### Step 2: Gather system information
 
-> **Important:** Before installing podman, you **must** ask the user the following questions. Do not assume or proceed without their answers.
+Try to detect as much as possible automatically before involving the user.
 
-1. **Detect or ask the distro:**
-   ```bash
-   cat /etc/os-release
-   ```
-   If the distro cannot be determined, ask the user: *"Which Linux distribution are you using? (e.g. Ubuntu, Fedora, Arch, Debian, RHEL, etc.)"*
-
-2. **Ask about sudo privileges:**
-   *"Do you have sudo (root) privileges on this system?"*
-   — If the user does not have sudo, guide them to request it from an administrator, or suggest rootless podman setup if possible.
+```bash
+# Detect distro
+cat /etc/os-release
 
-3. **Ask about rootless mode:**
-   *"Would you like to run podman in rootless mode (recommended for security)?"*
+# Check if sudo is available
+sudo -n true 2>/dev/null && echo "sudo: available" || echo "sudo: not available"
+```
 
-4. **Ask about special requirements:**
-   *"Do you have any specific requirements? (e.g. a particular podman version, a custom storage location, proxy settings, etc.)"*
+If auto-detection fails or sudo is unavailable, ask the user for clarification. You may also ask about preferences like rootless mode or custom storage locations if relevant.
 
-### Step 3: Install podman based on user's answers
+### Step 3: Install podman
 
 ```bash
 # Debian / Ubuntu
@@ -61,7 +55,7 @@ sudo pacman -S podman
 sudo zypper install -y podman
 ```
 
-If the user requested rootless mode, also configure subuid/subgid:
+If rootless mode is desired, configure subuid/subgid:
 
 ```bash
 sudo usermod --add-subuids 100000-165535 --add-subgids 100000-165535 $(whoami)
@@ -75,6 +69,8 @@ podman --version
 podman info
 ```
 
+Consider using the memory skill to save the detected distro and podman version for future reference.
+
 ## 2. Configure podman storage
 
 Check the path where container images and layers are stored, and verify sufficient disk space.
@@ -87,11 +83,11 @@ podman info --format '{{.Store.GraphRoot}}'
 df -h $(podman info --format '{{.Store.GraphRoot}}')
 ```
 
-If space is insufficient, change `graphroot` in `~/.config/containers/storage.conf`.
+If space is insufficient, `graphroot` in `~/.config/containers/storage.conf` can be adjusted.
 
 ## 3. Create sub-agent container
 
-All sub-agent containers must be assigned the `casabot` label.
+All sub-agent containers should be assigned the `casabot` label for identification.
 
 ```bash
 # Create a new agent container
@@ -103,7 +99,7 @@ podman run -d \
   node:20-slim sleep infinity
 ```
 
-### Required rules
+### Recommended conventions
 - `--label casabot=true`: Used to identify all CasAbot sub-agents.
 - `-v ~/casabot/workspaces/<agent-name>:/workspace`: Mounts a dedicated workspace for each agent.
 - `-v ~/casabot/skills:/skills:ro`: Shares the skills directory as read-only.
@@ -117,7 +113,9 @@ podman exec <agent-name> node /workspace/agent.js
 
 ## 4. Pass provider settings
 
-> **Important:** Read the current provider settings from `~/casabot/casabot.json` or ask the user for the provider type, API key, and model name. Do not hardcode these values.
+Provider settings can be read from `~/casabot/casabot.json`. If the file is unavailable or incomplete, ask the user for the provider type, API key, and model name.
+
+When sensitive information like API keys is obtained, consider persisting it via the memory skill so it doesn't need to be requested again.
 
 Pass LLM provider information to sub-agents via environment variables.
 
@@ -131,7 +129,7 @@ podman exec \
   <agent-name> node /workspace/agent.js
 ```
 
-Or set them in advance with `-e` options when creating the container:
+Or set them when creating the container:
 
 ```bash
 podman run -d \
@@ -158,7 +156,69 @@ cat /skills/memory/SKILL.md
 ls /skills/
 ```
 
-## 6. List agents
+## 6. Pass subskills
+
+Each skill directory can contain a `subskills/` subdirectory with skills specifically intended for sub-agents. When delegating a task, consider checking for relevant subskills to pass along.
+
+> **Note:** The full skills mount (`-v ~/casabot/skills:/skills:ro` from Section 3) already includes all `subskills/` directories. The separate mount shown below is an alternative for providing targeted access to specific subskills.
+
+### Discover available subskills
+
+```bash
+# List all subskills across all skill directories
+find ~/casabot/skills/*/subskills -name "SKILL.md" 2>/dev/null
+
+# List subskills for a specific skill
+ls ~/casabot/skills/agent/subskills/ 2>/dev/null
+
+# Search subskills by keyword
+grep -rl "keyword" ~/casabot/skills/*/subskills/ 2>/dev/null
+```
+
+### Mount subskills into a sub-agent container
+
+```bash
+# Mount a specific skill's subskills
+podman run -d \
+  --name <agent-name> \
+  --label casabot=true \
+  -v ~/casabot/skills/agent/subskills:/subskills:ro \
+  -v ~/casabot/workspaces/<agent-name>:/workspace \
+  node:20-slim sleep infinity
+```
+
+Or copy specific subskill documents:
+
+```bash
+podman cp ~/casabot/skills/agent/subskills/python-dev/SKILL.md \
+  <agent-name>:/workspace/skills/python-dev/SKILL.md
+```
+
+### Create new subskills
+
+If a task requires capabilities not yet covered by existing subskills, the agent can search the web for relevant tools, libraries, or techniques and write a new subskill document.
+
+```bash
+mkdir -p ~/casabot/skills/<skill>/subskills/<new-subskill>
+cat > ~/casabot/skills/<skill>/subskills/<new-subskill>/SKILL.md << 'EOF'
+---
+name: New Subskill
+description: What this subskill provides
+metadata:
+  casabot:
+    requires:
+      bins: []
+---
+
+# New Subskill
+
+(Instructions for sub-agents)
+EOF
+```
+
+Users can also add subskill documents manually at any time. Refer to the `subskills` skill for detailed guidance.
+
+## 7. List agents
 
 Query all containers with the `casabot` label.
 
@@ -170,7 +230,7 @@ podman ps --filter "label=casabot" --format "{{.Names}}\t{{.Status}}"
 podman ps -a --filter "label=casabot" --format "table {{.Names}}\t{{.Status}}\t{{.Created}}"
 ```
 
-## 7. Destroy and clean up agents
+## 8. Destroy and clean up agents
 
 Clean up agents that are no longer needed.
 
@@ -190,7 +250,7 @@ podman ps -a --filter "label=casabot" --format "{{.Names}}" | xargs -r podman st
 podman ps -a --filter "label=casabot" --format "{{.Names}}" | xargs -r podman rm
 ```
 
-## 8. Delegate tasks
+## 9. Delegate tasks
 
 How to pass tasks to sub-agents.
 
@@ -204,11 +264,11 @@ podman exec <agent-name> node /workspace/agent.js --task /workspace/task.txt
 ```
 
 ### Delegation principles
-- base is an orchestrator. Delegate actual work to sub-agents.
-- If no suitable sub-agent exists, create a new one and delegate.
-- Write task descriptions clearly and specifically.
+- The base agent is an orchestrator. Actual work is typically delegated to sub-agents.
+- If no suitable sub-agent exists, a new one can be created for the task.
+- Clear and specific task descriptions tend to produce better results.
 
-## 9. Collect results
+## 10. Collect results
 
 Check the results of sub-agent work.
 
@@ -226,4 +286,4 @@ ls ~/casabot/workspaces/<agent-name>/output/
 cat ~/casabot/workspaces/<agent-name>/output/result.txt
 ```
 
-After collecting results, summarize and report to the user.
+After collecting results, the findings can be summarized and reported to the user.

package/skills/config/SKILL.md

@@ -25,7 +25,8 @@ All CasAbot data is stored under `~/casabot/`.
 │   ├── config/           # Configuration management (this document)
 │   ├── chat/             # Conversation management
 │   ├── service/          # System service registration
-│   └── memory/           # Memory (memo) management
+│   ├── memory/           # Memory (memo) management
+│   └── subskills/        # Sub-agent skill attachment and management
 ├── workspaces/           # Per-agent workspaces
 │   └── <agent-name>/     # Individual agent working directory
 │       └── output/       # Agent output results

package/skills/subskills/SKILL.md

@@ -0,0 +1,199 @@
+---
+name: Sub-Agent Skills (subskills)
+description: Manual for attaching and managing skills available to sub-agents
+metadata:
+  casabot:
+    requires:
+      bins: []
+---
+
+# Sub-Agent Skills (subskills)
+
+This manual explains the `/subskills` directory mechanism — a way to attach, discover, and manage skill documents that sub-agents can use.
+
+---
+
+## 1. What is /subskills?
+
+Each skill directory under `~/casabot/skills/` can contain a `/subskills` subdirectory. This subdirectory holds skill documents intended for sub-agents rather than the base agent.
+
+```
+~/casabot/skills/
+├── agent/
+│   ├── SKILL.md
+│   └── subskills/          ← Skills for sub-agents in this domain
+│       ├── python-dev/
+│       │   └── SKILL.md
+│       └── web-scraper/
+│           └── SKILL.md
+├── memory/
+│   ├── SKILL.md
+│   └── subskills/
+│       └── vector-search/
+│           └── SKILL.md
+└── subskills/
+    └── SKILL.md             ← This document
+```
+
+### Key Concepts
+
+- **Base skills** (`SKILL.md` at the skill root) are read by the base agent.
+- **Subskills** (`subskills/<name>/SKILL.md`) are passed to sub-agents when they are created or delegated tasks.
+- Subskill documents follow the same format as regular skills (YAML frontmatter + Markdown body).
+
+## 2. Who can add subskills?
+
+### Agent-driven discovery
+
+The base agent (or a sub-agent) can search for relevant tools, libraries, or techniques and write a new subskill document based on the findings.
+
+```bash
+# Create a subskill directory
+mkdir -p ~/casabot/skills/agent/subskills/python-dev
+
+# Write the subskill document
+cat > ~/casabot/skills/agent/subskills/python-dev/SKILL.md << 'EOF'
+---
+name: Python Development
+description: Guidelines and tools for Python-based sub-agents
+metadata:
+  casabot:
+    requires:
+      bins: [python3, pip]
+---
+
+# Python Development
+
+Instructions for sub-agents working on Python projects...
+EOF
+```
+
+### User-provided subskills
+
+Users can also place skill documents directly into the `/subskills` directory of any skill. This is useful for domain-specific instructions or custom tool configurations that the user wants sub-agents to follow.
+
+```bash
+# User manually adds a subskill
+mkdir -p ~/casabot/skills/agent/subskills/my-custom-tool
+cat > ~/casabot/skills/agent/subskills/my-custom-tool/SKILL.md << 'EOF'
+---
+name: My Custom Tool
+description: Custom tool usage instructions for sub-agents
+metadata:
+  casabot:
+    requires:
+      bins: []
+---
+
+# My Custom Tool
+
+(Custom instructions for sub-agents...)
+EOF
+```
+
+## 3. How to pass subskills to sub-agents
+
+When creating or delegating to a sub-agent, mount or copy the relevant subskills into the container.
+
+### Mount the entire subskills directory
+
+```bash
+# Mount a specific skill's subskills into the container
+podman run -d \
+  --name <agent-name> \
+  --label casabot=true \
+  -v ~/casabot/skills/agent/subskills:/subskills:ro \
+  -v ~/casabot/workspaces/<agent-name>:/workspace \
+  node:20-slim sleep infinity
+```
+
+### Copy specific subskill documents
+
+```bash
+# Copy only the relevant subskill into the container
+podman cp ~/casabot/skills/agent/subskills/python-dev/SKILL.md \
+  <agent-name>:/workspace/skills/python-dev/SKILL.md
+```
+
+### Reading subskills inside a sub-agent
+
+```bash
+# List available subskills
+ls /subskills/
+
+# Read a specific subskill
+cat /subskills/python-dev/SKILL.md
+```
+
+## 4. Listing and searching subskills
+
+### List all subskills across all skill directories
+
+```bash
+find ~/casabot/skills/*/subskills -name "SKILL.md" 2>/dev/null
+```
+
+### Search subskills by keyword
+
+```bash
+grep -rl "keyword" ~/casabot/skills/*/subskills/ 2>/dev/null
+```
+
+### List subskills for a specific skill
+
+```bash
+ls ~/casabot/skills/agent/subskills/
+```
+
+## 5. Managing subskills
+
+### Remove a subskill
+
+```bash
+rm -rf ~/casabot/skills/<skill>/subskills/<subskill-name>
+```
+
+### Update a subskill
+
+Simply overwrite the `SKILL.md` file in the subskill directory.
+
+```bash
+cat > ~/casabot/skills/<skill>/subskills/<subskill-name>/SKILL.md << 'EOF'
+---
+name: Updated Skill Name
+description: Updated description
+metadata:
+  casabot:
+    requires:
+      bins: []
+---
+
+# Updated content...
+EOF
+```
+
+## 6. Subskill Document Format
+
+Subskill documents follow the same structure as regular skill documents:
+
+```yaml
+---
+name: Subskill Name
+description: What this subskill provides to sub-agents
+metadata:
+  casabot:
+    requires:
+      bins: []
+---
+
+# Subskill Title
+
+(Instructions, examples, and references for sub-agents)
+```
+
+## 7. Important Notes
+
+- Subskills are **not** automatically loaded by the base agent. They must be explicitly passed to sub-agents.
+- The base agent decides which subskills are relevant for a given task and passes them accordingly.
+- Agents are encouraged to search for new tools and techniques and create subskills to expand future capabilities.
+- Users can add subskills at any time without restarting CasAbot.

package/src/agent/base.ts

@@ -33,6 +33,8 @@ export function buildSystemPrompt(skills: Skill[]): string {
 2. Refer to skill documents first. Read the relevant SKILL.md and follow the instructions.
 3. Delegate to an appropriate sub-agent if one exists; otherwise, create a new one and delegate.
 4. Only perform orchestration (agent creation/delegation/management) directly.
+5. Try to solve problems independently using all available information before asking the user. Only ask the user when you truly need information you cannot obtain on your own (e.g. API keys, sudo passwords, personal preferences).
+6. When you encounter information worth remembering (e.g. user preferences, API keys, system details), use the memory skill to persist it for future sessions.
 
 ## Available Tools
 - \`run_command\`: Executes a command in the terminal. Use this single tool to read skills, manage sub-agents, and perform all orchestration.

package/src/cli/setup.ts

@@ -108,7 +108,8 @@ ls ~/casabot/workspaces/<agent-name>/output/
 │   ├── config/
 │   ├── chat/
 │   ├── service/
-│   └── memory/
+│   ├── memory/
+│   └── subskills/
 ├── workspaces/           # Per-agent workspaces
 ├── history/              # Full conversation logs (raw logs)
 └── memory/               # Agent-written memos (.md)
@@ -277,6 +278,63 @@ grep -rl "keyword" ~/casabot/memory/
 
 # Read specific memory file
 cat ~/casabot/memory/<filename>.md
+\`\`\``,
+    },
+    subskills: {
+      name: "Sub-Agent Skills (subskills)",
+      description: "Manual for attaching and managing skills available to sub-agents",
+      content: `# Sub-Agent Skills (subskills)
+
+## What is /subskills?
+Each skill directory can contain a \`/subskills\` subdirectory holding skill documents intended for sub-agents.
+
+\`\`\`
+~/casabot/skills/
+├── agent/
+│   ├── SKILL.md
+│   └── subskills/
+│       ├── python-dev/SKILL.md
+│       └── web-scraper/SKILL.md
+└── subskills/
+    └── SKILL.md
+\`\`\`
+
+## Who can add subskills?
+- **Agents**: Search for tools/techniques and write subskill documents autonomously.
+- **Users**: Place skill documents directly into any \`/subskills\` directory.
+
+\`\`\`bash
+# Create a subskill
+mkdir -p ~/casabot/skills/agent/subskills/python-dev
+cat > ~/casabot/skills/agent/subskills/python-dev/SKILL.md << 'EOF'
+---
+name: Python Development
+description: Guidelines for Python-based sub-agents
+metadata:
+  casabot:
+    requires:
+      bins: [python3]
+---
+# Python Development
+Instructions for sub-agents...
+EOF
+\`\`\`
+
+## Passing subskills to sub-agents
+\`\`\`bash
+# Mount subskills into container
+podman run -d --name <agent-name> --label casabot=true \\
+  -v ~/casabot/skills/agent/subskills:/subskills:ro \\
+  -v ~/casabot/workspaces/<agent-name>:/workspace \\
+  node:20-slim sleep infinity
+\`\`\`
+
+## Listing and searching
+\`\`\`bash
+# List all subskills
+find ~/casabot/skills/*/subskills -name "SKILL.md" 2>/dev/null
+# Search by keyword
+grep -rl "keyword" ~/casabot/skills/*/subskills/ 2>/dev/null
 \`\`\``,
     },
   };

package/src/config/manager.ts

@@ -13,7 +13,7 @@ export const PATHS = {
   memory: join(CASABOT_HOME, "memory"),
 } as const;
 
-const SKILL_DIRS = ["agent", "config", "chat", "service", "memory"];
+const SKILL_DIRS = ["agent", "config", "chat", "service", "memory", "subskills"];
 
 export function getDefaultConfig(): CasabotConfig {
   return {

package//354/227/220/354/235/264/354/240/204/355/212/270/354/227/220/352/262/214.md

@@ -0,0 +1,24 @@
+명심해야할 사항
+# 0. README를 읽고 시작할 것.
+1. README.md를 읽고 시작할 것.
+2. 현재 변경한 내용이 아니더라도 특정 부분이 README와 다르다면 README를 업데이트할 것.
+3. 변경 사항이 있었고 그 부분이 README에 명시된 내용 중 포함되어 있다면 README를 업데이트할 것.
+# 1. CasAbot의 시스템 프롬프트에는 다음 내용이 "영어로" 포함되어야 한다.
+1. SKILL을 잘 사용하기 위한 모든 내용
+2. 에이전트 자기 자신을 정의하는 내용
+3. 필요 시(예: api key, sudo 비밀번호 등) 사용자에게 정보를 요청해야 한다는 것
+4. 되도록이면 자신이 할 수 있는 모든 정보를 동원하여 사용자의 도움 없이 해결할 것
+5. 기억해야 하는 내용(예: 사용자 취향, api key, sudo 비밀번호, 현재 시스템 정보 등)이면 memory skill
+6. 기타 변경 가능 내용들
+# 2. 스킬 설명에서 명심해야할 사항
+1. 모든 스킬은 "어떻게 사용하는가"를 명시해야 하지만, "어떻게 사용해야 한다라고" 단정짓는 것은 피해야 한다. 에이전트가 스킬을 "자유롭고 창의적으로 이용"하는것이 중요하다.
+2. 스킬에 들어갈 내용은 "최신 사항"이어야 하며, "과거의 사실"이 포함되지 않아야 한다. 너의 지식은 과거의 지식이 많기 때문에 꼭 "검색"을 하여 최신 사항을 체크해야 한다.
+3. 스킬 문서는 영어로 작성되어야 하지만, "일부 예외적인 상황"에서는 다른 언어로 작성을 허용한다.
+# 3. 철학 변경 금지
+1. README에 명시되어 있는 핵심 철학을 확인할 것.
+2. 핵심 철학을 이해하였다면 절대 핵심 철학을 변경하지 말것.
+3. 핵심 철학을 이해하지 못하였다면, 너의 지식이 부족한 것이니, 검색을 하여 찾아볼 것.
+# 4. 실행 환경
+1. 이 패키지는 이 컴퓨터에서 실행되지 않는다.여기서 실행하게 하지 말 것.
+2. 이 패키지는 여기 설치되어 있지 않다. 이 환경 기준으로 생각하지 말 것.
+