skills.rest
susomejias
susomejiasCOMMUNITY
Explore all skills by this author →
Website𝕏@susomejiasGitHub

rembric-tui-installer

Enforce the canonical Rembric TUI installer contract for lifecycle operations.

9|1|Updated May 13, 2026
Search Tags:#validation#mcp#plugin#installer#tui#shell-script#rembric
One-click install
npx skills add https://github.com/susomejias/rembric --skill rembric-tui-installer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rembric-tui-installer
Source: https://github.com/susomejias/rembric/tree/main/.agents/skills/rembric-tui-installer
Command: npx skills add https://github.com/susomejias/rembric --skill rembric-tui-installer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of broken or inconsistent Rembric TUI installer implementations by providing the single, authoritative contract for all install, setup, upgrade, and uninstall operations for the Rembric server and its supported client plugins, preventing user-facing failures from divergent installer logic.

Core Features & Use Cases

  • Canonical Workflow Enforcement: Defines the single user-facing path for all Rembric lifecycle operations, eliminating fragmented or conflicting installer implementations across client plugins.
  • Orchestrator Model Guardrails: Mandates that the root installer delegates to per-client install scripts instead of duplicating logic, reducing maintenance overhead and cross-client bugs.
  • Safety & Compatibility Requirements: Enforces strict rules for token handling, POSIX shell compatibility, conservative uninstall behavior, and required validation suite execution to prevent common installer failures.
  • Use Case: When modifying Rembric installer code, distribution documentation, or client plugin integration files, use this Skill to ensure all changes adhere to the tested contract and avoid breaking existing user setups.

Quick Start

Use the rembric-tui-installer skill to validate that any proposed changes to Rembric installer scripts, distribution documentation, or client plugin integration files comply with the canonical installer contract and required guardrails before implementation.

Frequently Asked Questions about rembric-tui-installer

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

FAQPage Schema
How do I enforce a single canonical installer workflow for multiple client plugins?▼

A canonical installer workflow uses a delegating orchestrator model where the root installer delegates to per-client scripts, eliminating fragmented logic. This prevents conflicting implementations and ensures consistent operations across all client plugins.

What are the requirements for writing POSIX shell compatible installer scripts?▼

POSIX shell compatible installer scripts require strict adherence to safe token handling and conservative uninstall behavior. Following these guardrails prevents common installer failures and ensures scripts run reliably across different Unix-like environments.

Does the Rembric TUI installer support headless end-to-end validation?▼

The Rembric TUI installer mandates passing a headless end-to-end validation suite before merging any installer-related changes. This required validation ensures all install, setup, upgrade, and uninstall operations function correctly without user interaction.

Why should an installer use a delegating orchestrator model instead of duplicating logic?▼

A delegating orchestrator model prevents duplicated logic by having the root installer delegate to per-client install and uninstall scripts. This approach reduces maintenance overhead and eliminates cross-client bugs that arise from divergent installer implementations.

When do I need to validate changes to distribution documentation and marketplace configuration files?▼

You must validate changes to distribution documentation and marketplace configuration files whenever modifying Rembric agent integrations. The installer contract applies to these files to ensure all changes adhere to the tested guardrails and avoid breaking existing setups.

What is the safest way to handle token management during a server uninstall?▼

Safe token handling during a server uninstall requires conservative uninstall behavior that preserves existing user configurations. This approach prevents accidental data loss and ensures the uninstall process does not break remaining client integrations.

Related Skills

Explore More Software Engineering Skills→
JingyueCongJingyueCong

posix-shell-pro

Review shell scripts for POSIX compliance and portability improvements.

Community
Advanced
nirukk52nirukk52
1

e2e-testing

Automate ScreenGraph end-to-end UI validation with Playwright and .env configuration.

Community
Intermediate
susomejiassusomejias
9

rembric-plugin-development

Enforce spec-aligned Rembric plugin development with OpenSpec-first change management and unified cross-client versioning.

Community
Advanced
austintgriffithaustintgriffith
246

security

Review Solidity smart contracts for vulnerabilities and security best practices.

Community
Advanced