Overview

Previous Post: #3 — Plugin Trigger Fixes and Marketplace Recommendation System

In this #4 installment, the marketplace installation infrastructure was stabilized across 17 commits and v0.3.0 was released. The introduction of marketplace.json secured the claude plugin add installation path, READMEs were split into English and Korean, and a comprehensive plugin trigger review was completed — unifying CLAUDE_PLUGIN_ROOT, adding preset checks, and implementing installation verification. Marketplace recommendations were also redesigned with a pre-verification approach.

marketplace.json — The Starting Point for Plugin Installation

Problem

Installing a plugin from the Claude Code marketplace requires .claude-plugin/marketplace.json. Without this file, the claude plugin add command cannot be used, forcing users to manually clone the repository.

Solution

marketplace.json was added and the source path was changed to a ./ relative path to enable marketplace installation. This was the starting point for v0.3.0.

graph LR
    A["User"] -->|"claude plugin add"| B["Marketplace"]
    B -->|"marketplace.json reference"| C["plugin.json"]
    C --> D["skills / hooks installation"]
    D --> E["HarnessKit activated"]

README Split — Separating English and Korean

Once listed on the marketplace, English-speaking users will also read the README. Mixing two languages in a single README is inconvenient for both audiences. README.md was rewritten as English-only, and README.ko.md was added as a separate Korean version.

Comprehensive Plugin Trigger Review and Fixes

Spec-Based Approach

Rather than simply fixing bugs, a spec document was written first to classify 5 triggering issues. They were prioritized as CRITICAL, MAJOR, and MINOR, and after a spec review, the fix plan was finalized before implementation began.

graph TD
    A["Write Spec <br/> Identify 5 Issues"] --> B["Spec Review <br/> Fix CRITICAL/MAJOR"]
    B --> C["Create Implementation Plan"]
    C --> D["Unify <br/> CLAUDE_PLUGIN_ROOT"]
    C --> E["Add <br/> Preset Check"]
    C --> F["Add Installation <br/> Verification to Status Skill"]
    D --> G["Migrate All <br/> hooks / skills"]
    E --> G
    F --> G
    G --> H["v0.3.0 Release"]

CLAUDE_PLUGIN_ROOT Unification

A mix of claude plugin path, hardcoded absolute paths, and relative paths was unified under the single CLAUDE_PLUGIN_ROOT environment variable. All hooks including guardrails.sh and pre-commit-test.sh, as well as init and setup skills, were migrated to the same pattern.

# Unified pattern: environment variable + dirname fallback
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cd "$(dirname "$0")/.." && pwd)}"

Preset Check Added

post-edit-lint.sh and post-edit-typecheck.sh were running before the preset was configured, causing errors. A check for the preset file’s existence was added to exit early if it is missing.

Installation Verification Feature

A feature to verify plugin installation status was added to the /harnesskit:status skill. It provides an at-a-glance view of skill file existence, hooks execution permissions, and configuration file integrity.

Marketplace Verified Recommendation System

Real-time marketplace search-based recommendations were replaced with a pre-verified marketplace-recommendations.json.

• The update-recommendations.sh script crawls the marketplace to refresh the list
• /harnesskit:init recommends plugins from this list that match the project
• /harnesskit:insights also references the same list to ensure consistent recommendations

3-Step Sliding Window Tool Sequence

The tool usage pattern analysis in session-end.sh was upgraded. Instead of simple counts, tool sequences are tracked using a 3-step sliding window and recorded in tool:summary format. Detecting repeated patterns improves the precision of automation suggestions.

v0.3.0 Release

After all fixes were applied, the version in plugin.json was bumped to 0.3.0. Since the marketplace plugin cache detects version changes and refreshes, the changes are propagated to installed users as well.

Commit Log

Insights

Listing on a marketplace means transforming “a tool that works in my environment” into “a product that works in anyone’s environment.” Adding a single marketplace.json is simple, but it cascades into path reference unification, environment variable fallbacks, handling unconfigured presets, and installation status verification. Writing and reviewing the spec document before implementation was effective — identifying all 5 issues at once and prioritizing them enabled a systematic migration instead of scattered fixes. The principle of “fix the docs before fixing the code” proved valid once again.