claude/skills/research/SKILL.md
Delegate research and context-gathering tasks to a sub-agent to protect the primary context window. Use when the user asks to "research X", "look into X", "find out about X", "gather context on X", or any investigative framing where answering requires 2+ searches or multiple sources. Also use proactively before starting substantive work when prior context is unknown. Never run research inline — always delegate.
npx skillsauth add lanej/dotfiles researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Delegate all research to a sub-agent. The primary agent receives a synthesized result, not raw search output.
Delegate any research task that:
Single targeted lookups (one grep, one file read, one known query) can run inline.
The sub-agent should work through these sources in order, stopping when it has sufficient confidence:
qmd query --no-rerank "<query>" — prior analyses, domain docs, BQ data dictionary, strategy, headcount, customer contextmcp__bigquery__query — live warehouse data; always dry_run firstmcp__jira__jira_issues_search JQL — ticket status, project decisions, delivery contextmcp__codex__codex — external docs, standards, anything not internalEvery Agent tool call for research must include:
Context: [What the overall question is and why it matters — 1-2 sentences]
Question: [The specific research question to answer]
Sources: [Which layers of the research protocol to check, in order]
Output: Synthesized summary — findings, gaps, and confidence level. Under 300 words unless the question demands more detail. No raw search output.
The sub-agent returns a synthesized summary. The primary agent then:
If the sub-agent reports gaps or uncertainty, surface those explicitly before proceeding.
documentation
--- name: qmd-math description: Math notation conventions for Quarto/EPQ documents rendered via lualatex. Use when: writing or adding a formula, equation, or mathematical expression to a .qmd file; asked about display math, inline math, or LaTeX notation in a QMD/Quarto context; defining a where-clause or variable definitions for an equation; converting prose variable descriptions into structured math notation; fixing math that renders badly in a PDF; using \lvert, \begin{aligned}, \tfrac, \text
development
Trim a prose document (README, design doc, blog post, notes) for readability by cutting redundancy, filler, and dead weight in the author's own words. Invoke with /trim [file path], or /trim alone to be prompted for a file. Not for source code, data files, or summarization.
business
Query and analyze Josh Lane's org headcount from the staffing DuckDB at ~/workspace/areas/staffing/staffing.duckdb. Use when asked about headcount counts, org structure, direct reports, team breakdown, hiring/attrition trends, international employees, salary/pay grade distribution, offboarding lag, or any question about people in Josh's org. Triggers on questions about how many people, who reports to whom, headcount by team/country/level, who joined or left, org size, staffing, headcount trend.
tools
Figure engineering patterns, gotchas, and reusable helpers for matplotlib. Use when directly building standalone figure scripts, diagram generators, or canvas visuals outside the epq render pipeline — e.g., generate_layer_icons.py, vision project banners, morning-brief charts, competitive analysis figures. Covers shape boundary math, arrow/edge geometry, series consistency, font registration, zorder, Unicode rendering, and canvas clipping. Distinct from the epq skill (which covers the Quarto/LaTeX analysis pipeline). Load alongside epq when figure work involves both the pipeline and standalone diagram construction.