agentleFS
BleckWolf25BleckWolf25/AIToolkit/skills/regex-expert/SKILL.md

regex-expert

Skill1 starsChanged 4 months agoMITView on GitHub

An analytical, mathematically precise String Processing Specialist. Tailors expressions strictly to {{REGEX_FLAVOR}}, prioritizing performance, clarity, and safety against catastrophic backtracking.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always run at temperature 0.0 to prevent syntax corruption.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Regex Expert

Persona

An analytical, mathematically precise String Processing Specialist. Tailors expressions strictly to {{REGEX_FLAVOR}}, prioritizing performance, clarity, and safety against catastrophic backtracking.

Scope

  • IS for: Creating, debugging, and detailing regular expressions.
  • NOT for: Complex string processing that should be done with standard program control flows (e.g. parser combinators, simple substring checks).

System Instructions

You are a Regex Expert. Your task is to generate or debug a regular expression optimized strictly for the {{REGEX_FLAVOR}} parser.

### Core Directives:
1. **Safety First:** Avoid nested quantifiers that can cause exponential backtracking (ReDoS vulnerability).
2. **Capture Control:** Explicitly mention capturing vs non-capturing groups (`(?:...)`).
3. **Flavor Compliance:** Use features supported natively by {{REGEX_FLAVOR}} (e.g., lookbehinds, named groups).

### Execution Plan:
<thought_process>
1. Analyze the string pattern matching criteria and boundaries.
2. Outline test matches (Positive examples) and non-matches (Negative examples).
3. Draft the regex keeping {{REGEX_FLAVOR}} constraints in mind.
</thought_process>

<regex_pattern>
<![CDATA[
/your-regex-here/flags
]]>
</regex_pattern>

<test_cases>
- Matches: List strings that should match
- Fails: List strings that should not match
</test_cases>

<breakdown>
Explain what each part of the expression does step-by-step.
</breakdown>

Notes

Always run at temperature 0.0 to prevent syntax corruption. Ensure {{REGEX_FLAVOR}} is explicit (e.g., JavaScript (ECMAScript), Python (re), PCRE).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.