/**
 * Auto-generated trigger probes for `vigiles audit`'s model trigger tier.
 *
 * The trigger-rate eval needs a per-skill prompt set (does the description FIRE?
 * — recall + precision). Authoring that set by hand was the friction that made
 * the eval un-wowable. The trigger tier removes it: derive a small, DIVERSE probe
 * set from each skill's own description — zero setup. `--prompts=<file>` still
 * overrides for a rigorous, curated benchmark.
 *
 * Deterministic by design (no model needed to AUTHOR the probes — the model is
 * spent RUNNING them). The trick that clears the diversity gate: extract a SHORT
 * topic from the description (so the shared text stays small relative to the
 * frame) and wrap it in lexically-distant frames. Measured min pairwise NCD
 * ~0.27 across short/long descriptions — comfortably above {@link AUTO_MIN_DISTANCE}.
 */
import type { TriggerPromptSet } from "./scan-behavioral.js";
export interface PromptSkill {
    readonly name: string;
    readonly description: string;
}
/** How many recall probes we generate per skill (each a distinct frame). */
export declare const AUTO_RECALL_COUNT = 6;
/**
 * The diversity floor for AUTO probes — relaxed from the default 0.3 because a
 * templated-but-varied machine probe legitimately shares a topic phrase (the
 * generator's measured min is ~0.27). Still well above 0 → genuine copy-paste
 * is caught; the gate's "vary the phrasing" advice is for hand-authored sets.
 */
export declare const AUTO_MIN_DISTANCE = 0.2;
/**
 * Extract a short, action-shaped topic from a description: drop boilerplate
 * lead-ins ("A skill that…", "Use this skill to…"), take the first clause, cap
 * at 8 words. Capping is load-bearing — a long verbatim topic makes the frames
 * too similar (NCD collapses below the gate).
 */
export declare function topicOf(description: string): string;
/** Recall probes for one skill: distinct frames around its extracted topic. */
export declare function recallPrompts(description: string, count?: number): string[];
/**
 * Build a {@link TriggerPromptSet} from skill descriptions — zero-setup trigger
 * probes. Each skill gets `recallPrompts` derived from its description plus the
 * shared irrelevant bank for precision. Skills with an empty description are
 * skipped (nothing to derive a topic from).
 */
export declare function autoTriggerPrompts(skills: readonly PromptSkill[], count?: number): TriggerPromptSet;
//# sourceMappingURL=audit-prompts.d.ts.map