adjust-abstraction-scope
Skill504 starsChanged 49 days agoApache-2.0View on GitHub
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.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- yogsoth-ai/de-anthropocentric-research-engineword for word, first seen Sep 25, 2026
Other versions1 project uses a version of this.
Word for word · 1
- yogsoth-ai/de-anthropocentric-research-engine★ 505100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository270 other files it gives its agents.
- abstract-structureSkill
- adjudicate-exchangeSkill
- adversarial-deliberationSkill
- aggregate-rankingSkill
- analogical-discoverySkill
- analyze-constraints-readinessSkill
- analyze-experiment-resultsSkill
- analyze-future-scenariosSkill
- analyze-heterogeneitySkill
- analyze-interventionSkill
- analyze-leaderboard-dynamicsSkill
- analyze-patent-citation-networkSkill
- analyze-scaling-regimeSkill
- analyze-temporal-trajectorySkill
- apply-perturbationSkill
- apply-question-frameworkSkill
- apply-separation-principleSkill
- apply-stage-gateSkill
- apply-veto-filterSkill
- appreciative-reframeSkill
- assess-construct-validitySkill
- assess-evidence-saturationSkill
- assess-goal-feasibilitySkill
- assess-patent-claim-scopeSkill
- assess-patent-legal-statusSkill
- assess-prior-art-and-claimsSkill
- assess-problem-wickednessSkill
- assess-publication-biasSkill
- assess-question-qualitySkill
- assess-ranking-consistencySkill
- assess-readiness-dimensionSkill
- assess-removabilitySkill
- assess-sensitivitySkill
- assess-system-boundarySkill
- assumption-stress-testSkill
- atomize-claimSkill
- atomize-conceptSkill
- attach-evidence-to-relationSkill
- audit-benchmark-validitySkill
- audit-convergence-independenceSkill
- audit-data-contaminationSkill
- audit-explanatory-compressionSkill
- audit-reporting-qualitySkill
- audit-structural-equivalenceSkill
- audit-structure-consistencySkill
- audit-study-validitySkill
- audit-validator-independenceSkill
- biologize-problemSkill
- biomimetic-transferSkill
- build-concept-fanSkill
- build-current-reality-treeSkill
- build-domain-ontologySkill
- build-failure-chainSkill
- build-noncircularity-matrixSkill
- calibrate-adversarial-confidenceSkill
- calibrate-probability-forecastSkill
- canonicalize-entitySkill
- categorize-evidenceSkill
- challenge-assumptionSkill
- characterize-anomalySkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Every changed dimension is named with before/after values.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
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
- Record object, current level, and scope dimensions (population, mechanism, context, outcome, timeframe, boundary).
- Generate at least one upward and one downward abstraction candidate when leverage is unclear.
- For each candidate, state what is gained, lost, and newly testable.
- Select the narrowest or broadest level that supports the caller's stated use and record rationale.
Output contract
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. |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

