drift

Compare skill and agent definition files for structural differences and shared patterns.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/supertyrelle/pelley --skill drift-supertyrelle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: drift
Source: https://github.com/supertyrelle/pelley/tree/main/skills/drift
Command: npx skills add https://github.com/supertyrelle/pelley --skill drift-supertyrelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drift helps you spot when related skill and agent definitions are starting to look inconsistent, so you can catch duplication, missing patterns, and structural differences early.

Core Features & Use Cases

  • Cross-file comparison: Compare multiple skill or agent files to find shared sections, unique sections, and ordering differences.
  • Consistency review: Check frontmatter fields and section structure for patterns that should be aligned across similar definitions.
  • Change propagation: Use git history to identify recent edits that may need to be cross-pollinated into sibling files.
  • Use case: After a major skill edit, run Drift to see whether the same improvements should be applied to related skills or agents.

Quick Start

Use the drift skill to compare the relevant skill or agent definition files and report structural differences and shared patterns.

Frequently Asked Questions about drift

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

FAQPage Schema
How do I detect definition drift across multiple skill and agent files?

Detect definition drift by comparing section headers and frontmatter fields across related skill and agent files to identify shared structures, missing patterns, and divergence timing. This consistency check catches structural differences and duplication before they spread.

What is cross-pollination review for skill and agent definition files?

Cross-pollination review is a consistency check that identifies whether recent edits or improvements made to one skill or agent definition should be propagated into sibling files. It compares section structures and frontmatter to find shared and unique patterns across related definitions.

How do I check frontmatter consistency across related definition files?

Check frontmatter consistency by inspecting and comparing frontmatter fields across multiple skill or agent definition files. This reveals patterns that should be aligned across similar definitions and highlights missing fields or structural divergences between related files.

Can I use git history to find when definition files started diverging?

Yes, you can use optional git-history review to identify divergence timing and recent edits that may need to be cross-pollinated into sibling files. This retro analysis helps pinpoint exactly when related skill or agent definitions began drifting apart structurally.

What's the best way to compare section structure across multiple skill definitions?

The best way to compare section structure is by applying section-header comparison across multiple skill or agent files to find shared sections, unique sections, and ordering differences. This cross-file comparison reveals missing patterns and structural inconsistencies directly.

Do I need any dependencies to run drift analysis on my definition files?

No dependencies are required to run drift analysis on your definition files. The consistency checks, frontmatter inspection, and optional git-history review operate directly on your skill and agent definition files without any external packages or components.