Skill UI

Automates the creation of deprecation notices for technical documentation, guiding users through patterns, best practices, and validation steps when writing API docs, user guides, or architecture notes.

This comprehensive guide teaches the best practices for writing effective, blameless postmortem reports following technical incidents. It provides a structured approach to documenting timelines, conducting root cause analysis (RCA), identifying systemic failures, and creating actionable follow-up items. Mastering this skill is crucial for fostering organizational learning and preventing future service disruptions.

Defines a Markdown/Mermaid-first documentation skill for scientific and technical writing, providing diagram standards, 24 reference types, and templates so every report, README, or analysis stays text-first, versionable, and visualization-ready.

This skill provides deep technical expertise regarding the DWARF debugging format (v3-v5) and the DWARF standard. It assists in analyzing, parsing, verifying, and generating debug information from compiled binaries. Use cases include answering questions about the DWARF specification, writing code that interacts with DWARF data, and utilizing tools like `dwarfdump` or `readelf` for structural validation and quality metric extraction.

A comprehensive guide for writing, reviewing, and structuring technical documentation for Go projects. It covers best practices for godoc comments, READMEs, contribution guidelines, and changelogs, ensuring documentation is accurate, discoverable, and tailored for both human readers and AI agents. Applicable to both libraries and CLIs.

An advanced technical writer specializing in creating structured, high-quality software documentation. This skill strictly adheres to the Diátaxis Framework, ensuring content is categorized into Tutorials (learning), How-to Guides (problem-solving), Reference (technical details), and Explanations (concept understanding). It follows a rigorous workflow: clarification, structure proposal, and content generation, guaranteeing clarity, accuracy, and user-centricity.

A comprehensive skill for creating scientific and technical documentation using Markdown and embedded Mermaid diagrams. This method establishes diagrams as text-based sources of truth, ensuring clean version control via Git diffs, native rendering across platforms (GitHub, Notion), and compatibility with AI tools, making it superior to static images.

A professional methodology for writing penetration test and red team reports, covering executive summaries, technical findings, CVSS scoring, evidence handling, remediation tracking, retest notes, and delivery formats for clients and internal teams.

This skill automates the complex compilation process required for LaTeX documents, specifically implementing the sequence: xelatex -> bibtex -> xelatex -> xelatex. It takes pre-assembled content (such as abstracts and body text) and compiles them into a cohesive, structured academic paper. Ideal for the final steps of scientific and technical writing.

This tool acts as a pre-drafting planning mechanism for academic or technical writing. It analyzes the user's request to extract and structure detailed preferences, such as target audience, citation style, depth, and desired emphasis. It determines the optimal generation mode (direct or preference-driven) before any writing or research takes place, ensuring all required criteria are met systematically.

A comprehensive template designed to structure complex technical specifications, ensuring a complete record of engineering decisions. It guides users to document problem statements, proposed solutions, system architecture, data models, API designs, security considerations, and rollout plans, bridging product requirements and technical implementation.