compare

Compare trigger phrase generation across haiku, sonnet, and opus model sizes.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/brewpirate/acme-frontier-ai --skill compare-brewpirate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compare
Source: https://github.com/brewpirate/acme-frontier-ai/tree/main/catalog/projects/total-recall/skills/compare
Command: npx skills add https://github.com/brewpirate/acme-frontier-ai --skill compare-brewpirate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you compare how different model sizes generate trigger phrases from the same input, making it easier to spot agreement, divergence, and model-specific wording.

Core Features & Use Cases

  • Cross-model analysis: Runs the same comparison task across haiku, sonnet, and opus study agents.
  • File-based research: Supports single files or small batches of repository files for controlled experiments.
  • Result logging: Stores comparison output in a structured JSON file for later inspection and manual review.

Quick Start

Ask the compare skill to analyze the files you want compared and return a cross-model results table.

Frequently Asked Questions about compare

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

FAQPage Schema
How do I compare trigger phrase generation across different LLM model sizes?

To compare trigger phrase generation across LLM model sizes, you run a controlled experiment on a source file to study agreement, divergence, and shared terms across haiku, sonnet, and opus models. The Skill spawns study agents and logs cross-model results in a structured JSON file for manual analysis.

What is cross-model divergence analysis and how does it work for source files?

Cross-model divergence analysis identifies how different model sizes generate varying trigger phrases from the same source file. It works by spawning multiple study agents to process the file, applying confidence scoring, and logging comparative results into structured JSON output for review.

Can I use repository files for controlled LLM comparison experiments?

Yes, you can use a single file or a small batch of repository files for controlled LLM comparison experiments. This allows you to study model-specific wording and agreement across haiku, sonnet, and opus while logging relative-path results into a structured JSON file.

How do I log LLM agent workflow results to JSON for manual analysis?

You log LLM agent workflow results to JSON for manual analysis by running a cross-model comparison task on your source files. The process requires agent spawning and automatically stores trigger phrase generation outputs, confidence scores, and relative-path results in a structured JSON file.

What are the limitations of running cross-model comparison on repository files?

The limitation of running cross-model comparison is that it is designed for controlled experiments on a single file or a small set of repository files. It requires agent spawning to study haiku, sonnet, and opus divergence, making it unsuitable for processing large-scale codebases or unstructured data batches.