taw-security

Forwards legacy taw-security audit requests to the /taw workflow.

32|13|Updated Apr 21, 2026

Search Tags:#workflow #security #cli #audit #backward-compatibility #shim #taw

Ready to run

npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-security

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: taw-security
Source: https://github.com/nghiahsgs/taw-kit/tree/main/skills/taw-security
Command: npx skills add https://github.com/nghiahsgs/taw-kit --skill taw-security

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The taw-security shim provides backward compatibility by forwarding security audit requests to the main /taw workflow, allowing older integrations to continue functioning without changes.

Core Features & Use Cases

Forward to /taw audit: seamlessly route legacy taw-security invocations to the primary audit flow.
Sunset guidance: clearly states deprecation and encourages migration to /taw audit.
Compatibility maintenance: preserves behavior across taw-kit versions for security checks.

Quick Start

Invoke /taw audit using the legacy taw-security workflow to trigger the security check.

Frequently Asked Questions about taw-security

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

FAQPage Schema

How do I maintain backward compatibility for security audit routing in my CLI workflow?▼

Maintaining backward compatibility for security audit routing involves using a shim that forwards legacy CLI invocations to the main workflow, preserving consistent behavior across versions without changing older integrations.

What is a shim for forwarding legacy security audit requests?▼

A security audit shim is a compatibility layer that intercepts legacy workflow invocations and forwards them to the primary audit path, allowing older integrations to trigger security checks seamlessly without modification.

How do I route legacy security audit invocations to the primary workflow?▼

Route legacy security audit invocations by invoking the legacy workflow, which automatically forwards the request to the primary audit flow to ensure the security check is executed consistently across updated toolkits.

When should I migrate from a deprecated security workflow to the main audit path?▼

Migrate from a deprecated security workflow to the main audit path immediately, as the compatibility shim provides a clear sunset plan for deprecated paths and encourages migration to ensure long-term stability.

Do I need to update my existing integrations to run a security audit check?▼

No, you do not need to update existing integrations to run a security audit check, because the backward-compatible shim automatically routes legacy requests to the main workflow for consistent execution.