Skip to content
Back to skills

Resurrection Advocacy

ASecurity

Argue for rejected candidates using Devil's Advocacy, Dialectical Inquiry, and Adversarial Collaboration to ensure elimination was justified.

  • 417 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
researchexpress

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill resurrection-advocacy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Resurrection Advocacy?

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

Security grade badge for Resurrection Advocacy
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-resurrection-advocacy/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-resurrection-advocacy)

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: resurrection-advocacy
description: Argue for rejected candidates using Devil's Advocacy, Dialectical Inquiry, and Adversarial Collaboration to ensure elimination was justified.
used-by: steel-manning
---

# Resurrection Advocacy

**Purpose:** Construct the strongest possible case for candidates that were eliminated during convergence, ensuring rejection was based on genuine weakness rather than framing effects, anchoring bias, or insufficient consideration.

**When to use:**
- After convergence has produced a winner and eliminated alternatives
- When stakeholders express lingering doubt about rejected options
- When the elimination margin was narrow
- When rejected candidates had unique strengths not present in the winner

## Budget

| Metric | Minimum |
|--------|---------|
| Candidates resurrected | >= 2 (top rejected) |
| Advocacy depth | Full case construction per candidate |
| Debate rounds | >= 2 per resurrected candidate |

## State Ledger

```yaml
resurrected_candidates: []
advocacy_cases: {}
debate_outcomes: {}
final_dispositions: {}  # REAFFIRM_REJECTION | REVIVE | MERGE_STRENGTHS
```

## Available Tactics

| Tactic | When to Deploy |
|--------|---------------|
| adversarial-debate-protocol | Default — construct advocate, attack, judge cycle |
| multi-perspective-attack | When candidate has multi-stakeholder implications |

## Available SOPs

- advocate-construction — build strongest case for rejected candidate
- critic-attack — attack the advocacy case
- judge-verdict — render final disposition

## Execution Guidance

1. Select top 2-3 rejected candidates by elimination margin or unique strength
2. For each candidate, deploy adversarial-debate-protocol
3. If judge verdict is REVISE, escalate to campaign orchestrator
4. Record all dispositions in Challenge Ledger

## Output Format

```yaml
strategy: resurrection-advocacy
candidates_tested:
  - candidate: <name>
    advocate_strength: <1-10>
    verdict: REAFFIRM_REJECTION | REVIVE | MERGE_STRENGTHS
    key_argument: <strongest point>
    conditions: <if any>
surviving_concerns: []
recommendation: <action>
```

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.