Research & Data

Use Slashy MCP for connected Gmail or Outlook mail, Google or Outlook Calendar, contact research, meeting prep, reminders, and scheduled workflows. Covers connection setup, tool conventions, deep links, and attachments.

Use when code review feedback has arrived and needs a decision before any fix - a cr-request result, pull request comments, CI or static-analysis review output, or a reviewer's message - in any programming language. Verifies each finding against the current code, decides accept, reject, partial, defer, or escalate with evidence, fixes only what holds up, and reports per finding.

SQL-миграции PostgreSQL: парные up/down-файлы, современные типы и ограничения (identity, text с CHECK, timestamptz, jsonb), откат каждой операции, добавление значения в enum, индексы на живых таблицах через CREATE INDEX CONCURRENTLY без блокировки записи, что требовать от мигратора, разбор «индекс создан, а план — Seq Scan». PostgreSQL migrations: paired up/down files, modern types, reversible changes, non-blocking indexes, migrator requirements.

Как найти, что тормозит в PostgreSQL, и доказать, что правка помогла. Профиль по pg_stat_statements, сравнение вариантов по числу страниц (BUFFERS), а не по секундам, разбор плана от места, где оценка строк впервые разошлась с фактом. N+1 из Go-цикла сворачиваем в один запрос. Правим условия, FK, статистику и память, а не боремся с планировщиком. Postgres query tuning: profile first, compare by buffers, fix row estimates, remove N+1.

Import the user's ChatGPT or Claude data export into their AI file system, so it starts out knowing what they've already told AI. Use during setup, or when they say "import my ChatGPT history", "use my Claude export", or run /ai-file-system:import-history.

Runs a time-boxed research spike for one ticket of type spike (from the team's tracker such as Linear, or a local tasks file) and produces a decision record with evidence, a recommendation, and proposed backlog changes, without shipping code. Use only when a specific spike ticket (such as ENG-130 or T-03) is named, by the user or by the deliver-project orchestrator.

Comprehensive guide and development standards for maintaining, building, and extending the Campus Helpdesk React portal. Covers component architecture, responsive UI, issue validation, ticket lifecycle statuses, analytics, and verification workflows.

Orient in local codebases at the start of coding sessions and before refactors or complex code questions using scoped ast-grep outlines. Choose rg for exact text, ColGREP for behavioral discovery, and ast-grep for structural searches and transformations; not for web research.

>- Starts the post-commit reviewer for this project. One analysis, then a script-rendered Cursor canvas. Use when a coherent feature is done, or the user says review-change. Do not review in this chat. Do not launch this skill when applying or skipping canvas diffs.

把一篇学术论文变成一整套可汇报的中文优先材料——论文精读、技术与术语解析、Word 文档、汇报 PPT、引用脉络（前驱 + 后续）、可延伸的 idea。凡是用户提到「分析这篇论文」「论文汇报」「组会 pre」「文献汇报」「做成 PPT」「这篇论文讲了什么」「谁引用了这篇论文」「这篇论文还能怎么改进」，或者丢过来一个 PDF / arXiv 链接并要求讲解，都应当使用本 skill——即使用户没有明说「要一整套材料」。用户只说「帮我把这篇论文做成 PPT」时也要走本 skill 的完整流程：先精读、先核对，再动手做 PPT，避免整份 deck 建立在对论文的误读之上。PPT 采用白底、较大字号、图文分区和原生项目符号，版式主基准仍为 `references/group-meeting-sample.pptx`，每页含中南大学校徽。

Vẽ sơ đồ và biểu đồ đẹp cho báo cáo — flowchart/sequence/class/state/ER/gantt bằng Mermaid (kroki.io, PNG), biểu đồ cột/tròn/line bằng matplotlib (uv), output `<tên>.diagram.png` cạnh nguồn để nhúng vào `.report.docx`. Dùng khi báo cáo cần sơ đồ thay cho ASCII, cần biểu đồ dữ liệu, hoặc user yêu cầu "sơ đồ đẹp".

Viết báo cáo theo một trong hai dạng: chuẩn quốc tế hoặc phổ biến tại Việt Nam. Tổng hợp nguồn có trích dẫn, giữ báo cáo chính gọn và tách dữ liệu hỗ trợ khi cần; xuất `.report.md` hoặc `.report.docx`.

Trích xuất và chuyển đổi tài liệu PDF/DOCX/XLSX — lấy text layer (pdftotext), OCR ảnh scan (pdftoppm + tesseract), chuyển markdown (docling), XLSX → CSV (libreoffice headless), ghép/tách/đảo trang (qpdf/pdftk), kiểm tra output bằng pdfinfo + pdftotext. Dùng khi đưa tài liệu và muốn lấy text, OCR bản scan, chuyển định dạng, tách/ghép/trang, hoặc xác minh nội dung đã trích.

Reverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.

Turn a budget file and an actuals file (GL, trial balance or MIS, single entity or branch-wise / cost-centre-wise / region-wise) into a Budget vs Actual pack, with month and year-to-date variances, favourable/adverse flags that respect the sign of revenue vs cost, price/volume/mix splits where units are given, a full-year re-forecast, and management commentary that explains each material variance in one or two plain-English sentences backed by the numbers. Ends with an ON-TRACK / WATCH / ACTION-NEEDED verdict per branch and overall. Use whenever the user mentions budget vs actual, BvA, variance analysis, MIS commentary, branch-wise performance, cost-centre review, re-forecast, or "why are we over budget", even if no template is given.

Plan a rigorous topic-specific web investigation, compare independent evidence and create a cited research report with verified source accounting.

Draft, review, and schedule distinct social posts with the TimeToPost MCP. Use when asked to plan a social calendar, draft a post or thread, check approval drafts, choose a posting time, or schedule content.

Content Research command - find high-demand, low-supply content gaps. Use only when the user invokes cr-gaps or asks for the content-research "gaps" action. Entry point for the content-research skill.

Captures, sanitizes, and maintains high-value cross-session state in persistent memory files (MEMORY.md) while strictly protecting sensitive data and discarding ephemeral noise.

Content Research command - analyze competing creators and their content. Use only when the user invokes cr-competitors or asks for the content-research "competitors" action. Entry point for the content-research skill.

Content Research command - run the complete content research workflow. Use only when the user invokes cr-full or asks for the content-research "full" action. Entry point for the content-research skill.

Use when caching GraphQL reads in a NestJS (code-first) app — wiring a stale-while-revalidate (SWR) cache module once, deciding what to cache and where to mount it (service, field, operation, or CDN), and keeping it leak-safe. Triggers when you need SWR, single-flight dedupe, tag invalidation, per-user vs public scoping, cache observability, a stampede or blocking-miss at TTL expiry, a shared-key data leak, a dev/ops switch that disables caching entirely, or a one-time setup reference (module, file placement, storage, referencesTTL/GC, caller identity, decorator runtime, fail-open).

Search the web before answering or carrying out user requests, then use checked sources and citations. Use when the user wants web-first answers or research before each task, especially with models that need external knowledge.

Reviews macOS Swift 6+ code for modern idioms, SOLID principles, SwiftData patterns, and concurrency best practices. Use when reviewing macOS code quality or asking about best practices.