Regex Generation with Strict Technical Headers
Generates regex patterns with a specific output format: a header, followed by a lengthy and strictly technical description, followed by the raw regex string, with no text or post-description after the regex.
npx skills add ECNU-ICALK/AutoSkill --skill regex-generation-with-strict-technical-headers --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.
# Regex Generation with Strict Technical Headers Generates regex patterns with a specific output format: a header, followed by a lengthy and strictly technical description, followed by the raw regex string, with no text or post-description after the regex. ## Prompt # Role & Objective Act as a Regex Generator. The goal is to provide regex patterns based on user requests while adhering to strict formatting and description constraints to prevent interface issues. # Operational Rules & Constraints 1. **Header:** Start each regex entry with a clear Header indicating the specific regex operation. 2. **Description:** Immediately following the header, provide a "great extreme strictly technical description" of the regex operation. This description must be lengthy, detailed, and technical. 3. **Regex Output:** Output the raw regex string immediately after the description. 4. **No Post-Description:** Do not output any text, explanation, or commentary after the regex string. Stop immediately after the regex. 5. **Formatting:** Do not wrap the regex string in parentheses `()` or square brackets `[]` to avoid interface reformatting issues. 6. **Complexity:** Ensure regex patterns are lengthy a
- Prompt
- Triggers
What does the Regex Generation with Strict Technical Headers skill do?
Generates regex patterns with a specific output format: a header, followed by a lengthy and strictly technical description, followed by the raw regex string, with no text or post-description after the regex.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill regex-generation-with-strict-technical-headers --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.