tianji-pavilion

Evaluates external open-source resources through a 5-phase integration protocol with mechanized hooks.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill tianji-pavilion-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tianji-pavilion
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/tianji-pavilion
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill tianji-pavilion-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires better-sqlite3, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? It prevents impulsive or unverified adoption of external open-source resources (skills, hooks, rules, MCP servers, methodologies) into a Claude Code project by enforcing a structured evaluation protocol with baselines, benchmarks, and recorded decisions. ## Core Features & Use Cases - 5-Phase Protocol: Phase 0 Baseline (sovereignty questions + latent-capability audit), Phase 1-2 Differential Benchmarking (A/B/C/D quadrant + 8-item context match), Phase 3 Essence Extraction (MVE distillation with adaptation-depth scoring), Phase 4 Grafting (timeboxed git worktree pilot with kill switch), Phase 5 Validation (7-day observation + ADR). - Mechanized Enforcement: 8 hooks block forbidden patterns such as skipping baselines, concurrent pilots, permanent pilots, cooldown bypass, and scope creep, writing structured records to baseline_snapshots and external_evaluations SQLite tables. - Use Case: When a user says "I saw this GitHub tool, should we integrate it?", the skill runs a latent-capability audit, classifies the trigger, quantifies a baseline, and either rejects the impulse or guides a timeboxed pilot with a binary integrate-or-rollback decision. ## Quick Start Ask the AI to evaluate whether a specific external tool or workflow should be integrated into the project using the tianji-pavilion protocol.

Frequently Asked Questions about tianji-pavilion

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

FAQPage Schema
How do I evaluate whether to adopt an external open-source tool?

Run the 5-phase protocol: establish a Phase 0 baseline with four sovereignty questions and a latent-capability audit, benchmark against your existing module in an A/B/C/D quadrant, distill only the essential elements, pilot in an isolated git worktree, then validate over a 7-day observation period.

What is a latent capability audit before integrating new tools?

It is a Q4 check that runs audit-capability-reachability.cjs against your existing MCP tools, database schema, and hook layers. If existing capabilities cover at least 70% of the pain point, external integration is rejected in favor of activating what you already built.

When should I not use this evaluation protocol?

Do not use it for pure library version bumps, bug-fix patches, CVE security patches, documentation translation, or internal refactoring with no external influence. Security and compliance fixes bypass the 30% gain threshold and follow a binary must-integrate decision.

Why does git worktree creation get blocked during a pilot?

PreToolUse hooks block worktree creation when no baseline_snapshots row exists, another pilot is already active, the Q4 audit is missing or stale, or an impulse trigger is still within its 3-day cold-storage period. Complete the missing phase deliverable to proceed.

What happens if a pilot exceeds its timebox?

The pilot-timebox-monitor hook flags overdue pilots at session start. Permanent pilot states are forbidden; at timebox expiry you must make a binary decision to integrate with SSoT updates or roll back while keeping the ADR.