Total 30,622 skills, Documentation & Writing has 1022 skills
Showing 12 of 1022 skills
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Quickly search the user's library of real experiences, opinions and case materials (over 1800 entries) to add authenticity and credibility to content. Use this skill when the user mentions "real experience", "personal case", "well-founded", "practical experience", "material library" or "looking for examples".
Generate project documentation from codebase analysis — ARCHITECTURE.md, API_ENDPOINTS.md, DATABASE_SCHEMA.md. Reads source code, schema files, routes, and config to produce accurate, structured docs. Use when starting a project, onboarding contributors, or when docs are missing or stale. Triggers: 'generate docs', 'document architecture', 'create api docs', 'document schema', 'project documentation', 'write architecture doc'.
Write a client proposal or quote for a service business. Covers project understanding, scope, timeline, pricing presentation, and terms. Works for web development, consulting, trades, professional services, and any B2B service engagement. Triggers: proposal, quote, project proposal, client proposal, scope of work, SOW, engagement letter.
Structure scenes and control pacing using scene-sequel rhythm. Use when individual scenes work but don't accumulate, when pacing feels off (too rushed or too slow), when transitions feel mechanical, or when readers can follow but aren't compelled forward. Based on Dwight Swain's Goal-Conflict-Disaster and Reaction-Dilemma-Decision structure.
Diagnose and improve humor using systems thinking. Use when jokes fall flat, when humor feels forced, when punchlines don't land, or when you want to systematically enhance comedic writing. Treats jokes as engineerable connection systems.
Technical writer specializing in the Diátaxis documentation framework
Senior Content Humanization Architect for 2026. Specialized in natural language refinement, authentic voice injection, and AI-detection avoidance. Expert in transforming robotic, predictable AI drafts into high-engagement, human-centric content that satisfies E-E-A-T standards and builds deep trust through empathy, storytelling, and cultural nuance.
Document a business process — flowcharts, RACI, and SOPs. Use when formalizing a process that lives in someone's head, building a RACI to clarify who owns what, writing an SOP for a handoff or audit, or capturing the exceptions and edge cases of how work actually gets done.
Draft a knowledge base article from a resolved issue or common question. Use when a ticket resolution is worth documenting for self-service, the same question keeps coming up, a workaround needs to be published, or a known issue should be communicated to customers.
Review content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. Use when authoring or reviewing content in adev/src/content.