hve-core-installer Skill
Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation Published by microsoft in hve-core.
Decision snapshot
Is this a fit?
Developers using hve-core, Includes SKILL.md, Reusable instructions
VS Code
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
How to use hve-core-installer Skill
Compatible clients
What is hve-core-installer Skill?
Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation Published by microsoft in hve-core. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using hve-core
Declared skill metadata
- Declared license: MIT
- Compatibility: Requires VS Code or VS Code Insiders. Clone-based methods require git on PATH and network access. The Bash component scripts require jq.
- Source file: .github/skills/installer/hve-core-installer/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Works with VS Code
When to use hve-core-installer Skill
- Use it for developers using hve-core.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/hve-core
- Skill file: .github/skills/installer/hve-core-installer/SKILL.md
What it does
Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation
Skill instructions
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
Verified compatibility and discovery
Frequently asked questions
What is hve-core-installer?
hve-core-installer is a open-source AI agent skill for VS Code with Copy skill directory. Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation
Who is hve-core-installer best for?
hve-core-installer is best for reusing agent instructions, scripts, and references, vs code users.
How do I install hve-core-installer?
Install or run hve-core-installer using Copy skill directory. Check hve-core-installer for the latest setup command.
Is hve-core-installer actively maintained?
hve-core-installer may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
