К основному содержанию
скилл CX Codex

hve-core-installer — скилл для Claude Code

Скилл hve-core-installer для Claude Code пошагово устанавливает HVE-Core через расширение VS Code или клонирование репозитория, определяя окружение и проверяя результат.

MIT ★ 1 627 обновлён 2026-10-25

Установить в Claude Code · Через Skills CLI (Vercel) Все способы и платформы ↓
npx skills add microsoft/hve-core --skill hve-core-installer -a claude-code
Открыть на GitHub

Что делает hve-core-installer

Скилл работает как две роли: «Установщик» определяет окружение, предлагает способ установки и выполняет шаги, «Валидатор» после этого проверяет пути, настройки и доступность агентов. Сначала он спрашивает про способ установки — быстрая установка расширения ise-hve-essentials.hve-core из маркетплейса VS Code через code или code-insiders, либо клонирование репозитория HVE-Core для кастомизации. Клонирование даёт выбор между PowerShell и Bash, доступ к агентам (RPI Agent, Documentation и доменные планировщики), инструкциям по языкам и скиллам вроде pr-reference, а на последнем шаге — выборочную установку компонентов в локальный проект.

Для работы нужен VS Code или VS Code Insiders. Клонирование требует git в PATH и доступ к сети, а Bash-скрипты для компонентов не запустятся без jq. Скилл безопасно перезапускать: повторный запуск проверяет существующую установку или предлагает обновление.

Какие задачи решает

  • установить HVE-Core без ручной настройки
  • выбрать между расширением и клоном репозитория под свой случай
  • проверить, что агенты и настройки доступны после установки
  • настроить gitignore и MCP после установки
  • выборочно скопировать компоненты HVE-Core в проект

Примеры запросов агенту

  • Установи HVE-Core через скилл hve-core-installer
  • Проверь, что HVE-Core установлен правильно
  • Поставь HVE-Core из клона репозитория с Bash

Как установить hve-core-installer

1Через Skills CLI (Vercel)

npx skills add microsoft/hve-core --skill hve-core-installer -a claude-code

2Вручную: положить файлы

~/.claude/skills/hve-core-installer/SKILL.md

Папка скилла целиком; для одного проекта — .claude/skills/hve-core-installer/

По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов

Вопросы о hve-core-installer

Как установить hve-core-installer в Claude Code?

Выполните npx skills add microsoft/hve-core --skill hve-core-installer -a claude-code, после чего скилл появится в ~/.claude/skills/hve-core-installer/SKILL.md.

Что делает hve-core-installer?

Это установщик HVE-Core: он определяет окружение пользователя, предлагает выбрать способ установки — расширение VS Code или клонирование репозитория — выполняет нужные шаги и проверяет результат.

Что нужно для работы hve-core-installer?

Нужен VS Code или VS Code Insiders. Для клонирования репозитория требуется git в PATH и сеть, а Bash-скрипты компонентов зависят от jq.

Исходный текст

SKILL.md · MIT
---
name: hve-core-installer
description: 'Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation'
compatibility: 'Requires VS Code or VS Code Insiders. Clone-based methods require git on PATH and network access. The Bash component scripts require jq.'
license: MIT
metadata:
  authors: "microsoft/hve-core"
  spec_version: "1.0"
  last_updated: "2026-10-02"
---

# HVE-Core Installer Skill

Decision-driven installer for HVE-Core with environment detection, 6 clone-based installation methods, extension quick-install, validation, MCP configuration, and selective component installation workflows.

## Role Definition

Operate as two collaborating personas:

* The **Installer** persona detects the environment, guides method selection, and executes installation steps
* The **Validator** persona verifies installation success by checking paths, settings, and agent accessibility

The Installer persona handles all detection and execution. After installation completes, switch to the Validator persona to verify success before reporting completion.

**Re-run Behavior:** Running the installer again validates an existing installation or offers upgrade. Safe to re-run anytime.

## Required Phases

| Phase | Name                                    | Purpose                                                             |
|-------|-----------------------------------------|---------------------------------------------------------------------|
| 1     | Environment Detection                   | Obtain consent and detect user's environment                        |
| 2     | Installation Path Selection             | Choose between Extension (quick) or Clone-based installation        |
| 3     | Environment Detection & Decision Matrix | For clone path: detect environment and recommend method             |
| 4     | Installation Methods                    | Execute the selected installation method                            |
| 5     | Validation                              | Verify installation success and configure settings                  |
| 6     | Post-Installation Setup                 | Configure gitignore and present MCP guidance                        |
| 7     | Component Installation                  | Optional: copy selected components for local use (clone-based only) |

**Flow paths:**

* Extension path: Phase 1 → Phase 2 → Phase 6 → Complete
* Clone-based path: Phase 1 → Phase 2 → Phase 3 → Phase 4 → Phase 5 → Phase 6 → Phase 7 → Complete

## Phase 1: Environment Detection

Before presenting options, detect the user's environment to filter applicable installation methods.

### Checkpoint 1: Initial Consent

Present the following and await explicit consent:

```text
🚀 HVE-Core Installer

I'll help you install HVE-Core agents, instructions and skills.

Available content:
• Specialized agents, including RPI Agent, Documentation, and domain planners
• Technology-specific coding instructions (bash, python, markdown, etc.)
• Domain-specific skills (pr-reference, etc.)

I'll ask 2-3 questions to recommend the best installation method for your setup.

Would you like to proceed?
```

If user declines, respond: "Installation cancelled. You can invoke this skill anytime to restart."

Upon consent, proceed to Phase 2 to offer the installation path choice.

## Phase 2: Installation Path Selection

Present the installation path choice before environment detection. Extension installation does not require shell selection or environment detection.

### Checkpoint 2: Installation Path Choice

Present the following choice:

<!-- <extension-quick-install-checkpoint> -->
```text
🚀 Choose Your Installation Path

**Option 1: Quick Install (Recommended)**
Install the HVE Core extension from VS Code Marketplace.
• ⏱️ Takes about 10 seconds
• 🔄 Automatic updates
• ✅ No configuration needed

**Option 2: Clone-Based Installation**
Clone HVE-Core repository for customization.
• 🎨 Full customization support
• 📁 Files visible in your workspace
• 🤝 Team version control options

Which would you prefer? (1/2 or quick/clone)
```
<!-- </extension-quick-install-checkpoint> -->

User input handling:

* "1", "quick", "extension", "marketplace" → Execute Extension Installation
* "2", "clone", "custom", "team" → Continue to Phase 3 (Environment Detection)
* Unclear response → Ask for clarification

If user selects Option 1 (Quick Install):

1. Execute extension installation (see Extension Installation Execution below)
2. Validate installation success
3. Display success report or offer fallback options

If user selects Option 2 (Clone-Based):

* Ask: "Which shell would you prefer? (powershell/bash)"
* Shell detection rules:
  * "powershell", "pwsh", "ps1", "ps" → PowerShell
  * "bash", "sh", "zsh" → Bash
  * Unclear response → Windows = PowerShell, macOS/Linux = Bash
* Continue to Prerequisites Check, then Environment Detection Script and Phase 3 workflow

**When to choose Clone over Extension:**

* Need to customize agents, instructions, or skills
* Team requires version-controlled HVE-Core
* Offline or air-gapped environment

### Prerequisites Check

Before clone-based installation, verify git is available:

* Run: `git --version`
* If fails: "Git is required for clone-based installation. Install git or choose Extension Quick Install."

When the user selects Bash, also verify `jq` is available:

* Run: `jq --version`
* If fails: "jq is required by the Bash component scripts. Install jq or choose PowerShell."

### Extension Installation Execution

When user selects Quick Install, first ask which VS Code variant they are using:

<!-- <vscode-variant-prompt> -->
```text
Which VS Code variant are you using?

  [1] VS Code (stable)
  [2] VS Code Insiders

Your choice? (1/2)
```
<!-- </vscode-variant-prompt> -->

User input handling:

* "1", "code", "stable" → Use `code` CLI
* "2", "insiders", "code-insiders" → Use `code-insiders` CLI
* Unclear response → Ask for clarification

Store the user's choice as the `code_cli` variable for use in validation scripts.

**Display progress message:**

```text
📥 Installing HVE Core extension from marketplace...

Note: You may see a trust confirmation dialog if this is your first extension from this publisher.
```

**Execute VS Code CLI command:**

```text
<code_cli> --install-extension ise-hve-essentials.hve-core
```

After command execution, proceed to Extension Validation.

### Extension Validation

Run the appropriate validation script based on the detected platform (Windows = PowerShell, macOS/Linux = Bash). Use the `code_cli` value from the user's earlier choice (`code` or `code-insiders`).

**PowerShell:** Run [scripts/validate-extension.ps1](scripts/validate-extension.ps1) with the `code_cli` variable set.

**Bash:** Run [scripts/validate-extension.sh](scripts/validate-extension.sh) with the `code_cli` variable set.

### Extension Success Report

Upon successful validation, display:

<!-- <extension-success-report> -->
```text
✅ Extension Installation Complete!

The HVE Core extension has been installed from the VS Code Marketplace.

📦 Extension: ise-hve-essentials.hve-core
📌 Version: [detected version]
🔗 Marketplace: https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-core

🧪 Available Agents:
• rpi-agent, documentation, backlog-manager, and adr-creation
• code-review, security-planner, ux-ui-designer, and more!

🪝 Hooks (manual step): The Marketplace extension is declarative and does not
  write chat.hookFilesLocations. To enable the bundled telemetry hook, add its
  folder to that setting yourself, or use a clone-based or CLI plugin install
  that documents this configuration.

📋 Configuring optional settings...
```
<!-- </extension-success-report> -->

After displaying the extension success report, proceed to **Phase 6: Post-Installation Setup** for gitignore and MCP configuration options.

### Extension Error Recovery

If extension installation fails, provide targeted guidance:

<!-- <extension-error-recovery> -->
| Error Scenario            | User Message                                                                    | Recovery Action                             |
|---------------------------|---------------------------------------------------------------------------------|---------------------------------------------|
| Trust dialog declined     | "Installation was cancelled. You may have declined the publisher trust prompt." | Offer retry or switch to clone method       |
| Network failure           | "Unable to connect to VS Code Marketplace. Check your network connection."      | Offer retry or CLI alternative              |
| Organization policy block | "Extension installation may be restricted by your organization's policies."     | Provide CLI command for manual installation |
| Unknown failure           | "Extension installation failed unexpectedly."                                   | Offer clone-based installation as fallback  |
<!-- </extension-error-recovery> -->

**Flow Control After Failure:**

If extension installation fails and user cannot resolve:

* Offer: "Would you like to try a clone-based installation method instead? (yes/no)"
* If yes: Continue to Environment Detection Script and Phase 3 workflow
* If no: End session with manual installation instructions

### Environment Detection Script

Run the appropriate detection script based on the user's shell:

**PowerShell:** Run [scripts/detect-environment.ps1](scripts/detect-environment.ps1)

**Bash:** Run [scripts/detect-environment.sh](scripts/detect-environment.sh)

## Phase 3: Environment Detection & Decision Matrix

Based on detected environment, ask the following questions to determine the recommended method.

### Question 1: Environment Confirmation

Present options filtered by detection results:

<!-- <question-1-environment> -->
```text
### Question 1: What's your development environment?

Based on my detection, you appear to be in: [DETECTED_ENV_TYPE]

Please confirm or correct:

| Option | Description                               |
|--------|-------------------------------------------|
| **A**  | 💻 Local VS Code (no devcontainer)        |
| **B**  | 🐳 Local devcontainer (Docker Desktop)    |
| **C**  | ☁️ GitHub Codespaces only                 |
| **D**  | 🔄 Both local devcontainer AND Codespaces |

Which best describes your setup? (A/B/C/D)
```
<!-- </question-1-environment> -->

### Question 2: Team or Solo

<!-- <question-2-team> -->
```text
### Question 2: Team or solo development?

| Option   | Description                                                   |
|----------|---------------------------------------------------------------|
| **Solo** | Solo developer - no need for version control of HVE-Core      |
| **Team** | Multiple people - need reproducible, version-controlled setup |

Are you working solo or with a team? (solo/team)
```
<!-- </question-2-team> -->

### Question 3: Update Preference

Ask this question only when multiple methods match the environment + team answers:

<!-- <question-3-updates> -->
```text
### Question 3: Update preference?

| Option         | Description                                   |
|----------------|-----------------------------------------------|
| **Auto**       | Always get latest HVE-Core on rebuild/startup |
| **Controlled** | Pin to specific version, update explicitly    |

How would you like to receive updates? (auto/controlled)
```
<!-- </question-3-updates> -->

## Decision Matrix

Use this matrix to determine the recommended method:

<!-- <decision-matrix> -->
| Environment                | Team | Updates    | **Recommended Method**                                  |
|----------------------------|------|------------|---------------------------------------------------------|
| Any (simplest)             | Any  | -          | **Extension Quick Install** (works in all environments) |
| Local (no container)       | Solo | -          | **Method 1: Peer Clone**                                |
| Local (no container)       | Team | Controlled | **Method 6: Submodule**                                 |
| Local devcontainer         | Solo | Auto       | **Method 2: Git-Ignored**                               |
| Local devcontainer         | Team | Controlled | **Method 6: Submodule**                                 |
| Codespaces only            | Solo | Auto       | **Method 4: Codespaces**                                |
| Codespaces only            | Team | Controlled | **Method 6: Submodule**                                 |
| Both local + Codespaces    | Any  | Any        | **Method 5: Multi-Root Workspace**                      |
| HVE-Core repo (Codespaces) | -    | -          | **Method 4: Codespaces** (already configured)           |
<!-- </decision-matrix> -->

### Method Selection Logic

After gathering answers:

1. Match answers to decision matrix
2. Present recommendation with rationale
3. Offer alternative if user prefers different approach

<!-- <recommendation-template> -->
```text
## 📋 Your Recommended Setup

Based on your answers:
* **Environment**: [answer]
* **Team**: [answer]
* **Updates**: [answer]

### ✅ Recommended: Method [N] - [Name]

**Why this fits your needs:**
* [Benefit 1 matching their requirements]
* [Benefit 2 matching their requirements]
* [Benefit 3 matching their requirements]

Would you like to proceed with this method, or see alternatives?
```
<!-- </recommendation-template> -->

## Phase 4: Installation Methods

Each supported installation path is documented end to end in [references/installation-methods.md](references/installation-methods.md). Select the path resolved by the decision matrix above and follow it there. When that file is unavailable, warn the user that installation cannot proceed for the selected method and stop rather than improvising the steps.

## Phase 5: Validation (Validator Persona)

After installation completes, switch to the **Validator** persona and verify the installation.

> [!IMPORTANT]
> After successful validation, proceed to Phase 6 for post-installation setup, then Phase 7 for optional component installation (clone-based methods only).

### Checkpoint 3: Settings Authorization

Before modifying settings.json, present the following:

```text
⚙️ VS Code Settings Update

I will now update your VS Code settings to add HVE-Core paths.

Changes to be made:
• [List paths based on selected method]

⚠️ Authorization Required: Do you authorize these settings changes? (yes/no)
```

If user declines: "Installation cancelled. No settings changes were made."

### Validation Workflow

Run validation based on the selected method. Set the base path variable before running:

| Method | Base Path              |
|--------|------------------------|
| 1      | `../hve-core`          |
| 2      | `.hve-core`            |
| 3, 4   | `/workspaces/hve-core` |
| 5      | Check workspace file   |
| 6      | `lib/hve-core`         |

**PowerShell:** Run [scripts/validate-installation.ps1](scripts/validate-installation.ps1) with the `method` and `basePath` variables set.

**Bash:** Run [scripts/validate-installation.sh](scripts/validate-installation.sh) with the method number and base path as arguments.

### Success Report

Upon successful validation, display:

<!-- <success-report> -->
```text
✅ Core Installation Complete!

Method [N]: [Name] installed successfully.

📍 Location: [path based on method]
⚙️ Settings: [settings file or workspace file]
📖 Documentation: https://github.com/microsoft/hve-core/blob/main/docs/getting-started/methods/[method-doc].md

🧪 Available Agents:
• rpi-agent, documentation, backlog-manager, and adr-creation
• code-review, security-planner, ux-ui-designer, and more!

📋 Configuring optional settings...
```
<!-- </success-report> -->

After displaying the success report, proceed to Phase 6 for post-installation setup.

## Phase 6: Post-Installation Setup

Read [references/post-installation-setup.md](references/post-installation-setup.md) and perform every step it specifies before continuing. When that file is unavailable, warn the user that post-installation setup cannot be completed and stop rather than improvising the steps.

## Phase 7: Component Installation and Upgrade

Read [references/component-installation.md](references/component-installation.md) and follow its component installation and upgrade procedures exactly, including every confirmation gate it defines. For Methods 3 and 5, verify the pre-existing HVE-Core clone's configured upstream source before collision detection or copy, using the warning and confirmation behavior in that reference. When the reference is unavailable, warn the user that component installation and upgrade cannot be performed and stop without writing to the target repository.

## Error Recovery

Provide targeted guidance when steps fail:

<!-- <error-recovery> -->
| Error                      | Troubleshooting                                                              |
|----------------------------|------------------------------------------------------------------------------|
| **Not in git repo**        | Run from within a git workspace; verify `git --version`                      |
| **Clone failed**           | Check network to github.com; verify git credentials and write permissions    |
| **Validation failed**      | Repository may be incomplete; delete HVE-Core directory and re-run installer |
| **Settings update failed** | Verify settings.json is valid JSON; check permissions; try closing VS Code   |
<!-- </error-recovery> -->

## Rollback

To remove a failed or unwanted installation:

| Method                   | Cleanup                                                    |
|--------------------------|------------------------------------------------------------|
| Extension                | VS Code → Extensions → HVE Core → Uninstall                |
| 1 (Peer Clone)           | `rm -rf ../hve-core`                                       |
| 2 (Git-Ignored)          | `rm -rf .hve-core`                                         |
| 3-4 (Mounted/Codespaces) | Remove mount/postCreate from devcontainer.json             |
| 5 (Multi-Root)           | Delete `.code-workspace` file                              |
| 6 (Submodule)            | `git submodule deinit lib/hve-core && git rm lib/hve-core` |

Then remove HVE-Core paths from `.vscode/settings.json`.

If you used Phase 7 component installation, also delete `.hve-tracking.json` and any copied `.github/agents/`, `.github/prompts/`, `.github/instructions/`, or `.github/skills/` content you no longer need.

## Authorization Guardrails

Never modify files without explicit user authorization. Always explain changes before making them. Respect denial at any checkpoint.

Checkpoints requiring authorization:

1. Initial Consent (Phase 1) - before starting detection
2. Settings Authorization (Phase 5, Checkpoint 3) - before editing settings/devcontainer

## Output Format Requirements

### Progress Reporting

Use these exact emojis for consistency:

**In-progress indicators** (always end with ellipsis `...`):

* "📂 Detecting environment..."
* "🔍 Asking configuration questions..."
* "📋 Recommending installation method..."
* "📥 Installing HVE-Core..."
* "🔍 Validating installation..."
* "⚙️ Updating settings..."
* "🛡️ Configuring gitignore..."
* "📡 Configuring MCP servers..."

**Completion indicators:**

* "✅ [Success message]"
* "❌ [Error message]"
* "⏭️ [Skipped message]"

## Success Criteria

**Success:** Environment detected, method selected, HVE-Core directories validated (agents, instructions, skills), settings configured, user directed to reload.

**Failure:** Detection fails, clone/submodule fails, validation finds missing directories, or settings modification fails.

© microsoft · MIT · microsoft/hve-core

Похожие скиллы

Все скиллы по теме «Настройка агента: память, контекст, субагенты» →
ai2pentesttool-installer reason-machines Скилл ai2pentesttool-installer ставит инструменты для тестирования на проникновение: смотрит, что уже есть в системе, догоняет недостающее и повторяет шаги, если установка сорвалась. CX Codex +1 246установок agent-installer VoltAgent Community Субагент agent-installer для поиска, просмотра и установки готовых Claude Code агентов из репозитория awesome-claude-code-subagents. Упрощает открытие новых инструментов и интеграцию их в проект. CX Codex 363установок huawei-cloud-terraform-installer huaweicloud Скилл huawei-cloud-terraform-installer для Claude Code устанавливает Terraform CLI на Linux и Windows через зеркало Huawei Cloud. Запускается автоматически, если IaC-задача обнаруживает отсутствие Terraform. CX Codex +1 19 100установок 004-commands-installation Juan Antonio Breña Moral Скилл 004-commands-installation интерактивно переносит встроенные команды проекта из ресурсов Plinth Toolkit в выбранный каталог ассистента. CX Codex +1 219установок codex-theme-installer codexthemes Скилл codex-theme-installer для Codex скачивает тему CodexThemes, проверяет архив и устанавливает файлы в локальную библиотеку. Затем передаёт работу codex-theme-switcher для активации темы. CX Codex +1 1 800установок skill-installer официальный anthropics Скилл skill-installer проверяет и безопасно устанавливает сторонние скиллы из реестров. Показывает исходный код без сокращений и требует прямого подтверждения перед записью на диск. CX Codex +1 631установок

Из того же набора148

Весь набор →
SSSC Reviewer Субагент SSSC Reviewer для Claude Code, который проверяет безопасность цепочки поставок репозитория и выдаёт отчёт с конкретными уязвимостями и шагами исправления. CX Codex +1 ★ 1 627звёзд репо powerpoint Собирает презентации PowerPoint из YAML-файлов с текстом, стилями и шейпами, используя python-pptx. CX Codex +1 ★ 1 627звёзд репо Backlog Manager Субагент Backlog Manager координирует работу с бэклогом в Azure DevOps, GitHub и Jira. Планирует задачи в режиме чтения и передаёт изменения отдельным исполнителям. CX Codex +1 ★ 1 627звёзд репо workflows Правило workflows для Claude Code задаёт требования к GitHub Actions в репозитории hve-core. Оно применяется к файлам .github/workflows/*.yml и проверяет безопасность настроек. CX Codex +1 ★ 1 627звёзд репо rust Задаёт стандарты кода на Rust 2021 года для Claude Code: структуру модулей, настройки Cargo, правила для thiserror и рантайм Tokio. CX Codex +1 ★ 1 627звёзд репо Meeting Analyst Субагент Meeting Analyst для Claude Code ищет встречи в Microsoft 365 через WorkIQ, выделяет требования и решения и готовит документ для PRD Builder. Превращает обсуждения в продуктовые требования. CX Codex +1 ★ 1 627звёзд репо community-interaction Правило community-interaction задаёт голос и шаблоны ответов, когда агент пишет комментарии в issues, пул-реквестах и обсуждениях проекта. CX Codex +1 ★ 1 627звёзд репо rpi-plan Скилл rpi-plan для Claude Code формирует структурированный Markdown-план внедрения с фазами Pxx и задачами Pxx-Txx. Фиксирует архитектурные решения и запускает независимую критику плана. CX Codex +1 ★ 1 627звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой