Skill UI

This skill guides the systematic triage of project issues and external pull requests (PRs). It moves development items through a defined state machine using roles (e.g., bug, enhancement) and states (e.g., ready-for-agent, wontfix). The process involves context gathering, cross-codebase verification, deep questioning (grilling), and generating comprehensive, agent-ready briefs or marking them for human implementation.

A framework-agnostic, builder-based SEO system designed for React and React Native-for-web applications. It centralizes site identity (title, description, OG tags) in a single source of truth, ensuring all metadata, canonical URLs, and structured data (JSON-LD, sitemap, robots.txt, RSS) are consistent, machine-readable, and automatically generated for every route.

A comprehensive skill for generating production-grade, robust automation scripts and end-to-end tests using Selenium WebDriver. Supports multiple languages (Java, Python, JS, C#, etc.) and execution environments, including local machines and TestMu AI cloud for cross-browser compatibility. It guides users on best practices like explicit waits, Page Object Model (POM), and stable locator strategies, acting as a senior QA automation architect.

Flox is a declarative, Nix-based environment manager designed to create perfectly reproducible development environments. It handles system-level dependencies (like compilers, databases, and native libraries) and ensures that complex toolchains across multiple languages (Python, Node.js, Go, etc.) function identically across macOS and Linux. Ideal for solving 'works on my machine' issues and onboarding new team members instantly.

A comprehensive, end-to-end playbook designed for software engineers and AI agents. It provides a structured methodology to safely introduce machine learning capabilities into existing, non-ML codebases. The process covers critical stages: problem framing, data readiness, architectural decoupling (using dedicated APIs/services), baseline model implementation, and final handoff to MLOps practices (CI/CD, monitoring).

Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protobuf, or JSON Schema), with generated consumer types and contract-verified integration to prevent field drift and mock/production shape mismatch.

This guide outlines the stringent standards for academic paper reproducibility in theoretical machine learning (e.g., COLT). It provides a comprehensive pre-submission audit checklist covering formal proof completeness, assumption bookkeeping, constant tracking, and ensuring numerical illustrations are fully traceable. Use this methodology to strengthen your theoretical claims and withstand rigorous peer review.

This comprehensive style guide is written for authors submitting research papers to the CoRL conference. It provides specific directives on structuring the narrative to satisfy two distinct audiences: machine learning theorists and robotics engineers. It emphasizes quantifying all claims with concrete evidence scales (e.g., success rates, frequency), structuring the argument within a limited page count, and properly integrating mandatory sections like Limitations.

This guide provides comprehensive instructions for creating a robust, reproducible artifact package for database systems research. It details best practices including containerization, pinning workloads, generating a permanent DOI-archived record, and designing the package to be successfully built and demonstrated on a reviewer's clean machine within a tight time budget. The goal is to strengthen scientific rigor and ensure permanent, open-access citation.

This guide details best practices for submitting research artifacts to academic conferences, following the ACM Artifact Review and Badging scheme. It covers everything from required packaging plans (Docker, README, data provenance) to achieving various levels of validation (Functional, Reusable, Reproduced). Learn how to structure your submission to ensure maximum reproducibility and pass rigorous evaluator checks on a clean machine.

Provides comprehensive guidelines for packaging supplementary materials, including code, data, model weights, and benchmarks, for major machine learning conferences like ICML. It details the requirements for both the double-blind review stage (focusing on anonymization and minimal replication commands) and the final public release package (ensuring permanent public links and clear licensing).

This skill acts as a comprehensive router for the NeurIPS academic workflow. It guides users through every stage of preparing a machine learning manuscript, from initial topic and track selection to writing, mandatory paper checklist completion, OpenReview submission, handling the double-blind review process, and finalizing the camera-ready version. It helps ensure the manuscript is robust, evidence-backed, and adheres to all conference policies.