add-remote-installer

Generates install.ps1 and update-check snippet for PowerShell repositories from Git remote data.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/aberrantCode/llm_skills --skill add-remote-installer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-remote-installer
Source: https://github.com/aberrantCode/llm_skills/tree/main/claude/skills/add-remote-installer
Command: npx skills add https://github.com/aberrantCode/llm_skills --skill add-remote-installer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating a remote install script and self‑update logic for PowerShell projects is error‑prone and time‑consuming. This skill automates detection of repository context, identifies the main app script, gathers install parameters, and generates both install.ps1 and an update‑check block.

Core Features & Use Cases

  • Auto‑detect repository metadata: parses Git remote to obtain owner/repo and checks for typical launcher scripts.
  • Primary script resolution: extracts the target app script from scripts/Start-App.ps1 or prompts the user when ambiguous.
  • Interactive context gathering: asks only for missing information such as install directory or required PowerShell module.
  • Delegates to remote‑installer: creates a robust install.ps1 and injects an update‑check snippet into the app script.
  • Verification step: ensures generated artifacts exist and pass safety checklists.

Use case: When onboarding a new PowerShell application repository, run this skill to instantly equip the project with a one‑liner remote installer and automatic self‑updates.

Quick Start

Ask the skill to add a remote installer to the current repository.

Frequently Asked Questions about add-remote-installer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a remote install script with self-update to a PowerShell repository?

To add a remote install script with self-update, you can automate detection of Git repository metadata and generate an install.ps1 file alongside an update-check block injected into your primary app script.

What is the best way to automate PowerShell installer generation for Git projects?

Automating PowerShell installer generation involves parsing Git remote URLs for owner and repository data, resolving the primary application script, and delegating artifact creation to a remote-installer component.

Do I need Git to generate a remote installer for my PowerShell app?

Yes, Git is required to read the remote URL and extract repository context, while PowerShell is needed to generate the install.ps1 file and inject the self-update snippet.

How does the script identify the primary app script for deployment?

The primary app script for deployment is identified by checking for typical launcher scripts like scripts/Start-App.ps1, or by interactively prompting the user when the target script is ambiguous.

Can I use this approach if my repository only has a launcher script and .env.example?

Yes, this approach applies to repositories where a launcher script and optional .env.example exist, automatically gathering missing context like install directory or required PowerShell modules.

What happens after the install.ps1 and update-check block are generated?

After generating the install.ps1 and update-check block, a verification step runs to ensure the generated artifacts exist on disk and pass required safety checklists before completing the process.