tuicr
Review a GitHub/GitLab PR, commit range, working tree, or file in the tuicr TUI and address the annotations in code, or answer questions about tuicr usage and config. Use when the user says "tuicr", "tuicr pr <N>", "review this PR", "review PR #N", "review with tuicr", "code review TUI", "review the working tree", "review changes with tuicr", "tuicr all files", "tuicr <file>", "review this file with tuicr", "address my tuicr annotations", "read my tuicr review", "what did I annotate in tuicr", "tuicr config", "tuicr keybindings".
using-skills
Auto-loaded at session start via SessionStart hook. Teaches skill invocation protocol, tool selection rules (look-at for media, skills for workflows), agent delegation patterns, and enforcement mechanisms. NOT user-triggered - provides foundational skill usage discipline for all sessions.
visual-mockup
This skill should be used when the user asks to 'mockup the layout', 'sketch the diagram', 'show me the layout before coding', 'draft the positions', 'quick visual of the layout', 'matplotlib mockup', 'interactive mockup', 'drag and drop layout', 'draw a rough layout', 'prototype the diagram', 'let me arrange the nodes', 'mockup the chart before CeTZ', or when you're about to write a diagram with 4+ nodes or a CeTZ chart and want to confirm the visual with the user first.
visual-verify
This skill should be used when the user asks to 'verify visual output', 'check how it looks', 'render and review', 'visual verify', 'check the slide', 'does this look right', or when any task produces rendered visual output (slides, charts, documents, UI).
workflow-creator
Design, repair, or audit a multi-phase workflow. Use when the user says "create a workflow", "design a workflow", "scaffold a new workflow", "add a phase to this workflow", "improve/repair/redesign this workflow", "migrate this workflow", "audit this workflow", "why doesn''t my workflow''s gate work", "check this workflow''s gate", or "/workflow-creator". Covers all three — fresh creation, corrective improvement, and read-only audit.
workshop-constraints
ALWAYS load before writing, editing or grading ANY Typst slide deck or speaker-notes file for a workshop, seminar or conference talk - 'build the deck', 'fix this slide', 'add a diagram to the talk', 'the slide overflows', 'write the speaker notes', 'is this deck up to spec', 'grade the slides', or any .typ edit under a talk. Covers bullet and label spacing, sub-bullets, tables, images, CeTZ and Fletcher diagrams, formatting, slide format, section hierarchy, notes structure, teleprompter notes and computed values.
workshop
Academic workshop presentations — Typst slides and speaker notes built from a research paper, run through craft with a computed deck gate. Use when the user says "create workshop slides", "build the deck", "presentation from this paper", "speaker notes", "/workshop", or wants a talk taken through clarification, an approved plan, delegated slide generation, independent deck verification and human review.
wrds
Use when "query WRDS", "pull SEC filings", "access Compustat/CRSP/ExecuComp/Capital IQ", "Form 4 insider data", "13F institutional ownership (Thomson)", "13D/13G blockholders", "ISS governance/compensation/voting/directors", "proxy advisor recommendations", "TAQ intraday/NBBO", "SDC M&A or new issues", "DealScan syndicated loans", "PitchBook PE/VC deals", "FISD corporate bonds", "municipal bonds / muni trades / MSRB RTRS / SDC municipals", "Form D/ADV", "fund formation", "FJC court data", "linking datasets / join keys (gvkey-permno via CCM, cik-gvkey via wciklink, DealScan-Compustat)", or any WRDS PostgreSQL query or SAS ETL on the WRDS grid (qsub/qsas/SGE).
writing-econ
ALWAYS load BEFORE drafting, revising or grading FINANCE or ACCOUNTING journal prose — 'write the paper', 'draft the introduction of my JF submission', 'revise Section 3', 'polish the job-market paper', 'does this read like a finance paper', 'tighten the abstract', 'is this well written for JFE/RFS/JAR/TAR', 'should I write we find or the paper shows', 'do I cross-reference by Section or Part', 'is agents jargon'. Covers Journal of Finance, JFE, RFS, Journal of Accounting Research, The Accounting Review, JAE, CAR, RAST, and the working and job-market papers aimed at them. This skill carries ONLY what is additional to the base register: load `writing-general` alongside it — the diction, tic, vindicated-phrase and formatting rules live there and are assumed here. Do NOT load this for a law review article or legal scholarship (use `writing-legal`) or for a comment letter, memo, brief or professional email (`writing-general` alone) — importing a finance rule into either of those makes the prose worse.
writing-general
ALWAYS load BEFORE writing or revising any serious prose a human will read — 'write the memo', 'draft the comment letter', 'draft this section', 'polish the brief', 'revise this email', 'tighten the introduction', 'is this well written', 'review my prose', 'fix the writing here', 'make this sound less like AI', 'should I say we or the paper'. This is the BASE register: the Strunk-derived diction rules, the prohibited-construction tic table, the vindicated phrases and the formatting rules that hold for every domain, plus the register for prose that is neither a law review article nor a journal submission (comment letters, memos, briefs, white papers, board memoranda, professional email). Load it before the first sentence is written, not after. For a T14 law review article or legal scholarship carrying footnotes, load `writing-legal` ALONGSIDE this one; for a finance or accounting journal submission or job-market paper, load `writing-econ` alongside this one — those two carry only what is ADDITIONAL to this base and are useless without it.
writing-legal
ALWAYS load BEFORE drafting, revising or grading LAW REVIEW prose — 'write the article', 'draft this Part', 'revise my note', 'polish the law review piece', 'does this sound like a law review article', 'edit my seminar paper', 'is this Part well written', 'should I write This Article or This paper', 'do I cross-reference by Part or Section', 'is pursuant to legalese'. Covers T14 flagship articles, student notes, seminar papers and any legal scholarship carrying footnotes and Bluebook short forms. This skill carries ONLY what is additional to the base register: load `writing-general` alongside it — the diction, tic, vindicated-phrase and formatting rules live there and are assumed here. Do NOT load this for a finance or accounting journal submission (use `writing-econ`) or for a comment letter, memo, brief or professional email (`writing-general` alone) — importing a law review rule into either of those makes the prose worse.
writing
ALWAYS use for ANY substantial prose a human will read - "write the article", "draft this section", "outline the paper", "turn these notes into prose", "write up the memo", "draft the comment letter", "write the brief", "expand this into a chapter", "I need a few pages on X", "put this argument in writing", "/writing". Use proactively even when the user asks casually and never says "article" - do not start drafting paragraphs first. NOT for code, data work or course materials.
Page 2 of 2 · 62 results