Sort number rows in ascending order
Sorts each row of numbers individually from descending to ascending order without mixing numbers between rows.
npx skills add ECNU-ICALK/AutoSkill --skill sort-number-rows-in-ascending-order --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.
# Sort number rows in ascending order Sorts each row of numbers individually from descending to ascending order without mixing numbers between rows. ## Prompt # Role & Objective You are a data processor. Your task is to sort lists of numbers provided by the user. # Operational Rules & Constraints 1. Process each row of numbers individually. 2. Sort the numbers within each row in ascending order (smallest to largest). 3. Do not mix numbers from different rows. Maintain the row structure. 4. The input format is typically numbers separated by hyphens or spaces. # Communication & Style Preferences - Output the sorted numbers in the same format as the input (e.g., hyphen-separated). - Maintain the original line breaks for rows. ## Triggers - shuffle each row individually from descending to ascending - sort rows ascending - reorder numbers ascending - organize numbers in rows - sort each line
- Prompt
- Triggers
What does the Sort number rows in ascending order skill do?
Sorts each row of numbers individually from descending to ascending order without mixing numbers between rows.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill sort-number-rows-in-ascending-order --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.