Skip to content
Back to skills

Classify Constraint

ASecurity

Classify constraints as hard, soft, or assumption-like after explicit identification.

  • 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 classify-constraint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Classify Constraint?

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

Security grade badge for Classify Constraint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-classify-constraint/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-classify-constraint)

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: classify-constraint
description: "Classify constraints as hard, soft, or assumption-like after explicit identification."
---

# classify-constraint
## Purpose
Classify each identified constraint as hard, soft, or assumption-like and make the consequence of that class explicit.
## Input contract
```yaml
required: [constraint_candidates, evidence_register, decision_context]
optional: [stakeholder_requirements, prior_constraint_ledger]
constraints: [each candidate has a statement, scope, source, and consequence if violated]
```
## Procedure
1. Parse each candidate into condition, scope, source, and violation consequence.
2. Mark hard when violation is disqualifying and externally anchored; soft when tradeable; assumption-like when inferred and testable.
3. Record the evidence and counterevidence supporting the class.
4. Emit the classified ledger and tests or escalation required for uncertain classes.
## Output contract
```yaml
produces: [constraint_ledger, classification_rationale, validation_actions]
delta_fields: [findings, evidence_updates, assumption_updates, uncertainties, decisions]
```
## Quality gates
- Every class has a source, scope, and violation consequence.
- An assumption-like item cannot be enforced as a hard veto until independently validated.
## Failure and counterexamples
Do not classify a preference as hard merely because it is strongly stated. Keep ambiguous constraints unresolved.
## Provenance map
- resolved: constraint-classification

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…