50 reviewed skills.
Reviews a job advertisement for biased, exclusive or unclear wording and suggests fair alternatives. Use when you have a job ad or description to check before it is published.
Teaches how to write short, warm live chat replies for common situations: greeting, gathering details, waiting, saying no, bugs, anger and hand-offs. Use when drafting or improving a live chat reply.
Builds a one-page customer persona from interview notes, grounded in what people actually said. Use when you have notes from customer calls and want a persona your team can use for messaging and decisions.
Instructions for answering a prospect who asks you to just send information: turn the brush-off into a short, useful reply that earns a real next step. Use when a prospect says send me something and you are unsure how to answer.
Reviews a drafted customer reply for tone, clarity and risky promises, then returns a cleaner version. Use when a support agent pastes a draft and wants it checked before it goes to the customer.
Use when you need subject lines for a sales email. Gives ten honest options in five styles, with your two best picks and a matching opening sentence.
Tags each support ticket with one main topic, urgency and the team that should own it, the same way every time, and explains the choice in one line. Use when sorting a support inbox or cleaning up tags before a report.
Explains computer, account and security problems in plain steps and everyday words. Use when helping someone who is not comfortable with technical or security terms.
Prepares a seller for a weekly pipeline or forecast meeting from their deal list: flags stale and risky deals, checks close dates, and drafts a short update with asks. Use when someone pastes their open deals before a pipeline review or one-to-one.
Use when an engineer-to-engineer update needs to reach managers, product leads or executives: rewrites it in plain cause-and-effect language, sized for the channel (chat post, email, standup line, ticket comment, talking points).
Standing rules for writing and revising technical or business prose so it is specific, plain and honest about certainty. Use when drafting or editing documentation, reports, specs, release notes or explanations.
A way of working for reviewing copy for exclusionary wording, blaming tone and clarity barriers. Use when polishing product text, emails, help articles or announcements.
