Skip to content
Agentmart
Submit a tool

map-validity-envelope

Map where a claim, method, or design remains valid by defining variation axes, probing systematic or adversarial/boundary values, detecting breakpoints, and…

Skill by yogsoth-ai

IndexedApache-2.0★ 505
Write a review

Chalk Labs

Need help deploying map-validity-envelope?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/yogsoth-ai-map-validity-envelope

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Map where a claim, method, or design remains valid by defining variation axes, probing systematic or adversarial/boundary values, detecting breakpoints, and constructing a multidimensional validity envelope. Critical-case selection is an optional inference-maximizing mode.

Use cases: design, ml

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/map-validity-envelope

What's inside

Skill name
map-validity-envelope
Description
Map where a claim, method, or design remains valid by defining variation axes, probing systematic or adversarial/boundary values, detecting breakpoints, and constructing a multidimensional validity envelope. Critical-case selection is an optional inference-maximizing mode.
License
Apache-2.0
Instructions
66 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# map-validity-envelope
## Purpose
Map where a claim, method, or design remains valid by defining axes, probing values, detecting breakpoints, and constructing a multidimensional validity envelope.
## Input contract
```yaml
mode_contracts:
  systematic-perturbation: &validity_input
    required: [claim_or_method, validity_target, analysis_dimensions]
    optional: [baseline_conditions, critical_case_rule, perturbation_budget]
    constraints: [axes_values_outcome_measure_and_breakpoint_rule_must_be_explicit]
  boundary-value-stress: *validity_input
  critical-case: *validity_input
```
## Execution protocol
Do not perform called SOP operations inline; each loaded SOP owns its contract and thresholds.

1. You MUST load skill `define-analysis-dimensions` to define the validity axes. You MUST load skill `enumerate-dimension-values` to enumerate representative and boundary values.
2. Apply the probes required by the selected mode and retain their evidence.
3. You MUST load skill `detect-breakpoint` to locate validity transitions. You MUST load skill `construct-validity-envelope` to construct the supported envelope.
4. You MUST load skill `analyze-scaling-regime` to analyze scale-dependent regime changes.
   If global effect decomposition is needed beyond the envelope, consider `sensitivity-analysis`. If the resulting boundary claim lacks a reachable falsifier, consider `falsifiability-audit`.
Deviation: use `critical-case` when a decisive case can replace broad probing; otherwise use `systematic-perturbation` or `boundary-value-stress` according to the declared mode and evidence.
## Output contract
```yaml
mode_contracts:
  systematic-perturbation:
    produces: [dimension_schema, perturbation_records, breakpoints, validity_envelope]
    delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
  boundary-value-stress:
    produces: [dimension_schema, perturbation_records, breakpoints, validity_envelope, critical_case_report]
    delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
  critical-case:
    produces: [breakpoints, validity_envelope, critical_case_report]
    delta_fields: [findings, evidence_updates, uncertainties, decisions, open_questions]
```
## Thresholds and quality gates
- Breakpoints require an explicit outcome criterion and before/after evidence.
- Envelope claims must state untested regions and uncertainty.
## Failure and counterexamples
Do not infer an envelope from a single favorable case. Mark extrapolation outside sampled axes as unsupported.
## Provenance map
- concept: validity-envelope-mapping [strategy]
- resolved: systematic-perturbation
- resolved: variation-axis-definition
- resolved: controlled-perturbation
- concept: validity-envelope-construction [sop]
- resolved: adversarial-stress-testing
- concept: validity-envelope-mapping [stress strategy]
- resolved: parameter-space-mapping
- resolved: extreme-value-generation
- resolved: breakpoint-detection
- intermediate: Pass5/validity-envelope-analysis
- intermediate: Pass5/boundary-stress-test
## Preserved source criteria ledger
| source | source line | kind | source criterion |
|---|---:|---|---|
| v4 architecture | modes/calls | structural | Actual modes are `systematic-perturbation`, `boundary-value-stress`, `critical-case`; alias labels are not used. |
## Context checkpoint / Delta notes
Append axes, values, perturbations, breakpoints, envelope, critical cases, scaling findings, and untested regions.

## Mode branches
- `systematic-perturbation`: broad controlled variation across declared axes. You MUST load skill `apply-perturbation` to vary the declared axes systematically.
- `boundary-value-stress`: emphasize boundary, pathological, and adversarial values. You MUST load skill `apply-perturbation` to probe boundary and pathological values.
- `critical-case`: select inference-maximizing cases and document selection logic. You MUST load skill `select-critical-case` to select and justify the decisive cases.

From yogsoth-ai/de-anthropocentric-research-engine, Apache-2.0.

More from yogsoth-ai/de-anthropocentric-research-engine

Signals

Stars
505
Forks
43
Open issues
1
Last commit (this folder)
Sep 23, 2026 (1 month ago)
Last release
Oct 23, 2026 (13 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from yogsoth-ai

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get map-validity-envelope running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying map-validity-envelope?

CallGet help
Cite this page

map-validity-envelope skill. Agent Mart. https://agentmart.dev/skills/yogsoth-ai-map-validity-envelope (last updated 2026-10-24)