Explore skills
Showing 13081–13110 of 40492 skills
Commit changes, push to remote, and create a pull request. Use for completing features or fixes ready for review.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexImplements the Spec-Driven Development lifecycle (Intent, Requirements, Design, Tasks, Build) for structured feature development. Use when the user wants to scaffold a new feature spec, generate EARS requirements, create a technical design, break work into tasks, or check spec status. Trigger on keywords: sdd, spec-driven, ears requirements, feature spec.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexFind and fix technical debt including duplicated code, dead code, outdated patterns, and code smells. Run at the end of sessions to clean up.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRender Quarto slides and sync to docs/ for GitHub Pages deployment. Use when deploying lecture slides after making changes.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRun the proofreading protocol on lecture files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexTranslate Beamer LaTeX to Quarto RevealJS. Multi-phase workflow with TikZ extraction and QA.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexSystematic audit and review by Referee 2. Two modes — "deck" reviews slide presentations for rhetoric, visual quality, and compile cleanliness; "code" performs cross-language replication and econometric audit of empirical pipelines. Use when reviewing slides, auditing code, or verifying replication.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexChallenge research design decisions, assumptions, and methodology choices with specific critical questions. Helps strengthen the paper before submission.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexStructured literature search and synthesis with citation extraction and gap identification.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRun the proofreading protocol on manuscript files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexGenerate structured research questions, testable hypotheses, and empirical strategies from a topic or dataset.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRun the Julia code review protocol on Julia scripts. Checks code quality, type stability, parallel computing patterns, and scientific computing standards. Produces a report without editing files.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexComprehensive manuscript review covering argument structure, identification strategy, econometric specification, citation completeness, and potential referee objections.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRun the proofreading protocol on academic writing — papers or manuscripts. Checks grammar, typos, layout issues, consistency, and academic writing quality. Produces a report without editing files. Make sure to use this skill whenever the user wants surface-level writing errors found — not substantive academic critique. Triggers include: "proofread", "check for typos", "grammar check", "look for errors in my draft", "proofread all", "polish this", "check my writing", "are there any mistakes", "proofread before I send this", or when the user wants a clean-up pass rather than feedback on arguments or methods.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRun the R code review protocol on R scripts. Checks code quality, reproducibility, domain correctness, and professional standards. Produces a report without editing files. Make sure to use this skill whenever the user wants their existing R code evaluated or audited — not when they want new analysis written. Triggers include: "review my R script", "check my R code", "is my code replication-ready", "audit this R file", "does this code follow conventions", "will this reproduce", "check my analysis script", "code review", "review-r", or when the user has an existing .R file and wants quality feedback rather than new code.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexR&R cycle — classify referee comments and route to appropriate agents. Replaces /respond-to-referee.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexSubmission pipeline — journal targeting, replication package, audit, and final gate. Replaces /submit, /target-journal, /audit-replication, /data-deposit.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexDraft academic paper sections with notation protocol, anti-hedging, and humanizer pass. Replaces /draft-paper and /humanizer.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexStrategic research leadership for designing high-impact research agendas, coordinating teams, and translating research into policy and institutional influence.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRedistricting analysis in R using the redistverse ecosystem. Use whenever the user is working with redist, redistmetrics, ggredist, geomander, adj, alarmdata, PL94171, censable, easycensus, tinytiger, baf, rict, or redistio. Covers the complete pipeline: Census and spatial data loading, adjacency graph construction, SMC/MCMC simulation, constraints (population balance, county splits, VRA compliance), convergence diagnostics, plan metrics (compactness, partisan fairness, splits), visualization, summary tables, and interactive plan drawing. Invoke whenever the user mentions redistricting, gerrymandering, district plans, simulation ensembles, or any redistverse package by name.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexRun the proofreading protocol on lecture files. Checks grammar, typos, overflow, consistency, and academic writing quality. Produces a report without editing files.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexCross-checks citation keys in index.qmd against references.bib, reporting missing, orphaned, and duplicate entries. Use when verifying citations.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexFinds a paper by title, author, or DOI, adds BibTeX to references.bib, and shows citation syntax. Use when adding a reference.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexAuto-generates a Markdown codebook from a dataset (CSV, DTA, Excel, Parquet) with types and summary statistics. Use when documenting variables.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexScans notebooks for data file references and verifies each file exists on disk. Use when checking for broken data paths.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexDrafts academic prose for a manuscript section from bullet points or an outline. Use when writing or expanding a section.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexGenerates an HTML gallery of all project figures with captions and source notebooks. Use when reviewing figures.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexWrites academic prose interpreting regression output. Use when describing estimation results in manuscript-ready language.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexThis skill should be used when the user asks to co-author documentation, draft a proposal, write a technical spec, create a decision doc or RFC, or structure a substantial document through iterative collaboration and reader testing.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodexUse this skill when the user discusses experiment design, ablations, training runs, evaluation, baselines, metrics, failures, or result interpretation that should be logged into Obsidian experiment and result notes.
brycewang-stanford/Auto-Empirical-Research-Skills
Stars: 5kClaude CodeCodex