Skill UI

This comprehensive preflight checklist guides authors through the final submission requirements for academic journals, specifically targeting the Perspectives on Psychological Science (PoPS) format. It ensures compliance with critical standards including abstract word limits (200 words), APA formatting, open science data deposits, ethical declarations, and objective reviewer nominations. Use this before submitting to any scholarly portal.

This guide helps researchers determine if their academic idea is suitable for publication in Perspectives on Psychological Science (PoPS). It evaluates contributions against four critical criteria—Breadth, Integration, Provocation, and Tractability—ensuring the topic is a superordinate, theoretical, or meta-scientific argument, rather than a single empirical study. It helps refine the animating question and select the correct journal venue.

This router guides researchers through the complex, multi-stage lifecycle of writing a broad, integrative, or theoretical 'perspective' article for high-impact journals like PoPS. It dictates the next necessary scholarly skill (e.g., literature synthesis, framework building, editor strategy, revision) based on the manuscript's current stage, helping authors transition from initial concept to final submission and revision.

A comprehensive guide for producing the mandatory supplementary video figure for UIST submissions. This material treats the 3-minute video as core evidence, detailing requirements for resolution (1080p/4K), codec (H.264), and anonymity. It guides authors on scripting the video around key claims, ensuring uncut interaction loops, and maintaining academic rigor to convince reviewers of the system's reality.

This guide outlines best practices for structuring supplementary materials for OOPSLA submissions. It emphasizes the 'layering decision,' ensuring the core body can stand alone while appendices provide necessary proofs and technical details. It covers maintaining double-anonymity across all included content and performing crucial cross-checks for consistency across multiple review rounds.

Scans your local machine's Git history to locate abandoned or unfinished side projects. It performs a deep 'autopsy' on these repositories, determining their causes of death (e.g., deployment fear, killed by newer ideas) and identifying personal developmental patterns. The tool then surfaces the most promising candidate for resurrection, helping you finally ship it.

This specialized skill is designed to analyze complex security flaws involving forced authentication (coercion) and identity relay chains. It guides users to trace and document the complete, minimal path from the initial coercion trigger (e.g., a specific service or protocol edge) through intermediate hops, to the final service that accepts the relayed credentials. Use this for deep security research, forensics, and documenting the decisive sequence leading to privilege escalation or code execution.

This advanced skill is designed for security research and CTF environments to trace subtle divergences in request handling across multiple network hops (proxies, gateways, backend servers). It focuses on identifying vulnerabilities stemming from differential interpretation of headers, path normalization, transfer framing (CL/TE), and host derivation, crucial for detecting request smuggling and parsing inconsistencies.

This skill implements a critical CI gate to ensure the privacy and performance integrity of de-identification models. It automatically fails the build if the model's recall on held-out PHI data drops below the defined threshold, or if any critical Personally Identifiable Information (PHI) is leaked (leakage must be zero). It enforces strict privacy standards in continuous integration pipelines, blocking unsafe merges.

This tool analyzes a given codebase to automatically identify high-value, actionable automation routines. It surfaces use cases across three primary trigger types: scheduled cron jobs, external API calls, and GitHub repository events. By mapping manual pain points to autonomous workflows, it helps teams implement robust CI/CD and DevOps practices.

A comprehensive methodology for diagnosing complex systems where problems are emergent across multiple components. It guides the user to map system boundaries, stocks and flows, feedback loops, and underlying structural drivers. By identifying the highest feasible leverage point, it recommends structural interventions that address root causes rather than superficial symptoms.

Adds an Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making Azure DevOps REST API calls. Includes steps to apply a required HttpRequest body parameter fix, configure operations, build, and update the memory bank.