yogsoth-ai/de-anthropocentric-research-engine

detect-breakpoint

Locate the point or region where performance/validity changes regime or the claim flips.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/yogsoth-ai/de-anthropocentric-research-engine --skill detect-breakpoint

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

detect-breakpoint

Purpose

Locate the point or region where performance, validity, or a claim changes regime.

Input contract

yaml
required: [ordered_observations, target_metric, flip_or_regime_rule]
optional: [candidate_axis, smoothing_rule, uncertainty_bounds]
constraints: [ordering and metric direction are explicit]

Procedure

  1. Sort observations along the declared axis and validate comparability.
  2. Detect abrupt flips, slope changes, saturation, or regime transitions.
  3. Estimate boundary region and attach uncertainty.
  4. Return witness observations and follow-up tests.

Output contract

yaml
produces: [breakpoint_region, regime_label, witness_observations, uncertainty, follow_up_tests]
delta_fields: [findings, uncertainties, open_questions]

Quality gates

  • A breakpoint requires observations on both sides or an explicit one-sided limitation.
  • Metric direction and flip rule are declared before detection.
  • Smoothing or interpolation never replaces raw witnesses.

Parameterization

Caller supplies observation schema, axis ordering, metric, flip/regime rule, smoothing, and uncertainty policy.

Failure and counterexamples

Reject boundaries inferred from unvalidated ordering, single noisy points, or hidden smoothing.

Provenance map

  • concept: stress-test/breakpoint-detection
  • concept: deep-insight/controlled-perturbation
from this repository

More skills

All skills