extension-installer

Install and configure Freshell extensions from GitHub or local directories.

93|28|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/danshapiro/freshell --skill extension-installer-danshapiro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: extension-installer
Source: https://github.com/danshapiro/freshell/tree/main/.claude/skills/extension-installer
Command: npx skills add https://github.com/danshapiro/freshell --skill extension-installer-danshapiro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Installing and configuring Freshell extensions from GitHub repositories, local directories, or from scratch as custom panes is often error-prone and time-consuming.

Core Features & Use Cases

  • Install extensions from GitHub or local directories and prepare them for use in Freshell.
  • Validate and enforce manifest requirements (freshell.json), ensure pre-built artifacts exist, and maintain a safe, restart-driven load workflow.
  • Create or update extension metadata via the recommended symlink workflow, then restart Freshell to load the new extension.

Quick Start

Clone or create the extension, ensure a valid freshell.json manifest, symlink it into ~/.freshell/extensions, and restart Freshell.

Frequently Asked Questions about extension-installer

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

FAQPage Schema
How do I install Freshell extensions from a local directory or GitHub repository?▼

To install Freshell extensions, you clone or create the project, validate the freshell.json manifest, ensure pre-built artifacts exist, symlink it into ~/.freshell/extensions, and restart Freshell to load the extension reliably.

What is the safe symlink workflow for adding custom panes in Freshell?▼

The safe symlink workflow for Freshell extensions involves creating or updating extension metadata, symlinking the project directory into ~/.freshell/extensions, and restarting Freshell to trigger the startup discovery workflow and load the custom pane safely.

Why is my Freshell extension not loading after installation?▼

Freshell extensions fail to load if the freshell.json manifest is invalid, pre-built artifacts are missing, the category block is incorrect, or the symlink was not created properly before restarting Freshell to trigger startup discovery.

Do I need pre-built artifacts and a valid manifest to configure Freshell extensions?▼

Yes, configuring Freshell extensions requires a valid freshell.json manifest with a single category block and existing pre-built artifacts to ensure the startup discovery workflow can load the extension reliably without errors.

Can I create Freshell extensions from scratch and debug their installation process?▼

Yes, you can create Freshell extensions from scratch and debug their installation by validating manifest requirements, enforcing pre-built artifacts, creating safe symlinks, and verifying the startup discovery workflow loads the extension upon restart.

What is the best way to update an existing Freshell extension safely?▼

The best way to update Freshell extensions is to modify the project directory, validate the freshell.json manifest, ensure pre-built artifacts are current, update the symlink in ~/.freshell/extensions, and restart Freshell to load the new extension.