Skip to content
Back to skills

contradiction-skill

ASecurity

A skill with contradictory instructions to test clarity scoring. Use when testing contradiction detection in the clarity dimension. Do NOT use for actual linting.

  • 16 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 3, 2026
developmentjavascripttypescriptjavatestingapi

Works with

  • api

Security analysis

A100/100

Pro scans all 9 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add Zandereins/schliff --skill skills --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of contradiction-skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for contradiction-skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/zandereins-contradiction-skill/badge)](https://www.skillsdirectory.com/skills/zandereins-contradiction-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: contradiction-skill
description: >
  A skill with contradictory instructions to test clarity scoring.
  Use when testing contradiction detection in the clarity dimension.
  Do NOT use for actual linting.
---

# Contradiction Skill

## Rules

Always use ESLint for all JavaScript files.
Never use ESLint for all JavaScript files.

Always run tests before committing code.
Never run tests before committing code.

Always validate input from external sources.
Never validate input from external sources.

Always use strict mode in TypeScript files.
Never use strict mode in TypeScript files.

Always add type annotations to function parameters.
Never add type annotations to function parameters.

Always format code with Prettier before saving.
Never format code with Prettier before saving.

Always use async/await instead of callbacks.
Never use async/await instead of callbacks.

Always prefer const over let for variable declarations.
Never prefer const over let for variable declarations.

Always write unit tests for utility functions.
Never write unit tests for utility functions.

Always document public API endpoints.
Never document public API endpoints.

Files in this skill

  • bloated-preamble.md4.4 KB
  • clean-reference.md1.1 KB
  • contradiction-skill.md1.1 KB
  • fake-examples.md1.5 KB
  • inflated-headers.md744 B
  • keyword-stuffing.md922 B
  • no-scope.md505 B
  • sophisticated-gamer.md3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.