Skill UI

API Reference Creator automatically guides technical writers through producing consistent, production-ready API docs, user guides, and architecture notes, covering patterns, validations, and best practices within documentation automation workflows.

This skill acts as a compatibility alias for pull request (PR) creation. It is designed to handle requests using the legacy name 'create-pr', redirecting the user to the canonical and updated workflow found in 'sentry-skills:pr-writer'. Use this when referencing the old skill name to ensure the latest PR writing standards are applied.

Guides users through writing, reviewing, and editing documentation with consistent structure, tone, and accuracy; ideal when creating README files, updating docs folders, or refining markdown drafts per contribution standards.

A comprehensive guide for implementing and managing Role-Based Access Control (RBAC) within the Guidewire InsuranceSuite (PolicyCenter, ClaimCenter, BillingCenter). It details role hierarchies (Admin, Underwriter, Claims Adjuster), permission checking logic using APIs, and best practices for ensuring regulatory compliance (NAIC, DOI). Includes code examples for user provisioning and audit logging.

Automates Neuronwriter operations through Rube MCP (Composio) by discovering current tool schemas, managing toolkit connections, and executing workflows with schema-compliant arguments.

This skill functions as an expert technical writer, generating comprehensive and structured README.md documentation for software projects. It meticulously analyzes the codebase, identifying project structure, tech stack, prerequisites, dependencies, and deployment pipelines, ensuring users receive a complete guide for local setup and production deployment.

This skill simulates a senior documentation engineer, generating highly structured, evidence-based technical documentation. It processes codebases to create comprehensive wiki pages, mandating deep structural analysis, citing specific code paths (file:line), and incorporating mandatory architectural diagrams (Mermaid). Ideal for creating deep-dive system manuals, component guides, and technical deep dives with verifiable sources.

This guide outlines best practices for creating high-quality, structured pull requests (PRs) using Git and GitHub CLI. It ensures that every PR description captures not only what changed, but also the 'why' and necessary context for reviewers, significantly improving the code review process and adherence to engineering standards.

A comprehensive, canonical workflow for defining, writing, and improving complex AI skills. It guides users through a structured, multi-step process, including resolving targets, synthesizing information, enforcing depth gates, authoring artifacts, optimizing descriptions, and conducting thorough evaluation and validation.

This guide provides detailed best practices for writing and maintaining comprehensive End-to-End (E2E) test cases for the 'lark-cli' tool. It covers the entire workflow, from exploring live help documentation and identifying leaf commands, to structuring state-proving tests (e.g., read-after-write assertions) and generating the required `coverage.md` artifact. Use this when adding or significantly updating E2E coverage for any specific functional domain.

Write terse, intent-only Conventional Commits messages. Use for generating commit messages from diffs or summaries, with optional scope, imperative mood, and concise body only when needed.

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.