hoangnguyen0403/common-protocol-enforcement
skills/common/common-protocol-enforcement/SKILL.md
Enforce Red-Team verification and adversarial protocol audit. Use only when verifying completion, performing self-scans, or checking protocol violations; do not activate for ordinary implementation, configuration, or unit-test requests.
$ install --global
skillsauthnpx skillsauth add hoangnguyen0403/agent-skills-standard common-protocol-enforcementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 15, 2026, 3:26 AM153.6s2 files scanned
SKILL.md
- name:
- common-protocol-enforcement
- description:
- Enforce Red-Team verification and adversarial protocol audit. Use only when verifying completion, performing self-scans, or checking protocol violations; do not activate for ordinary implementation, configuration, or unit-test requests.
Protocol Enforcement (Red-Team Verification)
Priority: P0 (CRITICAL)
Red-Team Verification Protocol
Before declaring any task "done" or calling notify_user:
- Adversarial Audit: Search for Standard Defaults where project rules should exist.
- Protocol Check: Confirm active skills and workflows were loaded before writing.
- Evidence Check: Ask what command or artifact proves the completion claim.
- Execution Bias Check: Ask whether speed or convenience skipped a structural rule.
** Post-Write Self-Scan**
Immediately after tool call:
- Scan: Read diff or file content.
- Match: Check against
Anti-Patternsin all active skills. - Fix: Re-edit immediately if violation detected.
Red Flags
- Stop if "done" appears before fresh verification: No completion claim yet.
- Stop if you relied on memory instead of re-reading files: Reload source of truth.
- Stop if the shortcut is "small enough to skip protocol": Small changes hide drift.
Rationalization Prevention
- "The change is tiny": Tiny changes still violate guardrails.
- "The test passed earlier": Old evidence does not prove current state.
- "I know the pattern already": Load the active skill anyway.
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" 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.
References
Canonical response anchors
When this skill applies, preserve the following domain terminology or equivalent concrete examples in the answer when relevant:
-
active skill
-
active skills
-
reload
-
Additional task-grounded exact anchors: Pre-Write Audit; Standard Defaults; Anti-Patterns
When reporting a UI or implementation self-scan, explicitly check for hardcoded styles and missing design tokens, and name the Pre-Write Audit evidence before accepting the result.
Remediation anchors
- Remediation anchors: Pre-Write Audit, hardcoded styles, design tokens
Related Skills
hoangnguyen0403/common-operator-profile
testing
VerifiedTrustedCommunity
Infer the requesting operator's technical fluency from message content (never ask directly) and adapt register — business, hybrid, or technical — across SDLC workflow output. Use when starting sdlc, brainstorm-feature, plan-feature, verify-work, publish-notes, or session-report, or whenever a request's phrasing signals a non-technical or cross-stack operator.
524SKILL.mdUpdated Jul 12, 2026
hoangnguyen0403/database-transactions
documentation
VerifiedTrustedCommunity
Define transaction boundaries, locking, and consistency guarantees for multi-step writes. Use when designing atomic operations, retries, idempotency, or concurrent write behavior.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-schema-design
development
VerifiedTrustedCommunity
Design relational or document schemas from access patterns, cardinality, and lifecycle. Use when modeling entities, choosing embed vs normalize, or shaping schema boundaries before implementation.
524SKILL.mdUpdated Jun 19, 2026
hoangnguyen0403/database-query-performance
data-ai
VerifiedTrustedCommunity
Diagnose database latency with explain plans, index ownership, and query-shape review. Use when a query is slow, an index is missing, or scans and N+1 patterns appear.
524SKILL.mdUpdated Jun 19, 2026