Total 54,072 skills, Documentation & Writing has 1524 skills
Showing 12 of 1524 skills
Use when deciding which paper-related skill to use or how to sequence manuscript work from project setup through submission and rebuttal.
Write and edit professional content in Hebrew including marketing copy, UX text, articles, emails, and social media posts. Use when user asks to write in Hebrew, "ktov b'ivrit", create Hebrew marketing content, edit Hebrew text, write Hebrew UX copy, or optimize Hebrew content for SEO. Covers grammar rules, register from formal to dugri, mixed Hebrew/English, gendered language, nikud and numerals, and Hebrew SEO best practices. Do NOT use for Hebrew NLP/ML tasks (use hebrew-nlp-toolkit) or translation (use a translation skill).
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA comment, Slack post, async standup line, email, or meeting talking-points. Trigger when the user asks to write/rewrite for management / exec / VP / director / PM / release manager, asks for an "executive summary / leadership update / status update", says "make this less technical / less jargony", or asks for a slack / email / standup / meeting version of work originally written engineer-to-engineer.
Guides organizational and business storytelling—narrative structure (setup, tension, resolution), audience-tailored stories for executives, customers, boards, and teams, honest data and metrics framing, product and strategy narratives, incident and postmortem storytelling, and actuarial or insurance risk narratives for non-technical audiences. Covers story spine, key messages, and visual or slide narrative outlines. Use when the user says "tell the story", "storytelling", "narrative for executives", "data story", "board presentation narrative", "explain with a story", "story arc", "key message", "compelling narrative", "pitch story", or "incident story"—not cross-department reframing only (cross-department-translation), company-wide comms cadence and crisis wording packs (communication-lead), long-form creative fiction or screenwriting, brand copy without strategy context, or technical documentation and API reference (tech-writer-researcher).
Use when planning, running, auditing, or documenting systematic reviews, scoping reviews, PRISMA-style flows, screening decisions, inclusion criteria, exclusion criteria, or reproducible literature searches.
Rewrite and edit existing text to sound natural and human, removing common AI writing tells while preserving meaning and facts. Use when asked to humanize, de-AI-ify, un-AI, make it sound less robotic, polish an AI draft, or remove AI-writing signs in any prose (emails, docs, posts, essays, scripts).
This skill should be used when the user asks to "create a README", "generate a README", "make a readme", "write a README for my project", "need a README", "add a README", "document my project", "set up project docs", "readme with badges".
Intelligent Bid Document Writing Expert, specializing in preparing bid documents in the fields of engineering consulting, architectural design, and municipal engineering. This skill is activated when users mention terms such as: bid document, tender, bidding, bid proposal, technical bid, commercial bid, bid response, bidding plan, bid document, bid proposal, tender, proposal writing, bid document preparation, bid writing, tender document analysis, scoring standard optimization.
Write a structured escalation brief for an at-risk customer account. Use when an account has escalated, when a customer is threatening churn, when a P1 customer issue needs executive attention, or when preparing an internal save play. Produces a crisp escalation brief with account context, timeline, root cause, business impact, and a clear resolution plan.
Create structured technology trade-off analysis documents with scored comparison matrices. Use this skill whenever the user wants to compare technologies, evaluate architectural options, analyze build-vs-buy decisions, assess migration strategies, or produce any decision document that compares multiple approaches across weighted dimensions. Triggers on: 'trade-off analysis', 'tradeoff', 'comparison matrix', 'evaluate options', 'which technology should we use', 'compare approaches', 'pros and cons of', 'build vs buy', 'migration analysis', 'consolidation analysis', 'technology selection'. Also use when the user has completed technical research and wants to structure findings into a decision document.
Write PhD/Master's thesis — full chapter structure, literature review chapter, methodology chapter, results chapter, discussion chapter, and conclusion. Use when drafting thesis chapters, organizing thesis structure, or converting papers into thesis format.
Write, review, and restructure useful documentation with Diataxis, audience-specific README patterns, and AI-writing trope cleanup. Use when creating docs, improving READMEs, reorganizing documentation, or editing prose for clarity.