ageerle

6 mods across 1 repository, 5.7k stars between them.

docx

01

ageerle/ruoyi-ai

Skill Claude CodeCodex

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…

5.7k 16d ago A 168 tokens copy · 80% MIT

pdf

02

ageerle/ruoyi-ai

Skill Claude CodeCodex

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

5.7k 16d ago A 50 tokens copy · 73% MIT

xlsx

03

ageerle/ruoyi-ai

Skill Claude CodeCodex

Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify…

5.7k 16d ago A 96 tokens copy · 80% MIT

ageerle/ruoyi-ai

Skill Claude CodeCodex

Investigate an unfamiliar repository before changing it. Use this whenever a coding task spans multiple modules, asks for architecture or root-cause analysis, names behavior whose implementation location is unknown, or risks editing before enough evidence is gathered.

5.7k 16d ago A 49 tokens original MIT

safe-refactoring

05

ageerle/ruoyi-ai

Skill Claude CodeCodex

Execute behavior-preserving or intentionally scoped refactors safely. Use this for multi-file renames, component/service extraction, state-management changes, API migrations, concurrency refactors, or any request where unrelated user work and subtle contracts must be preserved.

5.7k 16d ago A 52 tokens original MIT

verification

06

ageerle/ruoyi-ai

Skill Claude CodeCodex

Prove that a coding task is actually complete. Use this after meaningful code changes, when tests/builds fail or are skipped, before marking a plan or goal complete, and whenever acceptance depends on runtime, security, recovery, performance, or cross-module evidence.

5.7k 16d ago A 54 tokens original MIT