skills.rest
dongzhuoyao
dongzhuoyaoCOMMUNITY
Explore all skills by this author →
Website𝕏@vtaohuGitHub

sue-normalize-structure

Scan DeepResearch workspaces for structural violations and migrate misplaced files to canonical locations.

Updated Aug 27, 2026
Search Tags:#boundary enforcement#file migration#sandbox compliance#sue workflow#workspace normalization#experiment structure
One-click install
npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-normalize-structure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sue-normalize-structure
Source: https://github.com/dongzhuoyao/deepresearch/tree/main/.codex/skills/sue-normalize-structure
Command: npx skills add https://github.com/dongzhuoyao/deepresearch --skill sue-normalize-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves messy, non-compliant DeepResearch workspaces that have misplaced files, duplicate configuration, legacy archive naming, and path escapes outside the allowed sandbox root, all of which cause SUE scale-up experiment workflows to fail during sync, dryrun, or fullrun steps.

Core Features & Use Cases

  • Dual-Axis Scanning: Checks both physical file placement at workspace/repo roots and lexical path escapes in code, configs, launchers, and documentation to catch all types of structural violations.
  • Targeted Migration: Moves misplaced files (stray data, duplicate runtime.yaml files, legacy scale-up-exp-history archives, repo-root experiment outputs) into their canonical locations without deleting any data.
  • Boundary Enforcement: Validates all filesystem references against the sandbox root contract and allowed external roots to prevent unauthorized path escapes, and auto-invokes before critical SUE steps to catch issues early.
  • Use Case: If your workspace has a full runtime.yaml at the root, checkpoints dumped at the repo root, or scripts referencing paths outside the sandbox, this skill identifies and fixes all these issues to ensure your SUE experiments run without boundary errors.

Quick Start

Use the sue-normalize-structure skill to scan your DeepResearch workspace for structural violations and migrate all misplaced files to their canonical locations.

Frequently Asked Questions about sue-normalize-structure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix misplaced files and boundary violations in a DeepResearch workspace?▼

To fix DeepResearch workspace boundary violations, scan your workspace and repository roots for physical file misplacement, lexical path escapes, and duplicate configurations, then migrate all misplaced files to their canonical compliant locations without deleting any data.

What causes SUE scale-up experiment workflows to fail during sync or dryrun?▼

SUE scale-up experiment workflows fail during sync or dryrun when the DeepResearch workspace has structural violations such as duplicate runtime.yaml files, legacy archive naming, checkpoints dumped at the repo root, or scripts referencing paths outside the sandbox root.

How do I enforce the sandbox root contract for SUE-managed experiment content?▼

Enforce the sandbox root contract by validating all filesystem references against allowed external roots to prevent unauthorized path escapes, ensuring all SUE-managed content resides within permitted filesystem boundaries before submitting sync, dryrun, or fullrun steps.

Does the workspace structure normalization process delete my misplaced data files?▼

The workspace structure normalization process does not delete your misplaced data files; it performs targeted migrations to move stray data, duplicate configurations, and legacy archives from the repo root into their canonical DeepResearch locations.

How do I check for lexical path escapes in my DeepResearch experiment code?▼

To check for lexical path escapes in DeepResearch experiment code, use a dual-axis scanning approach that inspects code, configs, launchers, and documentation for filesystem references that violate the sandbox root contract and allowed external root declarations.

When should I run a workspace normalization scan for my SUE experiments?▼

You should run a workspace normalization scan before critical SUE steps like sync, dryrun, or fullrun submissions to catch structural boundary violations early and ensure all SUE-managed content complies with the per-experiment directory rules.

Related Skills

Explore More Education & Research Skills→
plurigridplurigrid
60

skill-specification

Standardize agent skill definitions with YAML frontmatter for cross-platform compatibility.

Official
Advanced
caiokfcaiokf

gob-background-jobs

Manage parallel background commands with gob job IDs and output capture.

Community
Advanced
rjroyrjroy
6

retro

Record lessons learned from completed work into structured retro artifacts.

Community
Basic
FAeN399FAeN399

hello-world

Create, validate, lint, analyze, and migrate Claude Skills via CLI.

Community
Basic