Skill UI

This toolset provides a comprehensive development workflow for iterating on MicroPython applications (such as Claude Buddy, Hello, and Snake) on the Cardputer-Adv device. It allows developers to add new apps, push single updated .py files without full re-flashing, monitor device serial logs, or execute one-shot REPL commands directly from the host machine. Essential for rapid prototyping and debugging embedded systems.

Manages the deployment of local applications and websites to the Vercel platform. This skill intelligently detects the project's current state (e.g., if it is already linked or if git is available) and guides the user through the optimal deployment method. It prioritizes establishing a permanent git-push connection to facilitate a seamless Continuous Integration/Continuous Deployment (CI/CD) workflow. Use when the user explicitly requests deployment actions.

This tool automates complex Git workflows to save time and reduce manual overhead. It intelligently detects and groups related code changes, automatically generates descriptive branch names (e.g., fix/auth-bug), and streamlines the entire cycle: staging, committing, pushing, and creating Pull Requests (PRs). Use it to maintain clean, consistent commit histories efficiently.

This skill automates the commit and push process for local skill changes. It should be used after a skill has been fully validated and updated, ensuring the canonical copy of the skill is published to the configured remote GitHub repository. This is essential for sharing or finalizing skill updates.

This skill guides users through evidence-based terminal operations. It is designed for scenarios requiring direct command execution, Git status checks, debugging CI/build failures, and pushing narrow, verified fixes. It emphasizes following a structured, minimal-scope workflow and accurately reporting the repository's current state (e.g., local changes vs. pushed code).

A structured tool for sending critical, warning, or informational alerts to internal teams via Slack or Intercom. Ideal for pushing campaign status updates, performance metric alerts, or formal approval requests to stakeholders. It supports advanced features like tiered urgency flagging, context embedding (IDs, metrics), and mandatory execution approval, ensuring all internal communication is documented and actionable.

This comprehensive guide details the structured method for drafting author responses to peer reviewers' comments for major conferences like AISTATS. It covers best practices for addressing statistical validity, novelty, and technical concerns in a constrained, anonymous, text-only format. Learn how to triage objections, anchor claims to existing evidence, and handle specific statistical pushback patterns.

A comprehensive guide for authors responding to IEEE ICDE peer reviews. Learn how to structure both rebuttals to initial concerns and detailed revise-and-resubmit change documents. The guide emphasizes strategic triage, anchoring answers to concrete evidence, addressing systems-level pushback (e.g., baselines, cost), and maintaining feasibility discipline within tight revision deadlines.

A comprehensive guide for drafting persuasive and structured author responses to major academic conference reviews. This methodology teaches how to triage critical concerns, anchor answers strictly to submitted evidence (tables, appendices, repository), and effectively counter common technical pushbacks such as baseline tuning, temporal data leakage, and offline-online gaps, ensuring the response is professional, anonymous, and high-impact.

Guides authors through the rigorous process of revising and responding to referee reports (R&R) for top-tier academic journals. It details how to structure the response letter, triage reviewer comments (concede, clarify, push back, decline), and ensures the revised manuscript precedes the letter. Essential for maintaining academic credibility during the publishing cycle.

The Azure CLI command group for managing Azure Container Registry (ACR). This tool allows users to perform the entire ACR lifecycle, including creating registries, authenticating credentials, building and pushing container images (using cloud builds), importing images from other sources, and configuring advanced features like geo-replication, private endpoints, and webhooks. Essential for CI/CD pipelines and container deployment workflows in Azure.

Automates the entire Continuous Integration (CI) workflow, crucial before opening a Pull Request (PR). It systematically runs local unit tests for multiple languages (Python, Node, Rust), performs type checking, pushes the current branch to the remote repository, and finally provides the direct URL and status check for the CI platform (GitHub Actions/GitLab). This single command replaces multiple manual steps.