Claude Skills by edwinhu

This skill should be used when the user asks to 'create a plugin', 'scaffold a plugin', 'set up plugin structure', 'new plugin', 'edit the plugin manifest', 'wire plugin hooks', 'validate plugin structure', 'audit my plugin's enforcement', or needs plugin-level work spanning multiple components. Use proactively whenever plugin.json, marketplace.json or hooks/hooks.json is being edited, even if the user never says 'plugin'. NEGATIVE ROUTING: never invoke plugin-dev:create-plugin, plugin-dev:pl...

Use when the user asks to "render pptx", "show pptx slide", "compare with pptx", "pptx to image", "export pptx slide", "original slide", "show me the original", "what does the pptx look like", or needs to extract a specific PPTX slide's content for visual comparison.

Use when the user asks a QUESTION of their reading library rather than for a keyword lookup — 'ask readwise', 'chat about my highlights', 'what do my notes say about X', 'summarize my reading on X', 'what have I read about proxy advisors', 'compare what I've read about X vs Y', 'what's my take on X based on what I've read', 'pull together my highlights on X'. Use proactively for synthesis across many documents. NOT for finding a specific highlight by keyword — use readwise-search instead.

Use when the user says 'add to reader', 'save this article', 'read this later', 'put this in Readwise', 'list my documents', 'what's in my reading inbox', 'archive that article', 'tag this document', or 'delete that from Reader' - anything that lists, saves, updates or deletes documents in the Readwise Reader library. NOT for searching highlights (readwise-search) and NOT for bulk cleanup of stale documents (readwise-prune).

Clean up stale Readwise Reader documents. Use when the user wants to declutter their reading library, remove old unread articles, or manage Reader inbox. Triggers on "clean up readwise", "prune reader", "delete old articles", "declutter reading list".

ALWAYS use when the user wants something out of their own reading library — "what did I highlight about X", "search my highlights", "find in readwise", "my notes on X", "did I save anything on Y", "what have I read about Z", "find that quote I saved", "pull quotes from my reading", "who was it that said X". Use proactively before answering from memory whenever the user refers to their own reading or annotations. NOT for conversational summarizing across highlights (readwise-chat), listing or ...

ALWAYS use for ANY query against the user''s own reading library — "search Readwise", "find highlights", "what did I highlight about X", "get quotes from my reading", "search my annotations", "find that thing I saved about Y", "pull the full text of that article", "what do my notes say on this", "add my highlights to a notebook", "add tagged documents to notebook". Use even when the user never says "Readwise" but is asking about something they read or saved. NOT for web or academic search — t...

ALWAYS use when code and data have to leave the machine as a self-contained archive for someone who did not write them — 'build the replication package', 'package this for counsel', 'send the workpapers', 'production archive for the opposing expert', 'replication archive', 'they want the code and data', 'put together what they asked for in the document request', 'make a workbook for the client', 'archive this analysis so someone else can check it', 'write the runbook', 'they need to be able t...

ALWAYS use for ANY request to find academic papers - "find papers on X", "what does the literature say about X", "is there research on this", "who has written about X", "find me cites for this claim", "literature search", "any papers in the journals I like", "top journals only", "recent work on X", "has anyone studied this". Use proactively before answering an empirical or doctrinal question from memory, and never run scholar/consensus/paperpile by hand in sequence - this skill parallelizes t...

Use when the user says \"set up workflows\", \"workflows setup\", \"is workflows installed correctly\", \"verify my install\", \"check the workflows install\", \"why isn't my agent's guidance loading\", \"my agent dispatch got denied\", \"/setup\", or asks whether this plugin's agents, their preloaded skills and the main-thread guard's allowlist actually resolve on this machine. Use proactively right after installing or updating the plugin — a preload that fails to resolve is logged to the de...

This skill should be used when the user asks to 'create a skill', 'improve a skill', 'edit a skill', 'add a skill to a plugin', 'add enforcement patterns', 'add Iron Laws or fact rows', 'fix a skill description', 'audit skill enforcement', or needs to substantially create or edit any SKILL.md file — including a single skill inside a plugin. Use plugin-creator only for plugin-level work (manifest, hooks wiring, multi-component scaffolding).

Use when the user says 'verify my sources', 'check the citations', 'fact-check the footnotes', 'are my cites real', 'did I make this cite up', 'does the source actually say that', 'check this quote against the source', or 'source check before I submit'. Use proactively whenever a draft's citations or quotations have not been checked against the actual sources. NOT for Bluebook formatting - use bluebook or bluebook-audit.

This skill should be used when the user asks to 'test a slide', 'isolate a slide', 'debug a slide', 'preview a single slide', 'test this slide', 'render one slide', or when you need to visually verify a single Typst slide from a presentation in isolation. Provides the exact file setup pattern to avoid access-denied and import errors.

Review a GitHub/GitLab PR, commit range, working tree, or file in the tuicr TUI — and read the user's annotations back out of the session — 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\", \"tuicr all files\", \"tuicr <file>\", \"address my tuicr annotations\", \"read my tuicr review\", \"what did I annotate in tuicr\", \"tuicr con...

Use when the user asks to 'scrape Lex Machina', 'capture Bloomberg Law results', 'get all the search results', 'export more than the row cap', 'the export only gives me 1,000', 'pull the whole docket', 'grab every page of results', 'capture the JSON behind this page', 'page through this site and save the data', or wants the full result set out of an authenticated research UI (Lex Machina, Bloomberg Law, Westlaw, Docket Alarm, UniCourt) whose export is capped or absent. Also use when a site's ...

Use when a session's stopping condition is being written or repaired — \"set the stopping condition\", \"hold it until the tests pass\", \"what should the objective be\", \"give it something to work toward before I go to bed\", \"write the brief for the spawned agent\", \"it stopped overnight\", \"it idled while I was asleep\", \"it asked me a question instead of continuing\", \"why did it stop\", \"is the hold actually armed\", \"make it keep working\", \"run this unattended\", \"leave it ru...

Injected verbatim into every session by hooks/session-start.ts. Nothing triggers on this description — both invocation paths are off below.

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.

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).

Use when "scrape this site at scale", "fetch N thousand pages", "how many workers should this scraper use", "am I hammering this server", "we're getting 429s / blocked / CAPTCHAs", "should we use a proxy", "Zyte", "ScrapingBee", "Web Unlocker", "residential proxy", "rotate proxies", "scrape with Web Unlocker", "query Bright Data", "Bright Data datasets", "Bright Data Web Archive / Wayback alternative", "FINRA BrokerCheck data", "SEC IAPD / adviserinfo data", "Investment Adviser Public Disclos...

Use when the user says 'get this case from Westlaw', 'export the case as Word', 'download the opinion', 'pull 87 F.3d 536', 'I need the Westlaw version', 'get me the real text of this case', or 'the OCR is garbled, get the publisher text'. NEGATIVE ROUTING: excerpting an opinion already in hand into a course reading is workflows:elide-case; free case law with no subscription is workflows:courtlistener. This skill only retrieves and exports from Westlaw.

Use when the user says \"work this\", \"run a work loop\", \"craft this\", \"do this properly\", \"take this through clarify plan and verify\", \"run it through the gate\", \"/work\", \"/craft\", or hands over a substantial change that has no domain workflow of its own and should be planned, approved and independently verified before it lands. NEGATIVE ROUTING: a code change or bug fix is /dev; a dataset, table, figure or number is /ds; long-form prose is /writing; a talk built from a researc...

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", "the gate passes when it shouldn''t", or "/workflow-creator". Covers all three — fresh creation, corrective improvement, and read-only audit. Use proactively when ...

ALWAYS use when the deliverable is a research talk - Typst slides and teleprompter speaker notes built from a paper. Use when the user says \"create workshop slides\", \"build the deck\", \"make slides for my paper\", \"presentation from this paper\", \"write the speaker notes\", \"I'm presenting this at a seminar\", \"turn the paper into a 40-minute talk\", \"I have a workshop next week and nothing to show\", or \"/workshop\". Use proactively whenever a conference, seminar, job talk or brown...

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", "li...

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 Accoun...

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...

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 fo...

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.