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.

A comprehensive collection of battle-tested, structured prompts designed to elevate interactions with Large Language Models (LLMs). Covers advanced use cases including expert coding reviews, system architecture design, performance analysis, technical writing, and creative brainstorming, ensuring high-quality, actionable AI output.

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 enforces Sentry's rigorous blog writing standards, ensuring all content—from deep technical dives to product announcements—reads like it was written by a senior developer. It guides users on adopting a specific, opinionated, and technically credible voice, structuring posts around problem-solving, and avoiding generic corporate jargon.

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.

This skill involves recording technical decisions and documentation within software projects. It focuses on capturing the reasoning behind design choices, architecture decisions (ADRs), and public API changes. It helps future engineers and agents understand the codebase context, constraints, and trade-offs. It includes guidelines for writing ADRs, inline comments, and API documentation to maintain clarity and maintainability.

A comprehensive guide and skill for generating and auditing high-quality technical documentation for Go projects. It covers writing accurate godoc comments, READMEs, CONTRIBUTING, and CHANGELOGs for both libraries and CLIs, adhering to professional best practices. Supports multi-agent orchestration for large-scale codebases.

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 technical and scientific documentation using Markdown as the source format, enhanced by embedded Mermaid diagrams. This method establishes text-based diagrams as the canonical standard, ensuring that all visualizations are clean, editable, and highly readable in version control systems like Git. It is ideal for generating reports, architectural diagrams, workflows, and any content that requires cross-platform rendering and version history.

Generate complete patent specifications from claims and invention disclosure documents. Supports multiple jurisdictions (CN, US, EP) with proper formatting for title, technical field, background, summary, drawings description, detailed description, and abstract sections. Includes claim support verification and quality review.

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.