50 reviewed skills.
Edits drafts so they read as if a person wrote them: cuts filler, stock phrases and mechanical rhythm while keeping every fact. Use when writing or revising any prose meant for human readers.
Use when answering research, analysis or fact-finding questions: labels how well supported each claim is, flags possibly outdated knowledge, presents competing explanations and points out biased framing instead of agreeing by default.
Use when polishing or reformatting a paper written in LaTeX: improves academic prose and checks submission formatting while keeping every command, equation, label and citation intact.
Rules for writing procedures, runbooks, help articles and error messages that are short, literal and easy to translate. Use when writing or editing technical instructions, not marketing copy.
Standing instructions that make answers check context, use varied sources and avoid assuming Western conditions are universal. Use when a question about society, health, economy or education could apply to different regions.
Use when editing a draft that reads as machine-written: removes stock phrases, inflated claims and formulaic structure while keeping the meaning and matching the writer's own voice.
Prepares a focused agenda for a manager's one-to-one and turns rough meeting notes into a short record with actions. Use when you are planning or writing up a regular one-to-one with a direct report.
Answers an employee's question using only the policy text you provide, says plainly when the policy is silent and points to who to ask. Use when you handle repeat questions about leave, expenses or conduct.
A checklist-driven way to review code changes for security flaws and report them with severity and concrete fixes. Use when reviewing a pull request, a code snippet, or new code that handles input, data or access.
Steers coding work toward the smallest correct change: reuse what exists, avoid new dependencies and speculative abstractions, never cut safety. Use when writing, reviewing or refactoring code where over-building is a risk.
Rules for designing web pages and interfaces that look deliberately made rather than template-generated: varied structure, honest content, consistent design tokens and a solid mobile layout. Use when creating or reviewing landing pages, sites or UI mockups.
A way of working for any change that touches user-facing text. Use when adding or editing strings, translations, dates, numbers or plurals in a product.
