ワンクリックで
installing-dependencies
Use before installing dependencies, packages, or tools required for building project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use before installing dependencies, packages, or tools required for building project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Best practices for AI-driven English-to-Chinese translation. This skill should be used when the user asks to "translate to Chinese", "update the Chinese translation", "improve Chinese translation", "fix translation quality", "review Chinese translation", or when translating any English text into Chinese. Also applies when polishing an existing Chinese translation of English content.
This skill should be used when sending images, files, or notifications back to the user via messaging platforms (Discord, Feishu, Telegram, etc.) through cc-connect. TRIGGER when agent generates a plot/chart/screenshot and wants to show the user; agent creates a report/PDF/file the user should receive; agent needs to proactively notify the user (e.g. task completed, alert, reminder); user asks to "send image", "show me the chart", "notify me", "send the file", "send to Telegram", "show plot in Discord".
Browser automation CLI for AI agents. Use when needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. TRIGGER when user requests to "open a website", "fill out a form", "click a button", "take a screenshot", "debug this in browser", "scrape data from a page", "test this web app", "login to a site", "frontend UI/UX aesthetics", "automate browser actions", or any task requiring programmatic web interaction.
Review common AI slops of defensive programming patterns, avoid silent errors. TRIGGER when reviewing code for defensive anti-patterns, writing fail-fast code, or auditing error handling quality.
Guide for writing ast-grep rules to perform structural code search and analysis. This skill should be used when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search, or when a simple grep/glob search is insufficient for structural code pattern matching.
This skill should be used when the user asks about "code complexity", "cyclomatic complexity", "cognitive complexity", "code metrics", "maintainability index", "code coverage", or when measuring code quality quantitatively. Provides metrics thresholds and measurement techniques.
| name | installing-dependencies |
| description | Use before installing dependencies, packages, or tools required for building project. |
If the install command writes anything outside the current project directory, stop and ask the user for permission first.
This is non-negotiable. No exceptions.
Before running any install command, ask:
Does this command write outside the project directory?
YES -> Ask user for permission. Do not proceed until granted.
NO -> Proceed.
Is there no virtual environment / local package setup yet?
YES -> Initialize one first, then install.
NO -> Install into the existing local environment.
# Initialize venv if not present
uv venv # preferred
python -m venv .venv
# Install into venv
uv add <pkg>
uv pip install <pkg>
.venv/bin/pip install <pkg>
# NEVER without permission
pip install <pkg> # writes to system Python
pip install --user <pkg> # writes to ~/.local
# Install locally (default behavior)
npm install <pkg>
npm install --save-dev <pkg>
bun add <pkg>
bun add -d <pkg>
# NEVER without permission
npm install -g <pkg> # writes to system node_modules
bun add -g <pkg>
# Add as project dependency
cargo add <pkg>
# NEVER without permission
cargo install <pkg> # writes to ~/.cargo/bin
# NEVER without permission
sudo apt install <pkg>
brew install <pkg>
pip install <pkg> # system pip
System-level tools (runtimes, compilers, CLI utilities) always require explicit user permission. If a required tool is missing, inform the user and ask them to install it rather than installing it yourself.
Any path that is not under the current working project folder, including:
~/.local~/.cargo/usr/local/usr/libnode_modulesState clearly:
Wait for explicit approval before proceeding.