Skip to content
Back to skills

Generate Candidate Directions

ASecurity

Generate diverse candidate research fields/subfields consistent with current context while permitting deliberate boundary-crossing.

  • 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 generate-candidate-directions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Generate Candidate Directions?

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

Security grade badge for Generate Candidate Directions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-generate-candidate-directions/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-generate-candidate-directions)

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: generate-candidate-directions
description: "Generate diverse candidate research fields/subfields consistent with current context while permitting deliberate boundary-crossing."
---

# generate-candidate-directions

## Purpose

Generate diverse candidate research fields or subfields consistent with context while permitting deliberate boundary crossing.

## Input contract

```yaml
required: [research_intent, scope_anchor]
optional: [seed_evidence, actor_profile, constraints, neighboring_domains]
constraints: [each candidate must state fit, boundary crossing, and evidence needs]
```

## Procedure

1. Extract the problem mechanism, outcome, and scope anchor.
2. Generate candidates within the anchor and from adjacent domains.
3. Record the transfer or boundary-crossing rationale for each candidate.
4. Remove duplicates while preserving materially different mechanisms.

If candidate fields are diverse enough for comparative characterization, consider `synthesize-field-panorama` as the next tactic.

## Output contract

```yaml
produces: [candidate_directions, fit_rationales, boundary_crossings, evidence_questions]
delta_fields: [findings, hypothesis_updates, uncertainties, open_questions, recommended_jumps]
```

## Quality gates

- Candidates are distinct by mechanism or evidence opportunity.
- Speculative candidates are labeled as such.

## Failure and counterexamples

Do not equate popularity with fit or generate a list of fields without a boundary rationale.

## Provenance map

- `resolved: generate-candidate-fields`

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…