Skill UI

This guide details the meticulous process of converting an accepted PLDI conference paper into a formal PACMPL journal article. It covers crucial steps including de-anonymization (restoring author details, ORCIDs), adopting journal formatting standards, handling digital artifacts on Zenodo, managing open-access rights, and coordinating the three distinct deliverables: the article, the artifact, and the presentation talk.

This guide details the standards for submitting theoretical computer science papers, focusing on the required "formal-claims package." It emphasizes that the deliverable is not a runnable systems artifact, but a rigorous academic package containing a complete, self-contained proof appendix, a clear mapping of every stated claim to its proof location, and a full, publicly available version on arXiv.

This guide outlines the methodology for crafting a comprehensive, point-by-point rebuttal to a journal's decision letter. It teaches authors how to transform abstract reviewer critiques into concrete, auditable deliverables, such as formal derivations, new simulation cells, or empirical illustrations. The focus is on providing undeniable evidence for every claim to maximize the chances of publication acceptance.

A comprehensive guide for theoretical computer science authors on converting an accepted paper into two distinct, public deliverables: a concise, citable proceedings version (extended abstract) and a comprehensive, full version for public preprint servers like arXiv. Details the formatting, copyright requirements, version control, and post-publication hygiene necessary for academic publishing.

Turn interpretive-ambiguity audits of legal texts into polished deliverables: multi-page websites, single-page interactive sites, Word documents, PowerPoint decks, or LaTeX/PDF. Handles structured stress-test output, semi-structured reports, or raw prose, and renders consistent scenario-based legal analysis presentations.

Toolkit for comprehensive reading, editing, and creating Word documents (.docx) with visual quality control. Use for extracting content, precise typography, tables, diagrams, layout validation, and producing professional deliverables.

Restructures any vague build, research, or legal-drafting request into a highly structured IRAC (Issue, Rule, Analysis, Conclusion) prompt. This method optimizes output quality for frontier models by forcing the definition of constraints, underlying rules, required reasoning, and precise deliverables, moving beyond simple prompting.

This skill generates highly structured, consistently formatted legal documents in Word (.docx). It handles complex document architecture—including multi-chain numbering, structured recitals, and defined terms—for various document types like agreements, memos, and policies. It is designed for in-house legal teams needing a professional, jurisdiction-agnostic house style across all legal deliverables.

An advanced, automated pipeline designed for comprehensive, deep-dive Open Source Intelligence (OSINT) gathering and reconnaissance against authorized domains. It executes the full methodology—from passive data harvesting and subdomain discovery to multi-agent content fan-out, vulnerability identification (BOLA/IDOR), and automated findings generation. The output is a single, consolidated, multi-tab deliverable (XLSX), eliminating the need for manual follow-up or superficial reporting.

A comprehensive toolkit designed for reading, reviewing, and programmatically creating high-fidelity PDF documents. It supports content extraction from existing PDFs, generating professionally formatted reports, and validating visual quality through rendering to PNG images. Ideal for tasks requiring precise typography, layout integrity, and polished final deliverables.

Plan commits as reviewable work units to improve code quality and review efficiency. This skill helps split large features into manageable chunks, prepare commits before opening PRs, and maintain tests and documentation alongside code changes. It ensures each commit represents a clear deliverable behavior, reducing reviewer cognitive load and supporting chained PRs for larger changes.

Generates structured technical deliverables from completed analysis tasks, including reverse-engineering reports, penetration-test reports, CTF write-ups, and signature-analysis documentation with evidence-backed structure and standardized templates.