Skill UI

This comprehensive guide walks authors through the rigorous academic review process, specifically referencing the Strategic Management Journal (SMJ). It teaches how to correctly interpret complex decision letters (e.g., Major Revision, Desk Reject), understand the roles of action editors and reviewers, and systematically identify critical concerns (such as contribution to theory or endogeneity). Use this skill when you need to structure a detailed revision plan and write a convincing rebuttal letter to a top-tier academic journal.

This guide clarifies the role of computation in theoretical computer science submissions, particularly for venues that prioritize theorems over empirical data. It distinguishes between legitimate forms of evidence—such as certified proof steps, constructive object discoveries, and illustrative examples—and inappropriate performance benchmarking. It helps researchers structure their work to align with theorem-based research, ensuring computational elements enhance the core theoretical contribution.

A comprehensive model detailing the rigorous evaluation process for submissions to STOC (Symposium on Theory of Computing). It covers the committee structure, the roles of program committee members and external subreviewers, the key evaluation axes (Correctness, Significance, Breadth, Novelty), the typical timeline, and strategic advice for authors on maximizing their leverage throughout the double-blind review process.

This skill assists software engineers through the entire technical job search cycle. It provides structured analysis for job descriptions (identifying must-haves, red flags), optimizes CVs for specific roles, guides writing compelling cover letters, evaluates total compensation packages, and crafts professional post-interview follow-up emails, ensuring the job search process is professional and highly targeted.

A comprehensive project management layer designed for navigating the entire academic conference lifecycle. It guides authors through critical phases, including topic selection, paper drafting, rigorous review response, camera-ready submission, and final presentation. The workflow emphasizes meticulous planning, role assignment, and maintaining academic integrity to prevent common project failures.

This is the master workflow for complex security competitions, including CTF, reverse engineering, cloud, pwnable, and forensics. It establishes a controlled sandbox model, treating user-presented targets as internal fixtures by default. The orchestrator's role is to map the entry surface, prove one minimal end-to-end path, and intelligently route the investigation to the most relevant specialized analysis skill or reference material.

This command acts as a crucial product gate, forcing a deep, strategic review before any code is written. Instead of simply fulfilling the request, it guides users through three structured roles: Scope Expansion (finding the 10x vision), Hold Scope (stress-testing assumptions and failure modes), or Scope Reduction (defining the true MVP). It ensures that the developed solution solves the user's real job-to-be-done, not just the explicit feature request.