Total 65,204 skills, Documentation & Writing has 2040 skills
Showing 12 of 2040 skills
Write a business report in Word with a fixed structure (executive summary, background, analysis, recommendations, appendix), sourced numbers and a consistent voice. Use when the user asks for a report, memo, review, assessment or analysis document, or to turn notes or data into one.
Run multi-round searches with cross-checking and produce a research report with cited sources, delivered as a Word document
Verify that every reference in a manuscript really exists and matches its metadata, catching hallucinated, corrupted or mismatched citations before submission. Use when checking a .bib file or reference list, after an AI assistant drafted citations, when a DOI may point to the wrong paper, when adding missing DOIs, or before camera-ready. Queries Crossref, OpenAlex and arXiv; zero dependencies.
Author, configure, structure, and troubleshoot OpenAPI/Swagger API reference documentation in GitBook. Use this whenever a task involves a GitBook OpenAPI block or `{% openapi %}` block, adding or updating an OpenAPI/Swagger spec in GitBook (by file or URL, via the API, MCP, CLI, or app UI), generating API reference pages from a spec, configuring the interactive "Test it" runner (auth, servers, CORS, proxy), customizing pages with GitBook `x-*` extensions (icons, titles, navigation hierarchy, code samples, enum descriptions), marking operations experimental/deprecated/hidden, or automating spec updates in CI/CD. Trigger even when the user only mentions GitBook plus OpenAPI, puts an `x-` extension on a spec destined for GitBook, or asks "why isn't my spec loading" or "why doesn't Test it work", without naming this skill.
Writes or overwrites WORK-REPORT.md at the working tree root - session self-report (goal, problem/solution, follow-ups, suggested skills, abandoned) a reviewer or later session reads instead of re-deriving intent from the diff. Use for "work report", "checkpoint this", "hand off", "write up what we did". Offer proactively - asking first - when work is finished: "done", "ready to commit", "wrapping up", handoff to another agent.
Write, author, edit, and format GitBook documentation pages in Git-synced repos, IDEs, or any text editor. Use whenever a task involves creating or editing a GitBook markdown page, writing or updating a README.md or SUMMARY.md, inserting a hint, tab, stepper, card, or other GitBook block, configuring page frontmatter or layout options, setting up variables or expressions, or formatting content for GitBook outside the GitBook UI.
Generate or optimize figure/table captions for academic papers. Geography-aware: study area, CRS notation, data source. Writes output to .tex file. 图表标题生成与优化。
Generate or optimize academic paper abstracts using the 5-sentence Farquhar formula. Supports generate-from-scratch and restructure-existing paths. Produces labeled output for formula verification plus a clean version for clipboard use. 摘要生成与优化，支持从原始材料生成或改写现有摘要。
Polish English academic text through quick-fix or guided multi-pass workflow. Adapts to journal style with in-place editing and change tracking. 英文学术论文润色。
Verify logical consistency across paper sections. Traces argument chains and identifies gaps, unsupported claims, terminology inconsistencies, and number contradictions. 论文逻辑验证，识别论证链断裂、无支撑声明、术语不一致、数字矛盾。
Enforce modern Chinese writing standards including tone, spacing rules (Pangu), full-width punctuation, paragraph structure, and active voice. Provides specific guidelines for blog posts, error messages, UI text, and technical documentation.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.