tbm-prompt-auditor-pass

Route legacy TBM-prefixed prompt auditor invocations to the global skill.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/blucsigma05/tbm-apps-script --skill tbm-prompt-auditor-pass
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tbm-prompt-auditor-pass
Source: https://github.com/blucsigma05/tbm-apps-script/tree/main/.codex/skills/tbm-prompt-auditor-pass
Command: npx skills add https://github.com/blucsigma05/tbm-apps-script --skill tbm-prompt-auditor-pass

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves legacy invocations of the old TBM-prefixed skill name so they still run correctly, while directing users toward the preferred cross-project skill name.

Core Features & Use Cases

  • Legacy name compatibility: Supports old $tbm-prompt-auditor-pass calls without introducing new behavior.
  • Cross-project preference guidance: Advises using prompt-auditor-pass when available for new or MLS work.
  • TBM-specific context option: Points to historical TBM wording when TBM-specific rubric or phrasing is required, plus guidance for three-pass vs folded vs audit-only modes.

Quick Start

Use the tbm-prompt-auditor-pass skill only when your environment explicitly invokes the legacy TBM skill name, otherwise ask for the global prompt-auditor-pass.

Frequently Asked Questions about tbm-prompt-auditor-pass

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

FAQPage Schema
How do I maintain legacy system prompt invocations without breaking older tooling?▼

Legacy system prompt invocations are maintained by using a compatibility wrapper that reroutes old TBM-prefixed calls to the current prompt auditing logic without introducing new behavior.

When should I use a legacy prompt auditing alias instead of the global prompt auditor?▼

Use the legacy prompt auditing alias only when your environment explicitly invokes the old TBM-prefixed skill name, otherwise you should default to the global prompt-auditor-pass for new work.

Does the legacy TBM prompt auditor add new behavior to my evaluation rubric prompting?▼

No, the legacy TBM prompt auditor does not add new behavior to evaluation rubric prompting, as it relies strictly on existing historical wording to ensure backward compatibility.

Can I use TBM prompt hardening for new cross-project system prompt reuse tasks?▼

For new cross-project system prompt reuse tasks, you should prefer the global prompt-auditor-pass instead of TBM prompt hardening, reserving the TBM alias solely for legacy compatibility.

What is the difference between three-pass, folded, and audit-only modes in TBM prompt auditing?▼

TBM prompt auditing points to historical wording to differentiate three-pass, folded, and audit-only modes, ensuring the correct evaluation rubric phrasing is applied for your specific context.

Why does my system prompt reuse fail when calling the old TBM-prefixed skill name?▼

System prompt reuse fails when calling the old TBM-prefixed name if the compatibility wrapper is not used, as the wrapper is required to safely map legacy invocations to the current auditor.