Skip to content
Back to skills

Identify Inventive Contradiction

ASecurity

Identify paired parameters or requirements where improving one worsens another, and distinguish technical from physical contradictions.

  • 499 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 24, 2026
research

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill identify-inventive-contradiction --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Identify Inventive Contradiction?

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

Security grade badge for Identify Inventive Contradiction
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-identify-inventive-contradiction/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-identify-inventive-contradiction)

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: identify-inventive-contradiction
description: "Identify paired parameters or requirements where improving one worsens another, and distinguish technical from physical contradictions."
---

# identify-inventive-contradiction
## Purpose
Identify paired requirements where improving one worsens another, distinguishing technical from physical contradictions.
## Input contract
```yaml
required: [system_requirements, improvement_target, worsening_effect]
optional: [parameter_set, operating_conditions]
constraints: [both sides must refer to the same design decision or parameter]
```
## Procedure
1. State the desired improvement and the resulting worsening effect.
2. Determine whether distinct system states or one parameter must satisfy opposing properties.
3. Classify technical versus physical contradiction and record the implicated parameters.

If improving and worsening parameters are explicit, consider `select-inventive-principle` as the next tactic.

## Output contract
```yaml
produces: [contradiction_statement, contradiction_type, implicated_parameters]
delta_fields: [findings, hypothesis_updates, uncertainties, decisions]
```
## Quality gates
- Improvement and worsening are measurable or operationalized; contradiction type is justified.
## Failure and counterexamples
Reject trade-offs that are merely competing objectives without a causal worsening relation.
## Provenance map
- `triz/contradiction-identification`: resolved.

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…