Skill UI

This skill applies Steve McConnell's construction rules to software development tasks. It covers routine design, variable usage, class design, control flow, defensive programming, coding standards, and testing. Use it for disciplined software construction to ensure high-quality code implementation.

This skill enforces strict communication protocols for AI agents interacting in shared channels with external parties. It ensures agents speak only when explicitly addressed, prevents internal context leakage, and routes sensitive content to draft-only approval. Ideal for group chats, DMs, and business partnerships where privacy and security are critical.

Apply Martin Kleppmann-inspired rules for designing reliable, scalable, and maintainable data systems. Covers consistency, replication, partitioning, transactions, streams, batch processing, and schema evolution. Use when making architecture decisions for data-intensive applications.

Apply lightweight Domain-Driven Design rules for bounded contexts, subdomains, and tactical modeling without unnecessary ceremony. Ideal for practical software architecture guidance and design decisions in complex systems.

Apply Martin Fowler-inspired enterprise architecture rules when choosing layers, service layers, transaction scripts, domain models, repositories, mappers, or DTOs. Helps structure enterprise applications with proven patterns.

This skill performs pharmacokinetic and pharmacodynamic modelling, including non-compartmental analysis, compartmental fitting, and population PK. It helps derive exposure metrics, evaluate dosing regimens, and predict drug interactions using Python scripts. Suitable for analyzing concentration-time data and supporting clinical pharmacology workflows.

This skill provides a stable standalone fixture for Qoder, allowing users to inspect the active project using standard QwenPaw tools. It is designed for developers to verify project status and structure without external dependencies. Ideal for debugging and project analysis tasks.

This portable skill enables the AI to utilize standard file tools to examine and analyze the current project structure. It allows for inspecting code files, configuration settings, and documentation directly within the workspace. This fixture skill ensures stability and reliability when performing file-based operations during development tasks.

This skill applies Refactoring.Guru-inspired rules for diagnosing code smells and selecting appropriate refactoring techniques. It helps preserve behavior while avoiding uncontrolled redesign. Before making design or code decisions, read the mini rules first. Use the full guide only as a deeper reference when needed. It ensures targeted cleanup without over-engineering.

Apply Michael T. Nygard-inspired production reliability rules when designing failure handling, timeouts, retries, circuit breakers, observability, or deployment behavior.

This skill helps maintainers verify reported bugs in the mcp-toolbox project. It involves analyzing issue reports, checking versions and configurations, and attempting local reproduction to determine if the bug is real, fixed, or misconfigured. The process requires citing specific evidence like file paths and commit SHAs to support verdicts such as confirmed, already-fixed, or client-side issues. It ensures efficient bug triage without unnecessary infrastructure setup.

Sweeps googleapis/mcp-toolbox for issues and PRs with no real activity in N days, classifies each silence as the author's, maintainer's, or nobody's, and drafts nudge or close comments for maintainer review only.