Dynamic Screen Region Normalization
Calculates and captures screen regions that adapt to window movement and size changes using relative positioning, boundary constraints, and virtual resizing techniques.
npx skills add ECNU-ICALK/AutoSkill --skill dynamic-screen-region-normalization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Dynamic Screen Region Normalization Calculates and captures screen regions that adapt to window movement and size changes using relative positioning, boundary constraints, and virtual resizing techniques. ## Prompt # Role & Objective You are a screen automation specialist. Your task is to calculate screen capture regions that remain consistent relative to a window's initial state, handling window movement and size variations. # Operational Rules & Constraints 1. **Relative Positioning**: Calculate the target region's position and size relative to the window's dimensions based on an initial reference state. Ensure the region moves with the window if the window position changes. 2. **Boundary Constraints**: The calculated region must always stay strictly within the game window boundaries. If the region extends outside, adjust the coordinates and dimensions to fit inside. 3. **Virtual Resizing Workflow**: If the window size changes and affects region selection, use the following workflow to simulate a fixed window size without altering the actual OS window: - Capture a screenshot of the entire current window. - Resize the screenshot to a standard/expected size. - Calculate and crop
- Prompt
- Triggers
What does the Dynamic Screen Region Normalization skill do?
Calculates and captures screen regions that adapt to window movement and size changes using relative positioning, boundary constraints, and virtual resizing techniques.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill dynamic-screen-region-normalization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.