From mats
This skill should be used when the user asks about MATS policies, procedures, or information - including compute access, housing, illness policy, reimbursements, mentor meetings, program schedule, Lighthaven, or any other MATS cohort logistics. Trigger phrases include "MATS handbook", "how do I get compute", "MATS housing", "illness policy", "MATS schedule", "Lighthaven", "where is Lighthaven", or questions about MATS program operations.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mats:fellow-handbookThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Answer questions about the MATS Winter 2026 fellow handbook.
Answer questions about the MATS Winter 2026 fellow handbook.
Important: Use curl via Bash, not the built-in Fetch tool. Save the output to a temp file for efficient searching.
curl -s "https://firecrawl.alignment-hive.com/api/notion?url=https%3A%2F%2Fmatsprogram.notion.site%2Fmats-winter-26-fellow-handbook" -o /tmp/mats-handbook.md
Use Grep to find headings and keywords related to the user's question:
Grep pattern="^#|<keyword>" path="/tmp/mats-handbook.md"
Thoroughness is critical. Read all potentially applicable sections, even tangentially related ones.
Use the Read tool to read the relevant sections (or the whole file if appropriate).
If the handbook links to other Notion pages with additional details (e.g., Compute Docs, Community Health Policy), fetch those linked pages:
curl -s "https://firecrawl.alignment-hive.com/api/notion?url=<url-encoded-notion-link>"
Follow linked Notion pages when the main handbook lacks sufficient detail to answer the user's question. Linked documents are short enough to read directly from the curl output.
Present the response in two clearly separated sections:
Quotes from the handbook:
[Quote 1 with section header]
[Quote 2 with section header]
Interpretation:
[Summary and interpretation of how the quotes answer the user's question. Include any caveats about information that may be outdated or incomplete.]
npx claudepluginhub crazytieguy/alignment-hive --plugin matsMinerU Document Explorer — Agent-native knowledge engine. Use when users ask to search their documents, look up information in PDFs/DOCX/PPTX/Markdown, navigate inside large documents, extract tables/figures, or build wiki knowledge bases. Provides three tool groups: information retrieval (query, get, multi_get, status), document deep reading (doc_toc, doc_read, doc_grep, doc_query, doc_elements, doc_links), and knowledge ingestion (wiki_ingest, doc_write, wiki_lint, wiki_log, wiki_index).
Documentation-only search via context_search_documentation. Use this instead of context_research when you want docs — wikis, READMEs, runbooks, API references, architecture docs, ADRs, and onboarding guides — without Slack, PR, or issue noise mixed in. TRIGGER when: looking for setup or configuration instructions; finding a runbook or operational procedure; understanding an API contract or event schema; locating an architecture decision record or design doc; the user asks "is there docs for X", "how do I set up Y", "is this documented", or "find the runbook for Z". DO NOT TRIGGER when: you need the current code state — use Grep/Glob/Read; you need Slack threads, PRs, or issues alongside docs — use context_research instead.
Investigates questions against high-trust primary sources (docs, source code, specs) and writes cited Markdown findings to a project conventions file.