Skill UI

This tool gathers comprehensive diagnostic evidence from an Obsidian vault. It collects details such as app versions, installed plugins, appearance settings, file statistics, and console errors into a structured markdown report. Use it when troubleshooting persistent issues or preparing detailed bug reports for developer support.

This skill guides users in systematically organizing and documenting a year's worth of past projects into the specific SRED format. It processes scattered evidence—including GitHub PRs, Notion documents, and Linear tickets—to evaluate project suitability, generate comprehensive descriptions, and create structured, standardized reports within Notion. Ideal for formal academic submissions or professional portfolio creation.

Draft, revise, and audit scientific manuscripts and reports with rigorous evidence provenance, authorship accountability, and confidentiality controls. This tool ensures every factual claim is traceable to verified evidence, making it essential for high-stakes academic writing, journal submissions, and regulated research reporting where accuracy and compliance are non-negotiable.

This skill restructures AI-generated content to maximize cognitive accessibility, specifically optimized for users with ADHD or neurodivergence. It uses evidence-based techniques such as chunking, visual hierarchy, front-loading key points, and progressive disclosure. It offers three distinct modes (clean, flow, zen) to tailor the output structure, ensuring that complex information is highly digestible and easy to follow.

This skill functions as an optional agent companion for MDPR, a deterministic Markdown-to-presentation runtime. It helps review presentation workflows by providing semantic hints, visual evidence reports, and high-level layout intentions. Crucially, it keeps agent output evidence-based while letting MDPR maintain control over final slide geometry, rendering details, and layout coordinates.

Guides builders to verify task delivery by collecting required evidence such as CLI output, screenshots, or DOM snapshots, then submitting artifacts for review. Useful when a task must self-certify against a verify plan.

A comprehensive project management guide for submitting academic papers to the AAMAS conference. It details all critical milestones, including venue fit, evidence locking, abstract submission, double-blind review, rebuttal, and final camera-ready preparation. Essential for managing complex research involving game theory and multi-agent systems.

This skill acts as the primary orchestrator for any American Historical Review (AHR) manuscript. It guides users through the entire academic writing lifecycle, determining the next necessary step based on the project stage. From developing a significant historical question and gathering primary sources to structuring the argument, refining prose, and managing citations, it ensures the focus remains on deep historiographical evidence and interpretation.

This skill is designed to polish and refine academic manuscripts intended for the American Historical Review (AHR). It focuses on enhancing the clarity, narrative flow, and authoritative voice of the prose, ensuring the work is accessible and engaging for historians across all subfields. It tightens the overall readability, minimizes unnecessary jargon, and helps frame evidence without altering the core arguments or academic content.

A comprehensive project management guide for the entire academic lifecycle of submitting a paper to a top-tier conference like AISTATS. It maps all crucial milestones—from initial venue fit and evidence freezing to abstract submission, review discussion, and final camera-ready publication—providing backward-planning heuristics and risk assessment to ensure timely and high-quality submissions.

This workflow router serves as the central orchestrator for academic articles submitted to art history journals. It guides authors through the complex, multi-stage publishing lifecycle, from initial topic selection and scholarly positioning to visual analysis, evidence gathering, and final submission. Crucially, it proactively manages the often-overlooked and time-consuming process of image rights and permissions, ensuring authors do not delay this critical step until the end.

A comprehensive guide detailing the complex, multi-stage workflow for submitting a systems paper to a major academic conference (like ASPLOS). It maps out timelines across two submission gates, revision cycles, hardware evidence gathering (T-8 to T-2), and critical role assignments required to successfully navigate the intense academic publication process.