> common-protocol-enforcement
Standards for Red-Team verification and adversarial protocol audit. Use when verifying tasks, performing self-scans, or checking for protocol violations. (triggers: **/*, verify, complete, check, audit, scan, retrospective)
curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/common-protocol-enforcement?format=md"Protocol Enforcement (Red-Team Verification)
Priority: P0 (CRITICAL)
Strict guidelines for adversarial verification. Assume the implementation is "guilty" of protocol slippage until proven innocent.
Red-Team Verification Protocol
Before declaring any task "done" or calling notify_user:
- Adversarial Audit: Search for code patterns that look like "Standard Defaults" (e.g., hardcoded values, generic library calls) where a Project Skill exists.
- Protocol Check: Ensure the "Pre-Write Audit Log" was present for EVERY write tool call.
- Execution Bias Check: Ask: "Did I skip a structural constraint to make the code run faster/pass a test?"
The Post-Write Self-Scan
Immediately after a tool call:
- Scan: Read the diff or the file content.
- Match: Check against
Anti-Patternsin all active skills. - Fix: Re-edit immediately if a violation is detected.
Anti-Patterns
- No "Done" Bias: Functional success != Protocol success.
- No Reliance on Memory: Always retrieval-led (Skill view_file) before write.
- No Skipping Protocols: "Small changes" are where most violations happen.
Execution Bias Detection
Look for:
- Local mocks instead of shared fakes.
- Hardcoded styles instead of design tokens.
- Try-catch blocks without standard error handling.
- Missing
Pre-Write Audit Login thoughts.
> related_skills --same-repo
> typescript-tooling
Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. (triggers: tsconfig.json, .eslintrc.*, jest.config.*, package.json, eslint, prettier, jest, vitest, build, compile, lint)
> typescript-security
Secure coding practices for TypeScript. Use when validating input, handling auth tokens, sanitizing data, or managing secrets and sensitive configuration. (triggers: **/*.ts, **/*.tsx, validate, sanitize, xss, injection, auth, password, secret, token)
> typescript-language
Modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings. (triggers: **/*.ts, **/*.tsx, tsconfig.json, type, interface, generic, enum, union, intersection, readonly, const, namespace)
> typescript-best-practices
Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)