Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
Get active work items for a team showing dependencies, priorities, and sprint assignments. Displays items that are blocking others, high priority items first, and items due this sprint. Shows parent/child hierarchy with Title, State, Priority, ChangedDate, Iteration Name, and Iteration End Date.
Turn meeting audio into three artifacts (a corrected transcript, an HTML visual canvas, and a Markdown summary with AI insights), transcribed locally with Whisper on any platform: no cloud, no external transcription app. Use when the user provides a meeting recording or wants meeting notes from one ("处理这个录音", "会议纪要", "把录音转成文字", or an audio file lands in the configured drop-zone), wants an existing transcript corrected or cleaned ("处理 transcript", "转录纠错", "转写文本", or a .txt lands in the drop-zone), wants a recording pulled from their connected PLAUD account ("process my Plaud recording", "从 Plaud 拿"), asks for edits to a transcript, canvas, or summary this skill just produced, or requests cross-meeting Insights on communication patterns instead of processing one recording ("analyze my meetings", "how do I come across in meetings", "分析我的沟通模式", "复盘我最近的会议", "跨会议分析").
Run a structured business analysis workflow: requirements elicitation with stakeholder interviews and MoSCoW prioritization, as-is/to-be process mapping with BPMN notation, data-driven analysis (CBA, SWOT, root cause), and production-ready documentation (BRD, FRD, user stories with INVEST acceptance criteria). Triggers on "gather requirements", "write user stories", "map business process", "BRD", "FRD", "gap analysis", "cost-benefit analysis", "facilitate workshop", "business requirements", "process mapping", "as-is to-be", "stakeholder interview", or "business analyst". For management consulting (issue trees, steerCo business cases, operating model), use business-consultant—not business-analyst. For business model canvas, market sizing, and unit economics research, use business-model-researcher. Human data / labeling platform PRDs: product-management-human-data-platform. Monetization PRDs and packaging: product-management-monetization.
Convenes expert panels for problem-solving. Use when user mentions panel, experts, multiple perspectives, MECE, DMAIC, RAPID, Six Sigma, root cause analysis, strategic decisions, process improvement, or asks for philosophers/ancients (Socratic, Aristotelian, Stoic method experts).
Audit the reasoning of a document or argument (memo, proposal, investment analysis, board paper, article, the user's own draft): claims, evidence, unstated assumptions, logical gaps, fallacies, and what would falsify it, each anchored to quoted text. Use whenever the user wants reasoning examined, in any language ("audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft"; Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "góp ý bản nháp của tôi"), even when they never say "critical thinking". Also use when the user drops a document and asks whether to trust or act on it, or asks to see their reasoning profile. Not for company-level strategic bets (strategy-board) or learning a topic through dialogue (socratic-questor).
Aggregated trending-list API service across the web — based on the open-source DailyHotApi project, auto-deployed locally, with zero-configuration access to real-time trending data from 40+ platforms. Covers major platforms such as Douyin, Weibo, Zhihu, Bilibili, Baidu, Toutiao and Kuaishou. Trigger words: 热点、热搜、趋势、热榜、trending、hot topics.
Invoke when the user has formed a strong opinion or theory and needs to test its reliability. Typical trigger signals: confirmation bias, looking only at supporting evidence, instinctive rejection of new evidence, "I'm sure this is right", self-review before a major judgment. Not for urgent situations requiring fast decisions, nor for pure information-gathering stages (no falsification needed when there is no opinion yet).
Synthesize a fragmented academic conversation into a cohesive, structured markdown report. Use this skill whenever the user has asked many disconnected questions about a topic in one session and now wants a unified write-up that captures what was discussed. Trigger phrases: write a report on our conversation, summarize this discussion into a document, turn this into a readable report, capture everything we talked about, make a note of this whole conversation, write up what we covered. The skill scans the full conversation, groups ideas into themes, identifies gaps, asks 2–4 targeted clarifying questions to fill them, then drafts the report. It does NOT write experimental results sections (use results-writeup), Related Work prose (use related-work-writer), or paper section drafts (use method-section-writer or abstract-and-intro-writer).
Distill each day's raw activity into a daily report. Ensures ~/.Life exists, pulls the day's activity via Luci, writes an objective report under ~/.Life/reflections/daily/, and writes new entities under ~/.Life/entities/. Use when the user says "distill", "distill my life", "catch up on daily reports", "summarize the last few days", or first needs the life folders created.
Answer questions using Einstein's thought-experiment method, relativistic thinking and imagination-driven approach. Use when the user explicitly asks for this figure's perspective, mentions "einstein-perspective", or wants to apply its core method to analyze a problem; do not trigger automatically for general questions.
Run scientific (software) experiments. Use when the user asks to "run an experiment", "run an investigation", or "research with Asta." Also use this skill to analyze experimental data generate a research report from it. The user may refer to this system by its internal project name, "Panda."
Retrieves a Jira ticket or a GitHub issue into docs/<KEY>.md as a read-only, validated Markdown snapshot for downstream workflow phases. Use when a Jira URL, a GitHub issue URL, or owner/repo/number coordinates need the Phase 1 fetch-work-item step. Detects the platform from the input and loads the matching playbook just-in-time.
Access and interact with my FreshRSS instance via python scripts. Use for any RSS-related question, including reading articles, searching past content, finding feeds, getting recommendations, managing subscriptions, checking unread counts, marking read/star, or exploring what I follow. Triggers on keywords: RSS, FreshRSS, feed, unread, headlines, articles, subscriptions, starred.
Generates comprehensive GitHub activity reports across all authenticated accounts. Gathers repos, PRs, features, and themes for configurable time periods (1/5/7/30/90 days). Produces shareable markdown with tables, mermaid charts, and executive summaries. Can create a private repo with GitHub Actions automation and GitHub Pages aggregation site. Use when: "github report", "work report", "activity summary", "what did I work on", "gh-work-report", "show my github activity".
Send and manage Gotify push notifications, applications, clients, and messages via the Gotify REST API. Use this skill whenever the user mentions "gotify", "push notification", "自托管通知", "消息推送", sending alerts, managing Gotify apps/clients, checking message history, toggling Gotify plugins, or verifying Gotify server health. Also trigger for "发通知到gotify", "gotify推送", "gotify消息", "通知服务", or any command mentioning a Gotify server instance.
Score the QUALITY of a research idea at the idea stage — given a Markdown file with Title / Motivation / Method sections (no experiments needed), produce a per-axis quality assessment with cited evidence and an overall 0–100 score plus a verdict; or, given two such idea files, a blind head-to-head comparison. TRIGGER when the user asks "how good is this idea", "rate / score / grade this research idea or proposal", "review my idea .md before I write it up", "is this contribution strong enough to pursue", "which of these two idea files is stronger", or hands over an idea Markdown file (Title/Motivation/Method) and wants a quality judgment. Use this even when the user does not say the word "score" but clearly wants an assessment of how strong an idea is. DO NOT trigger for prior-art / overlap / "is this novel vs existing work" checks (that is a literature-collision task), for full reviews of finished papers that already have results, or for generating the idea itself.
Convert vague industry, banking, fintech, enterprise, or operational problems into precise R&D problem statements, stakeholder maps, hypotheses, constraints, and solution search directions. Use whenever the user says a problem is vague, ambiguous, unclear, broad, political, business-driven, or not yet researchable. This skill should usually run before publication-grounded-solution-design when the problem is not specific enough to search literature or draft methods.
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Post-merge Jira writeback SOP: transition only to「已修复」, then an independent Wiki-markup comment posted in the body field with read-back markup-fidelity verification and a direct-REST fallback. Triggers — 「Jira 状态回写」「回写已修复」「合并后写 Jira」「jira writeback」「jira status writeback」. Do NOT use for reading issues, creating issues, or pre-merge comments. Loaded by Jira fix hosts after merge via frontmatter dependencies.
Manage a remote LinkGo v3 instance via its HTTP API. Use when the user wants to list/add/edit/delete service cards, modify page settings, upload icons, change or reset passwords, export/import config, or query debug info on the LinkGo navigation page. Also triggers for "导航页", "服务卡片", "LinkGo", "add card", "edit card", "sublink" and similar card management tasks.
Manage Notion notes, pages, and data sources with a JSON-first CLI for search, read/export, write/import, append, and move operations. Use when working with Notion, organising notes, moving pages, triaging an inbox, or reading/writing page content.
The declassified UAP file archive in your terminal — browse, search, and download 162+ files from the PURSUE initiative Trigger phrases: `check UFO files`, `search declassified UAP`, `download PURSUE files`, `war.gov UFO`, `browse UFO archive`, `use ufo`.
Product Owner (/po, alias: Max, /max) - Senior PO with 10+ years agile experience. Use when defining product vision, creating/prioritizing backlog, writing user stories with acceptance criteria, making scope decisions, validating features against business goals, or planning releases and sprints.
Facilitates a top-down pyramid discussion that calibrates the user's topic depth, then starts at high-level goals and progressively descends to concrete actionables, sharpening gaps and assumptions at each layer. Use when the user wants to break down a goal, explore a vision, elicit requirements, or mentions pyramid discussion, top-down planning, or progressive breakdown.
Plan and write responses to peer review, including journal “response to reviewers” letters for revise-and-resubmit, conference rebuttals under strict length limits (OpenReview/ICLR, NeurIPS, ICML, ACL ARR, CVPR), author responses to meta-reviews, and appeals. Use when a user receives reviews, must triage reviewer comments, draft point-by-point replies, decide what new experiments to run, disagree respectfully with a reviewer, or track manuscript changes for a revision. For authors answering reviews of their own manuscript; to write a review of someone else's paper, use peer-review instead.
Interactive research orchestrator. Scopes a high-level research goal through a short interview, presents an approvable nested plan tree of sub-questions ("unknown unknowns"), then fans out parallel subagents (with per-branch model tiering for cost) and rolls up their findings live into a written report plus executive summary. Use when the user wants to research a broad or fuzzy topic, explore unknown unknowns, run a deep multi-angle investigation, or mentions fan-out research, a research plan, or a research report
Generate structured research questions, testable hypotheses, and candidate empirical strategies from a topic, phenomenon, or dataset description. Use when user says "give me research ideas on X", "brainstorm questions about Y", "what could I study with this data?", "I'm looking for a paper idea on...", "generate hypotheses for...". One-shot generation, not multi-turn. For idea-refinement use `/interview-me`.
Acts as the primary starter that automatically coordinates the entire research workflow, from topic exploration and gap identification through methodology, data experiments, literature synthesis, to publication readiness.
Plan and structure a research talk (conference presentation, seminar, invited talk, or job talk) from a paper, set of results, or research overview. Use whenever the user needs to turn a paper into slides, structure a 15/20/30/45/60-minute talk, decide what to cut for a short slot, plan a job talk narrative, or figure out how to present technical content to a mixed audience. Also use when the user asks "how do I present this paper", "what should my slides cover", "how long should each section be", or "I only have 15 minutes". A talk is not a paper read aloud — the narrative arc, pacing, and depth of detail must be rebuilt from scratch for a listening audience.
Reads RHDH Jira and owns the mechanics every other RHDH Jira skill needs: `acli` flags and their traps, JQL for RHIDP, RHDHPLAN, RHDHBUGS and RHDHSUPP, custom field IDs, GraphQL and REST fallbacks, board and sprint IDs, the component catalog, and the workflow states with their exit criteria. Use to look up an issue such as RHIDP-1234, to write or debug a JQL query, to answer "which field is Story Points", "why is my search returning 30 rows", or "what does Release Pending require". Reading and query mechanics only — deciding what to file, judging readiness, or changing an issue belongs to the Jira skill that owns that verb.
Use when the user wants to send an email, email a file or document, send a message via email, forward information by email, or use HTML email templates. Trigger on any email-related request — including 'email this to...', 'forward this to...', 'send the report to...', 'attach this file and send'. Do NOT use for non-email communication like Slack or SMS.
Build, connect and maintain local knowledge bases, preserving originals and creating a traceable index. Use for "enterprise knowledge base", "company document organization", "product, customer and skill libraries", "turn a folder into a knowledge base", "self-media knowledge base" and "knowledge base health check". Supports three modes: enterprise three-library, general, and self-media; enterprise mode first understands the company and materials, classifies by product, customer and team SOP, and delivers each library's content and material gaps. Works with WorkBuddy, Codex and Claude Code; does not handle cloud RAG, automatic sync, or unauthorized file relocation.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.