revalidation
- Repo stars 0
- Author repo skills-registry
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes: File and directory paths exist and match the documentation. Referenced tools, reference docs, and linked files exist. Named types, classes, dialogs, and namespaces are accurate. Documented conventions still match existing code.
Analyze the configuration beyond mechanical path checks: Responsibilities align with the available tools and reference files. Conventions still make sense for the current codebase. Sections do not overlap, contradict each other, or duplicate stale guidance. Commonly edited areas are covered.
# Agent And Skill Revalidation
Use this workflow to keep Codex configuration accurate and coherent with the actual codebase.
## Step 1: Structural Validation
Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes:
- File and directory paths exist and match the documentation.
- Referenced tools, reference docs, and linked files exist.
- Named types, classes, dialogs, and namespaces are accurate.
- Documented conventions still match existing code.
Apply objective structural fixes automatically. These corrections do not need approval.
## Step 2: Logical Analysis
Analyze the configuration beyond mechanical path checks:
- Responsibilities align with the available tools and reference files.
- Conventions still make sense for the current codebase.
- Sections do not overlap, contradict each other, or duplicate stale guidance.
- Commonly edited areas are covered.
- Self-maintenance rules catch likely side effects.
- Reference files are structured well enough to scale.
Present logical findings one at a time, ordered by importance. For each finding:
1. Describe the issue and concrete suggestion.
2. Ask the user to approve, reject, or modify the suggestion. Use a concise plain-text question when no structured question tool is available.
3. Apply approved changes immediately before moving to the next finding.
Do not batch logical findings. Do not apply logical-analysis changes without user approval.
---
> Source: [BitzArt-VS/UI-Tweaks](https://github.com/BitzArt-VS/UI-Tweaks) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
Listed in source order.
sections -> Step 1: Structural Validation → Step 2: Logical Analysis
terms -> Use this workflow to keep Codex configuration accurate and coherent with the actual codebase. · Re-read the target agent or skill configuration file in full. · - File and directory paths exist and match the documentation. · Apply objective structural fixes automatically. · - Responsibilities align with the available tools and reference files. · Present logical findings one at a time, ordered by importance. · 1. Describe the issue and concrete suggestion. · Do not batch logical findings.
files/cmd -> BitzArt-VS/UI-Tweaks · github.com/BitzArt-VS/UI-Tweaks
body sha256 -> 84191a7aa85a
Step 1: Structural Validation
Re-read the target agent or skill configuration file in full. Validate every documented fact against the current codebase, including current-session changes: File and directory paths exist and match the documentation. Referenced tools, reference docs, and linked files exist. Named types, classes, dialogs, and namespaces are accurate. Documented conventions still match existing code.
Step 2: Logical Analysis
Analyze the configuration beyond mechanical path checks: Responsibilities align with the available tools and reference files. Conventions still make sense for the current codebase. Sections do not overlap, contradict each other, or duplicate stale guidance. Commonly edited areas are covered.