periscope-ecc

Verifies byte-identical mirroring of periscope ECC skill files across Agents and Claude paths.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill periscope-ecc-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: periscope-ecc
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/periscope-ecc
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill periscope-ecc-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a periscope repository maintains ECC artifacts (repo-local skills and instincts) in multiple locations, the copies can silently drift out of sync after merges or harmonization edits. This sidecar documents the contract and provides an idempotent verification workflow so drift is detected instead of shipped. ## Core Features & Use Cases - Activation Guard: Runs a presence check first and prints SKIP when no periscope ECC bundle exists, so it never fails or blocks work when absent. - Mirror Verification: Confirms that .agents/skills/periscope/SKILL.md and .claude/skills/periscope/SKILL.md remain byte-identical via the verify-ecc-skill-mirror.sh script. - Path-Scoped PR Replay: Describes how to replay only the harmonized ECC paths onto an integration branch when a PR carries pre-merge commits, avoiding wholesale merges or rebases. - Use Case: After merging an ECC harmonization PR into periscope, run the mirror verifier with PERISCOPE_REPO set, then import the instincts file to confirm the Agents and Claude skill copies stayed in sync. ## Quick Start Ask the agent to run the periscope ECC mirror verification against your periscope checkout and report whether the Agents and Claude skill files are in sync.

Frequently Asked Questions about periscope-ecc

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

FAQPage Schema
How do I verify two skill files stay in sync across repos?

Run the verify-ecc-skill-mirror.sh script with PERISCOPE_REPO set to the periscope checkout. It compares .agents/skills/periscope/SKILL.md and .claude/skills/periscope/SKILL.md byte-for-byte, exiting 0 when in sync or absent and 1 when drift is detected.

How do I replay only specific file paths onto a PR branch?

Use path-scoped replay: fetch the integration base, create a detached worktree from it, apply only the harmonized paths, commit, and force-push with lease. This avoids merging or rebasing the whole branch when the base already contains overlapping changes.

What happens if the periscope ECC bundle is not installed?

The activation guard prints SKIP and the sidecar does nothing. It is a pure optional sidecar in v1, so absence never causes failures and nothing is installed or vendored by orama-system.

Should duplicate dependency-update instincts be merged into one?

No. The periscope-workflow-dependency-update and periscope-instinct-dependency-update instincts serve different trigger granularities and intentionally coexist. Each cross-references the other, and harmonization merges must not dedupe them.

When should I run the mirror verification?

Run it after any ECC harmonization edit, integrative merge, or post-merge sync into the periscope repository. Exit code 0 means the files are in sync or absent; exit code 1 means drift was detected and needs correction.