auxiliary-helper-pattern

Defines a read-only helper pattern for independently auditing work implemented by a primary account.

Updated Sep 16, 2026
One-click install
npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill auxiliary-helper-pattern-military-veteran-team-lpt-realty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auxiliary-helper-pattern
Source: https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills/tree/main/skills/auxiliary-helper-pattern
Command: npx skills add https://github.com/Military-Veteran-Team-LPT-Realty/mvt-manus-public-skills --skill auxiliary-helper-pattern-military-veteran-team-lpt-realty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When one account both implements a change and audits its own work, there is no independent verification before major decisions. This Skill provides a structured pattern for delegating a read-only audit to an auxiliary helper account, separating implementation from verification. ## Core Features & Use Cases - Helper Scope Definition: Provides a template for narrowly scoping the helper's permitted and prohibited actions, including time boxes and output formats. - Structured Reporting: Defines a findings-only report format with evidence, unverifiable items, and an explicit no-changes-made statement. - Reconciliation Workflow: Describes how to compare helper and primary account findings, resolve discrepancies, and escalate to a human when needed. - Use Case: After a primary account remediates a repository, an auxiliary helper performs a read-only audit of the same system, and an auditor reconciles both reports into a decision packet for human approval. ## Quick Start Use the auxiliary helper pattern to define a read-only audit scope for verifying the changes my primary account just implemented.

Frequently Asked Questions about auxiliary-helper-pattern

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

FAQPage Schema
How do I independently audit work done by the same account that implemented it?

Use an auxiliary helper account with a read-only scope to audit the primary account's work. The helper reports findings only, and a separate auditor or human reconciles both reports before any major decision.

When should I use an auxiliary helper for verification?

Use a helper when independent verification is required before production, when the task mixes implementation and audit in one account, or before irreversible decisions. Skip it for purely read-only or low-stakes tasks.

What should a read-only audit helper be allowed to do?

The helper may read files, query APIs, and run non-modifying commands. It must not commit, push, merge, deploy, or change credentials or settings, and its scope should include a time box and defined output format.

How do I resolve disagreements between a helper audit and the implementer?

Compare findings, and give precedence to the helper on the primary account's own work since it is independent. If both have equal visibility and still disagree, escalate the discrepancy to the human decision-maker.

What are the limitations of the auxiliary helper pattern?

The helper only reports findings and cannot implement fixes or make decisions. It adds coordination overhead, so it is impractical under tight time pressure or when independent verification adds no value.