Explore

Intercepts, redacts sensitive credentials from, and compresses large terminal crash dumps, stack traces, and multi-line error outputs into a compact 25-line Failure Digest to conserve context windows. Use when an application, build, container, test suite, or CI pipeline crashes with massive stdout/stderr payloads, or whenever unhandled exceptions and runtime errors occur even if the user does not explicitly name this skill. Triggers on phrases like "debug this failure", "why did this build crash", or "here is the error log".

Check whether factual claims in a report are supported by supplied sources. Use when reviewing student research reports, checking citations, or auditing AI-generated summaries.

Investigates software bugs, explains failing tests, reviews suspicious permissions, and traces errors across frontend, API, backend, and database layers. Use when a developer reports broken behavior or needs root-cause analysis and an evidence-backed fix, even when the faulty file is unknown.

Evidence-based bug localization for unfamiliar codebases. Use when investigating bug reports, exceptions, stack traces, failing tests, or unexpected behavior to rank suspicious files with verifiable evidence and practical verification steps.

Say what this does and when an agent should reach for it. This is the line that decides whether a skill is used at all, so write it for the agent choosing between tools rather than for a person browsing a list.

Say what this does and when an agent should reach for it. This is the line that decides whether a skill is used at all, so write it for the agent choosing between tools rather than for a person browsing a list.

Audits CSV datasets for missing values, duplicate rows, inconsistent data types, invalid values, and potential outliers. Use when a data analyst needs a reliable data-quality report and safe cleaning recommendations.

Say what this does and when an agent should reach for it. This is the line that decides whether a skill is used at all, so write it for the agent choosing between tools rather than for a person browsing a list.

Say what this does and when an agent should reach for it. This is the line that decides whether a skill is used at all, so write it for the agent choosing between tools rather than for a person browsing a list.

Guide students, beginners, and small teams from a software project idea to a scoped MVP, technical architecture, actionable build plan, testing strategy, README, and demo. Use when planning, building, debugging, reviewing, or preparing to present a software project.

Migration Guard reviews SQL database migrations for data-loss risks, production locks, unsafe backfills, rollback gaps, and incompatibility with rolling application deployments. Use when a user asks to review a database migration, check whether a schema change is safe, audit a migration before deployment, or assess a risky ALTER, DROP, constraint, index, rename, type change, or backfill. Use it even when the user does not explicitly say “database migration” but provides SQL or schema changes and asks whether the change could break production, lose data, cause downtime, or fail during a rollout. Do not use it for general SQL questions unrelated to schema changes.

RepoMedic is an evidence-based software debugging skill. Use when an agent needs to investigate a bug even if the user does not explicitly ask for debugging. Trigger on requests such as "fix this error", "why is my API returning 401", "my tests are failing", "debug this crash", or "find the root cause". It guides agents to inspect relevant evidence, separate confirmed causes from hypotheses, propose minimal fixes, create regression tests, and report honestly which checks were or were not run.

Troubleshoots deployment failures, build errors, missing dependencies, environment configuration issues, and application startup problems. Use when users ask "why is my deployment failing?", "fix my build error", or "my app will not start", even if they do not mention deployment troubleshooting or this skill by name.

Drafts a ready-to-file Right to Information (RTI) application under India's RTI Act 2005. Use when a user wants records, status or decisions from an Indian government body, e.g. pending scholarship, delayed pension, road work expenses, exam evaluation. Also drafts first appeals. Not for legal advice, court cases or private companies.

Checks a C or Python assignment against its own spec before submission, like a strict autograder: file and zip names, function signatures, exact output format, banned headers or libraries, and edge cases the spec names. Runs the spec's samples and reports each requirement as PASS, FAIL or CANNOT VERIFY with evidence, without writing the solution. Use when a student says "check my assignment", "will this pass the autograder" or "review my lab before I submit", or shares a spec with code.

Analyze GitHub Actions CI failures for Python and Node.js projects, identify the most likely root cause from logs and repository evidence, and produce safe, evidence-based remediation and verification steps. Use when a user asks "why is my GitHub Actions build failing", says "debug this CI log", shares a failed npm ci, pytest, build, test, or lint job, provides workflow YAML, or asks why an automated check failed.

Helps agents plan and validate software ideas. Use when a user asks to evaluate a startup idea, research competitors, define an MVP, or test product demand.

This skill helps beginners learn DSA in C++, solve LeetCode problems, understand data structures and algorithms, build problem-solving skills, and prepare for coding placements. Use this skill when the learner says “teach me DSA”, “solve this LeetCode problem”, “explain this algorithm”, “give me DSA practice”, or “help me prepare for placements”.

Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.

ROS 2 engineering: rclcpp/rclpy, colcon/ament, launch, QoS/DDS, tf2/URDF, ros2_control, Nav2, MoveIt 2, sensors, runtime/artifact provenance, and hardware safety. Use for development, review, debugging, and ROS 1 migration to ROS 2. Not for general C++/Python, unrelated middleware, or web/mobile tasks.

Export a monorepo into review-ready zip bundles for a non-agentic frontier model (GPT Pro on the ChatGPT web UI, or any chat model with file upload) — node_modules-free, secret-free, split by subsystem so a model with no shell and a bounded context can navigate the codebase a part at a time. Use for packaging a repo for external LLM review, audit, or architecture feedback. Pairs with the `gptpro-handoff` workflow skill.

Patterns and best practices for integrating ROS2 systems with web technologies including REST APIs, WebSocket bridges, and browser-based robot interfaces. Use this skill when building web dashboards for robots, streaming camera feeds to browsers, exposing ROS2 services as REST endpoints, or implementing bidirectional WebSocket communication between web UIs and ROS2 nodes. Trigger whenever the user mentions rosbridge, rosbridge_suite, roslibjs, FastAPI with ROS2, Flask with rclpy, WebSocket for robot telemetry, MJPEG streaming, WebRTC for robots, REST API wrapping ROS2 services, web-based robot control, browser robot interface, robot dashboard, CORS configuration for robots, or any web-to-ROS2 bridge pattern. Also trigger for authentication on robot web interfaces, rate limiting sensor streams, video streaming from robot cameras to browsers, or running async web frameworks alongside the ROS2 executor. Covers rosbridge_suite, FastAPI, Flask, WebSocket, and WebRTC approaches.

Comprehensive best practices for robot perception systems covering cameras, LiDARs, depth sensors, IMUs, and multi-sensor setups. Use this skill when working with RGB image processing, depth maps, point clouds, sensor calibration (intrinsic, extrinsic, hand-eye), object detection, semantic segmentation, 3D reconstruction, visual servoing, or perception pipeline optimization. Trigger whenever the user mentions OpenCV, Open3D, PCL, RealSense, ZED, OAK-D, camera calibration, AprilTags, ArUco markers, stereo vision, RGBD, point cloud filtering, ICP registration, coordinate transforms, camera intrinsics, distortion correction, image undistortion, sensor streaming, frame synchronization, or any computer vision task in a robotics context. Also covers multi-camera rigs, time synchronization across sensors, perception latency budgets, and production deployment of perception pipelines.

Bringing up a complete ROS2 system on a robot's onboard computer: systemd services, launch file composition, ordered startup, and production monitoring. Use this skill when configuring a robot to start ROS2 nodes on boot, writing systemd unit files for ROS2 launch, composing layered launch files for full robot stacks, setting up watchdog monitoring, configuring udev rules for deterministic device naming, or debugging boot-time race conditions. Trigger whenever the user mentions robot bringup, robot startup, systemd for ROS2, ROS2 on boot, launch file composition, robot boot sequence, udev rules for cameras or serial ports, automatic restart for ROS2 nodes, network configuration for multi-machine ROS2, log rotation for robots, graceful shutdown of robot stacks, or SSH-based remote debugging. Also trigger for sourcing workspaces in systemd, ordered startup with health checks, or running ROS2 systems as long-running production services. Covers systemd on Ubuntu 22.04/24.04 with ROS2 Humble, Iron, and Jazzy.

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.