Skill UI

This guide provides a comprehensive overview of the rate limits imposed by the MindTickle API across various endpoints, such as user management, content upload, and quiz result exports. It details specific limits for different operations and provides robust engineering solutions using TypeScript. Key implementation strategies include implementing a token-bucket rate limiter, developing a retry mechanism with exponential backoff, and optimizing bulk data processing through batching to ensure stable and efficient application integration.

This skill generates a complete and detailed specification for an ETL/ELT data pipeline. It covers everything from source systems, transformation logic, and data quality rules to destination data warehousing and required SLAs. Use this when planning data ingestion, designing complex data flows, or needing comprehensive architecture documentation for engineering handoff.

This skill generates comprehensive, production-ready database schema documents. It covers Entity-Relationship (ER) diagrams, detailed SQL DDL definitions, constraint analysis, index strategies, and access pattern optimization. Use it when designing a new database, documenting an existing one, or modeling complex data relationships for engineering review.

This skill generates a comprehensive technical debt register for any team or service. It guides users to input critical data points (e.g., business impact, effort, tech stack) and produces a structured report that categorizes debt (Architecture, Security, Testing, etc.). The output includes a calculated priority score and a quarterly debt reduction roadmap, enabling deliberate, business-aware engineering decision-making.

A comprehensive template designed to structure complex technical specifications, ensuring a complete record of engineering decisions. It guides users to document problem statements, proposed solutions, system architecture, data models, API designs, security considerations, and rollout plans, bridging product requirements and technical implementation.

This skill helps transform vague product or engineering ideas into structured, verifiable acceptance criteria (AC). It is crucial for high-impact changes involving security, data migration, or external APIs. By inspecting existing context and asking minimal, targeted questions, it produces clear, observable criteria, significantly de-risking the development process and ensuring handoff readiness.

This skill helps optimize and verify latency-sensitive systems such as real-time dashboards, market data feeds, and streaming agents. It involves tracking p50/p95/p99 latency, freshness age, and queue depth. You will map hot paths and run live readbacks to ensure performance. Use this when throughput or data freshness matters in engineering contexts.

A comprehensive guide for researchers and reviewers designing or auditing Automated Software Engineering (ASE) evaluations. It outlines the necessary rigor, including the use of real subject systems, establishing fair and runnable tool baselines, performing targeted ablations (especially for LLMs), defining explicit oracles, and ensuring full data and model provenance to guarantee reproducible and scientifically sound results.

A comprehensive guide for researchers submitting to ASE (Automated Software Engineering). It details mandatory requirements for ensuring research reproducibility, covering the Data Availability Statement, providing anonymized and runnable tools, pinning system provenance (commits, versions, SHAs), and managing cached LLM outputs. Essential for passing rigorous peer review.

A comprehensive guide for authors targeting the IEEE International Conference on Data Engineering (ICDE). This skill helps assess venue fit, re-frame manuscripts from journal/arXiv styles, and structure papers for top CS conferences. It details required evidence (system architecture, realistic workloads) and best practices for positioning contributions in data engineering, database systems, and analytics.

This specialized skill provides a deep workflow for reverse engineering stripped Go and Rust binaries. It guides the recovery of lost runtime metadata, including symbols, pclntab data, and panic strings. The process addresses language-specific challenges, such as Go's interface structures and Rust's complex async state machines, serving as a crucial complement to general decompilers like IDA or Ghidra.

This gate review forces a transition from vague product direction to a concrete, buildable technical specification. It mandates the creation of architectural diagrams, data flow maps, state machines, and failure mode inventories before a single line of implementation code is written. Essential for complex features with async components or external dependencies.