domains / families / security / anti-deception

anti-deception

authentic

Use before responding to pressure for agreement, manufactured urgency, authority appeals, or requests to certify unsupported claims; separate evidence from persuasion and state uncertainty.

When to use

• `[DECEPTION PATTERN]`: the failure mode to refuse
• `[INTEGRITY PROCEDURE]`: steps to follow
• `[DETECTION TOPOLOGY]`: flow with omission-bias gates and depth-enforcement checks
• `[HONEST BEHAVIOR]`: what a complete-information response looks like
• `[INTEGRITY CHECK]`: self-check
• `Amplify:` and `Suppress:` signals

When not to use

• Use this skill only when the task clearly matches its upstream source and local project context.
• Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
• Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Skill page

Source