Total 53,016 skills, Documentation & Writing has 1500 skills
Showing 12 of 1500 skills
Use when writing or reviewing k6 documentation across TypeScript types, user docs, and release notes.
Scan the codebase and classify every fact by lifecycle stage — tag @draft, @spec, or @implemented based on what the code actually shows. Add missing facts, fix inaccurate ones, remove obsolete ones. Use when asked to discover facts, bootstrap or update a fact sheet, scan the codebase for truths, sync facts to match the code, or audit the fact sheet for accuracy.
Analyze story plot points, identify key plots and turning points. Suitable for in-depth analysis of plot structure and evaluation of plot development effectiveness
Creates comprehensive developer onboarding documentation and materials including step-by-step setup guides, first-task assignments, expected time per step, common troubleshooting, team introductions, and code walkthrough tours. Use when preparing "new developer onboarding", "first day setup", "junior dev training", or "team member onboarding".
Publish documentation and books with GitBook including spaces, collections, variants, Git sync, collaboration, and API integration
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation.
Create a new specification file for the solution, optimized for Generative AI consumption.
Write and format OceanBase database SQL statement documentation following official style guidelines. Use when creating or editing SQL reference documentation for OceanBase database.
Comprehensive toolkit for writing high-quality computer science research papers (conference, journal, thesis). Provides narrative construction guidance, sentence-level clarity principles (Gopen & Swan), academic phrasebank, CS-specific conventions, and section-by-section quality checklists. Use when assisting with academic paper writing, revision, or structure planning across all stages from drafting to submission.
Use when structuring, formatting, evaluating, or reviewing a Technology Innovation Management (TIM) project report for Carleton University — provides report rules, chapter guidance, literature review expectations, research method templates, and a compliance-audit checklist.
Plan multi-part content series with structure, cross-linking, and publishing cadence. Use when user needs to plan a blog post series, structure a multi-part tutorial, or design content with cross-linked navigation. Use for "plan series", "series on [topic]", "multi-part blog", or "content series". Do NOT use for writing individual posts, single-article outlines, or content calendar planning without series structure.
Prowler documentation style guide and writing standards. Trigger: When writing documentation for Prowler features, tutorials, or guides.