Skip to content
Back to skills

Adjust Abstraction Scope

ASecurity

Move a scientific object up/down in abstraction or narrow/broaden selected scope dimensions (population, mechanism, context, outcome, timeframe, system boundary) until the representation has useful explanatory and experimental leverage.

  • 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 adjust-abstraction-scope --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Adjust Abstraction Scope?

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

Security grade badge for Adjust Abstraction Scope
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/yogsoth-ai-adjust-abstraction-scope/badge)](https://www.skillsdirectory.com/skills/yogsoth-ai-adjust-abstraction-scope)

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: adjust-abstraction-scope
description: "Move a scientific object up/down in abstraction or narrow/broaden selected scope dimensions (population, mechanism, context, outcome, timeframe, system boundary) until the representation has useful explanatory and experimental leverage."
---

# adjust-abstraction-scope

## Purpose
Move a scientific object up or down in abstraction, or narrow/broaden scope dimensions, until explanatory and experimental leverage improve.

## Input contract
```yaml
required: [research_object, current_scope, leverage_failure]
optional: [candidate_levels, context_constraints, target_use]
constraints: [retain object identity; change representation or declared scope explicitly]
```

## Procedure
1. Record object, current level, and scope dimensions (population, mechanism, context, outcome, timeframe, boundary).
2. Generate at least one upward and one downward abstraction candidate when leverage is unclear.
3. For each candidate, state what is gained, lost, and newly testable.
4. Select the narrowest or broadest level that supports the caller's stated use and record rationale.

## Output contract
```yaml
produces: [scoped_representations, selected_scope, leverage_rationale]
delta_fields: [findings, decisions, uncertainties]
```

## Quality gates
- Object identity is invariant across representations.
- Every changed dimension is named with before/after values.
- Selected scope has an explicit explanatory or experimental leverage claim.

## Parameterization
Caller supplies object schema, allowed abstraction dimensions, admissible scope bounds, target use, and selection rule.

## Failure and counterexamples
Reject a level that changes the object while appearing to change only scope; reject scope changes with no stated leverage test.

## Provenance map
- resolved: abstraction-laddering
- resolved: scope-assessment
- resolved: question-reformulation
- resolved: scope-calibration
- intermediate: Pass8/shift-abstraction-level
- intermediate: Pass8/adjust-question-scope

## Preserved source criteria ledger

| source | criterion |
|---|---|
| scope-assessment | Input must contain at least 1 fully stated research question. |
| scope-assessment | Too broad requires a book/multiple papers; appropriate is answerable by one paper; too narrow is self-evident or lacks contribution. |

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…