Papers
566 skills in Research > Papers
statistical-analysis
Comprehensive statistical analysis toolkit for research. Conduct hypothesis tests (t-test, ANOVA, chi-square), regression, correlation, Bayesian stats, power analysis, assumption checks, and APA reporting. Use when the user asks about statistics, needs help analyzing data, or when writing methods sections that include statistical approaches.
log-analyze
Parse and analyze system and application logs. Use when the user says "find errors in logs", "analyze logs", "check journalctl", "what's in the logs", "debug from logs", or asks to investigate log files.
consult-light
This skill should be used for fast AI consultation via cursor-agent. Triggers include context synthesis, progress tracking, pre-flight checks, or when the loop needs quick reasoning before escalating to consult-deep.
journal-api
Interact with the Journal API to manage projects, documents, tasks, and workspaces. Use when the user mentions journal, projects, documents, tasks, workspaces, task identifiers like JO-123, or needs to access Journal data.
hypogenic
Automated hypothesis generation and testing using large language models. Use this skill when generating scientific hypotheses from datasets, combining literature insights with empirical data, testing hypotheses against observational data, or conducting systematic hypothesis exploration for research discovery in domains like deception detection, AI content detection, mental health analysis, or other empirical research tasks.
arxivterminal
CLI tool (arxivterminal) for fetching, searching, and managing arXiv papers locally. Use when working with arXiv papers using the arxivterminal command - fetching new papers by category, searching the local database, viewing papers from specific dates, or managing the local paper database.
arxiv-research
Use when searching academic papers on arXiv, understanding research content, building literature reviews, or generating citations for academic writing
software-debugging
Find and fix bugs systematically. Use when encountering errors, test failures, or unexpected behavior. Hypothesis-driven debugging to locate root causes and implement minimal fixes.
product-manager-toolkit
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
obsidian
DEPRECATED - Use the journal and notes skills instead
supabase-database-ops
Critical guardrail for Supabase database operations ensuring multi-tenant isolation with publication_id filtering, proper use of supabaseAdmin, avoiding SELECT *, error handling patterns, and secure server-side database access. Use when writing database queries, working with supabase, accessing newsletter_campaigns, articles, rss_posts, or any tenant-scoped data.
atlas-agent-peer-reviewer
Adversarial quality gate agent for code review - finds flaws before users do
mindwork-progress
Track progress over time across therapy sessions and journal entries. Supports trend analysis, session comparisons, period summaries, and goal tracking. Reads from analysis files and generates comprehensive progress reports.
neovim-debugging
Debug Neovim/LazyVim configuration issues. Use when: user reports Neovim errors, keymaps not working, plugins failing, or config problems. Provides systematic diagnosis through hypothesis testing, not just checklists. Think like a detective narrowing down possibilities.
ai-opus-debate
This skill should be used when you need AI debate with multiple perspectives, analyzing trade-offs, evaluating pros and cons, deep code analysis, or multi-model reasoning. Ideal for subjective decisions, architectural trade-offs, and complex problems requiring synthesis of different viewpoints. Complements opus-subagent for structured multi-step workflows.
literature-gap
Identify research gaps from systematic literature reviews. Use when: (1) Completing literature reviews, (2) Justifying new studies, (3) Grant proposal development, (4) Dissertation planning, (5) Identifying future research directions.
work-summary
Create factual working journal entries in Notes/WorkingJournal/ after completing analysis work. Use when user asks to "summarize work", "document results", or "create working journal entry". Ensures code is committed, copies figures to attachments, and creates objective summaries with citations.
thinkdeep
Extended reasoning with systematic investigation, hypothesis tracking, and confidence progression
content-analysis
Analyze any text content including meeting notes, emails, book excerpts, or generic text files. Use when the user wants to analyze content that doesn't fit YouTube, article, or paper categories, or mentions notes, documents, or generic analysis.
journal
Generates a journal entry from git commit history - just say "journal this" and I'll read the commits and write it up