iterm-cross-skill-sourcing

Source shared utility scripts from sibling directories within the iTerm plugin.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/manifoldlogic/claude-code-plugins --skill iterm-cross-skill-sourcing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: iterm-cross-skill-sourcing
Source: https://github.com/manifoldlogic/claude-code-plugins/tree/main/plugins/iterm/skills/iterm-cross-skill-sourcing
Command: npx skills add https://github.com/manifoldlogic/claude-code-plugins --skill iterm-cross-skill-sourcing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The need to duplicate utility scripts across iTerm plugin skills can be complex and error-prone.

Core Features & Use Cases

  • Shared Utility Scripts: Facilitates the use of common utility scripts across sibling skills within the iTerm plugin.
  • Consistent Scripting: Ensures all scripts use a standard set of shared utilities.
  • Simplified Setup: Reduces setup complexity and potential for errors when including multiple utility scripts in separate skills.

Quick Start

Source shared utilities for your iTerm scripts by following the pattern outlined in the Skill.

Frequently Asked Questions about iterm-cross-skill-sourcing

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

FAQPage Schema
How do I source shared utility scripts across iTerm plugin skills?

Sourcing shared utility scripts across iTerm plugin skills involves referencing the `iterm-utils.sh` file from a shared directory structure, eliminating duplication and ensuring consistent script execution across sibling directories.

What is the best way to avoid duplicating bash utilities in multiple iTerm scripts?

Avoiding bash utility duplication in iTerm scripts is achieved by using a cross-plugin sourcing pattern that pulls standard functions from a centralized shared location, reducing setup complexity and preventing scripting errors.

Does cross-plugin sourcing require specific dependencies for iTerm bash scripting?

Cross-plugin sourcing requires no external dependencies, relying solely on the presence of the `iterm-utils.sh` utility script stored within the shared location of the iTerm plugin directory structure.

Can I use shared utility scripts with sibling directories in my iTerm plugin?

Shared utility scripts work directly with sibling directories inside the iTerm plugin by sourcing `iterm-utils.sh` from a shared path, allowing all sibling skills to access a standard set of common functions.

Why does my iTerm bash script fail to find standard utility functions?

iTerm bash scripts fail to find standard utility functions when they do not correctly source `iterm-utils.sh` from the designated shared location in the plugin directory, breaking consistency across sibling skills.