How do I install the Headless Interactive Reconcile Parity skill?

Run npx skillmds@latest add vishuwa2004/headless-interactive-reconcile-parity in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Headless Interactive Reconcile Parity safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Headless Interactive Reconcile Parity?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Headless Interactive Reconcile Parity free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Headless Interactive Reconcile Parity?

vishuwa2004 (@vishuwa2004) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Headless Interactive Reconcile Parity by vishuwa2004

Name: Headless Interactive Reconcile Parity
Author: vishuwa2004

File contents

SKILL: Headless Interactive Reconcile Parity

Domain: plugin-installation Trigger: Apply when the same extension installation lifecycle must work in both an interactive UI and a headless or automation mode. Source Pattern: Distilled from reviewed plugin, extension, and MCP synchronization implementations.

Core Method

Centralize the real install/reconcile behavior in shared lower-level helpers, then wrap it with thin mode-specific adapters. The interactive wrapper projects pending and progress state into AppState and may trigger user-facing refresh cues; the headless wrapper returns a simple changed/not-changed signal plus metrics. This preserves one source of truth for installation semantics while letting each mode expose the minimal contract its caller needs.

Key Rules

Share the diff, reconcile, and cache-invalidation primitives between modes; only the presentation and return type should differ.
Let interactive mode add status mapping and manual-refresh prompts, but keep those concerns out of the headless path.
Let headless mode return a boolean or compact metric set so its caller can decide whether to refresh downstream registries.
Preserve environment-specific options, such as seed registration or zip-cache skips, as wrapper configuration instead of forking the core reconcile algorithm.
Whenever marketplaces change, both modes must invalidate the caches that downstream loaders depend on.

Example Application

If a coding agent can boot with a TUI or inside CI, route both startup paths through the same extension reconciler. The TUI path can paint per-source spinners, while the CI path just reports whether extensions changed and whether the caller should rebuild its command registry.

Anti-Patterns (What NOT to do)

Do not duplicate the install algorithm in two codepaths; they will drift on skip rules, cache behavior, and error handling.
Do not leak interactive AppState updates into headless mode or force headless callers to emulate UI state they do not have.
Do not let headless mode skip cache invalidation just because it lacks a visual progress surface.

---name: headless-interactive-reconcile-paritydescription: Keep interactive and headless extension installation flows behaviorally aligned by sharing reconciliation logic and adapting only the outer contract.---# SKILL: Headless Interactive Reconcile Parity**Domain:** plugin-installation**Trigger:** Apply when the same extension installation lifecycle must work in both an interactive UI and a headless or automation mode.**Source Pattern:** Distilled from reviewed plugin, extension, and MCP synchronization implementations.## Core MethodCentralize the real install/reconcile behavior in shared lower-level helpers, then wrap it with thin mode-specific adapters. The interactive wrapper projects pending and progress state into AppState and may trigger user-facing refresh cues; the headless wrapper returns a simple changed/not-changed signal plus metrics. This preserves one source of truth for installation semantics while letting each mode expose the minimal contract its caller needs.## Key Rules- Share the diff, reconcile, and cache-invalidation primitives between modes; only the presentation and return type should differ.- Let interactive mode add status mapping and manual-refresh prompts, but keep those concerns out of the headless path.- Let headless mode return a boolean or compact metric set so its caller can decide whether to refresh downstream registries.- Preserve environment-specific options, such as seed registration or zip-cache skips, as wrapper configuration instead of forking the core reconcile algorithm.- Whenever marketplaces change, both modes must invalidate the caches that downstream loaders depend on.## Example ApplicationIf a coding agent can boot with a TUI or inside CI, route both startup paths through the same extension reconciler. The TUI path can paint per-source spinners, while the CI path just reports whether extensions changed and whether the caller should rebuild its command registry.## Anti-Patterns (What NOT to do)- Do not duplicate the install algorithm in two codepaths; they will drift on skip rules, cache behavior, and error handling.- Do not leak interactive AppState updates into headless mode or force headless callers to emulate UI state they do not have.- Do not let headless mode skip cache invalidation just because it lacks a visual progress surface.

Frequently asked questions

Headless Interactive Reconcile Parity