list

Display stored trigger phrases from .claude/triggers.json in a structured table.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect and review stored trigger phrases without manually digging through the backing JSON file, making it easier to audit what has been captured and how confidently it was identified.

Core Features & Use Cases

  • Full Inventory View: Displays every stored trigger phrase in a structured table for quick review.
  • Path-Based Filtering: Narrows results to entries whose file path matches a provided pattern, which is useful when focusing on one area of a project.
  • Quality Review: Highlights low-confidence entries and summarizes cross-model terms so you can spot uncertain or inconsistent trigger labels.
  • Use Case: A maintainer checks all triggers after a scan, filters to a specific source directory, and reviews weak matches before promoting them into a workflow.

Quick Start

Use the list skill to show the stored trigger phrases, optionally filtering the results to a specific file path pattern.

Frequently Asked Questions about list

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

FAQPage Schema
How do I review stored trigger phrases from a JSON file without manually digging through the code?

You can review stored trigger phrases by displaying them in a structured table, which parses legacy and per-model entries, confidence values, and scan dates from the backing JSON file for quick auditing.

Can I filter trigger phrase audits to focus on a specific source directory?

Yes, you can filter trigger phrase audits using path-based patterns, narrowing the structured table results to entries whose file path matches a specific project area for targeted review.

How do I spot low-confidence trigger labels during a prompt-knowledge review?

To spot low-confidence trigger labels during a prompt-knowledge review, inspect the structured table output which highlights uncertain entries and summarizes cross-model terms for accurate reporting.

What is the best way to compare cross-model terms for inconsistent trigger labels?

The best way to compare cross-model terms is by generating a structured inventory view that summarizes optional crossModelTerms alongside confidence values, helping you spot inconsistent trigger labels.

Does this trigger reporting tool work with legacy JSON entries and per-model data?

Yes, the trigger reporting tool works with legacy JSON entries and per-model data, requiring parsing of both formats alongside confidence values and scan dates to display an accurate structured table.