Skills
96,770 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
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.).
Manage a Markdown-based Kanban board using card files in a kanban/ directory (including kanban/archived/ for completed cards). Use when the user asks to create, move, view, list, or manage tasks or cards on a kanban board, or when tracking work items across statuses like backlog, todo, doing, done, or archive.
Rewrite text to remove the tells of AI-generated writing so it reads like a careful person wrote it, preserving the original meaning, facts, and intent. Use whenever the user wants prose to sound more human or less robotic, wants an AI/LLM draft cleaned up, asks to “de-slop” or “humanize” text, worries something “sounds like ChatGPT wrote it,” or asks you to write copy without the usual AI patterns. Trigger even when the user doesn't say “humanize” — any request to make writing sound natural, less generic, or less machine-made is in scope.
Extract durable knowledge from the current live session, stage it as a validated done session log, and run it through the same curation machinery as /kk-curate. Use when the user wants to proactively process the current session before waiting for capture hooks and a later curate pass — not for dictating one node (/kk-add) or batch-processing accumulated logs (/kk-curate).
Audits a local Claude-managed knowledge base under a 'Knowledge Base/' folder. Surfaces contradictions between articles, broken backlinks, unsourced claims, stale articles, writing-rules violations, and three suggested new articles. Files a full report into the KB's 'Outputs/' folder, appends a one-line CHANGELOG entry, and (in interactive sessions) walks through which findings to action. Use this skill whenever the user says "run a health check", "audit the [name] KB", "audit my knowledge base", "check the wiki", "let's go through the health check report", or "action the latest health check". Also use when the monthly scheduled task 'knowledge-base-monthly-health-check' fires. Use this skill for any audit-style request against a folder under 'Knowledge Base/' even if the user doesn't say the word "health check" - the protocol is the same.
Write and maintain knowledge base articles from resolved support issues. Use when a ticket is resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.
Searches Reddit, X/Twitter, and the broader web for recent opinions, sentiment, and signal on any topic. Use when you need to know what real people are saying about a tool, product, trend, or event in the past 30 days — cutting through SEO content to surface genuine community reaction. Produces a structured report with consensus findings, pain points, positive signals, contrarian takes, source links, and a signal confidence rating.
Leave or unassign from a task you accepted on OpenAnt. Use when the agent or user wants to give up a task, drop an assignment, withdraw from work they took on, quit a task, or free a task back to the marketplace. Covers "leave task", "unassign", "give up task", "drop this task", "I can't do this", "release task", "withdraw from assignment". Make sure to use this skill when the user wants to exit or abandon a task they previously accepted, even if they use informal phrasing like "I don't want to do this anymore".
Issue, update, release or report legal hold notices — draft the hold notice as .docx, update the hold fields in the matter log, and schedule the next update. Use when the user says "issue a legal hold", "update the hold notice", "release the hold", or asks for a portfolio-wide legal hold status report.
Session entrypoint for working on any project. Use when the user invokes /lets-work, says they are starting work on a project, or returns to one after time away ("catch me up", "what changed here since I left?"). Briefs the user on how the project drifted relative to their own recorded mental model, orients first-time visits, and sets the session's working frame — the user's work-style philosophy, including arming the exit ritual (/checkpoint).
Read and manage Linear issues, projects, cycles, teams, comments, and labels. Use this whenever the user wants to list their issues, search issues, create or update an issue, move an issue between states, add a comment, check a project or cycle, look up a team, or ask "what's on my plate in Linear" — even if they don't say "API" or "GraphQL". Also use it for any linear.app URL or an issue identifier like "ENG-123". Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
Sync, audit, or rescue an existing Linear project against repo reality. Use when the user asks to sync Linear, reconcile tracking, audit this project, fix a messy board, revive a parked project, or score readiness with the rubric. Runs discovery + confirmation before writes; never silent reorganize. NOT for first-time bootstrap (use linear-setup) or one-off CRUD.
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature searches across biomedical, scientific, and technical domains. Creates professionally formatted markdown documents and PDFs with verified citations in multiple citation styles (APA, Nature, Vancouver, etc.).
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to wiki', 'LLM wiki' or 'Karpathy wiki'.
Build and query a local Markdown knowledge base ("vault"). TWO functions — (1) CONVERT raw files (PDF, Word/docx, PowerPoint/pptx, Excel/xlsx, csv/tsv, images, html, md/txt, json/yaml/code, audio/video) into clean Markdown with retrieval-friendly frontmatter; local-first (pandoc / python-pptx / openpyxl / pymupdf4llm / whisper), with cloud OCR (MinerU) only as a fallback. (2) ANSWER questions over the resulting vault with retrieval discipline — self-monitor coverage, flag missing/lossy content, and propose Maps-of-Content (MOCs). Triggers: "build/sync my local knowledge base", "convert these files to markdown for AI", "整理我的资料库", "把文件转成 md 给 AI 读", "本地知识库", "读我的本地 vault 回答", "这个主题我的资料里怎么说". Not for: one-off web research, or files that are already in a single doc you can read directly.
Lumen — project knowledge keeper. Trigger on any /lumen command, on mentions of "lumen", "knowledge base", "wiki", "ADR", "document the project", on broad architectural questions about a codebase ("how does X work", "why did we choose Y"), or when the user pastes a transcript/spec to capture for future sessions.
Manage up effectively and produce a Managing Up Operating System Pack (manager profile, comms cadence, weekly updates, escalation/ask plan, expectation & boundary script, and exec-ready decision/tradeoff memo). Use for managing up, managing your boss, working with your manager, exec communication, stakeholder updates, and escalation. Category: Leadership.
Prepare structured briefings for meetings with legal relevance and track resulting action items. Use when preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed.
File-scan review feature of the AI personal memory system. Scan files modified this week in the Obsidian vault (excluding the AI_MEMORY directory) and identify potentially important events and decisions. Use cases: (1) when the user says "file scan", "check this week's files", or "scan file changes"; (2) before supplementing L1 records during a weekly review; (3) when the user wants to review this week's activity in Obsidian. The skill lists the modified files, asks the user which ones need to be recorded in L1, and assists with the recording.
Monthly review feature of the AI personal memory system. Analyze this month's L2 behavior-layer updates, distill thinking patterns into the L3 cognition layer, and check whether the L4 core layer needs recalibration. Use cases: (1) when the user says "monthly review"; (2) for regular reviews at the end of each month; (3) when you need to distill a cognitive framework from behavior patterns. The skill analyzes whether multiple behaviors point to the same thinking principle, tries to distill them to L3, and guides the user to reflect on the L4 core layer.
Weekly review feature of the AI personal memory system. Analyze this week's L1 situational-layer records, identify recurring patterns, and distill them into the L2 behavior layer. Use cases: (1) when the user says "weekly review"; (2) for regular reviews each week; (3) when you need to distill behavior patterns from daily records. The skill automatically counts recurring behaviors (3+ times), generates a candidate list, and updates the L2 behavior layer after user confirmation.
Run a scenario-based DevOps, SRE, Cloud, or Platform Engineering mock interview, then deliver a brutally honest analysis and a tailored prep plan. Pulls questions configured by topic (Kubernetes, AWS, Docker, Terraform, CI/CD, Linux, Monitoring/Observability, System Design, Networking, Security, mixed), difficulty (junior 0-2y / mid 2-5y / senior 5-8y / staff 8+y), and target company tier (Service like TCS/Infosys/Wipro/Capgemini, Product like Razorpay/Zerodha/Swiggy/PhonePe/Atlassian, or MANG/FAANG like Meta/Apple/Netflix/Google/Amazon/Microsoft). Conducts the interview question-by-question in interviewer voice (no hints, no mid-interview praise), then flips to coach mode for per-question analysis, pattern detection across the session, a tier-by-tier verdict, and a 7-day prep plan. Trigger AGGRESSIVELY on: /mock-interview, "mock interview", "interview prep", "interview practice", "DevOps interview", "SRE interview", "cloud interview", "Kubernetes interview", "AWS interview", "scenario question", "system design interview", "interview me", "test me", "quiz me on K8s/AWS/etc", "help me prepare for an interview", or anytime the user expresses they have an upcoming DevOps/SRE/Cloud/Platform/Infra interview, even if they don't use the word "mock" — interview readiness is the trigger, not the exact phrasing.
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Create and edit Obsidian Flavored Markdown. When tasked with creating, structuring, or initializing a new Obsidian vault or knowledge base, MUST default to the llm-wiki structure (comprising SCHEMA.md, index.md, log.md, raw/, topics/, entities/, concepts/, comparisons/, queries/). This skill MUST be used when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Self-hosted, open-source alternative to Google NotebookLM for AI-powered research and document analysis. Use when organizing research materials into notebooks, ingesting diverse content sources (PDFs, videos, audio, web pages, Office documents), generating AI-powered notes and summaries, creating multi-speaker podcasts from research, chatting with documents using context-aware AI, searching across materials with full-text and vector search, or running custom content transformations. Supports 16+ AI providers including OpenAI, Anthropic, Google, Ollama, Groq, and Mistral with complete data privacy through self-hosting.
Use this skill for "search for papers", "find citations", "look up a DOI", "get BibTeX", "download PDF", "convert PDF to markdown", "find canonical papers", "convert identifiers", "batch download papers", "configure opencite", "literature review", "find related papers", "what papers cite this", "export references", "read this paper", or mentions of opencite, Semantic Scholar, OpenAlex, PubMed, academic literature search, citation management, or paper retrieval.
Screenshot and visually read any web page or document using pixelshot. Use instead of fetching raw HTML when you need to see how a page looks, read visual content such as charts, diagrams, and infographics, check layouts, or verify UI. Triggers include “look at this page,” “screenshot,” “what does this site look like,” “check the UI,” “read this visually,” “view this URL,” and requests to view web content.
Build a Pragmatic Institute Product Canvas / business case to justify investing in an opportunity — the market-driven way. Use when the PM asks to “make the business case”, “justify this to leadership”, “size the market”, “should we buy, build or partner”, “what's the ROI”, “build a product canvas”, or “get buy-in for this idea”. Frames the opportunity as Value Proposition, Value Creation and Value Capture, sizes the market, runs the Buy/Build/Partner decision, and ends in a go/no-go recommendation with quantified risk. Produces a Product Canvas / Business Case as a Markdown or Word .docx artifact.
Build a Pragmatic Institute Product Roadmap that communicates vision, direction and priorities over time — a plan, not a commitment. Use when the PM asks for a "roadmap", "product vision", "what's coming", "phases", "themes over time", or wants to align stakeholders on direction (as distinct from a dated release plan). Frames outcomes and market problems over time-frames, not features on dates. Produces a Product Roadmap as a Markdown or Word .docx artifact.
Turn a prioritized set of requirements into a committed Pragmatic release plan — themed, sized, and signed. Use when the PM asks to plan a release, define MVP scope, commit a date, build a release charter, or “what goes in this release”. Covers MVP done right, themes, the estimation ladder, the market window, and the scope/schedule/resources change levers. Produces a Release Charter as a Markdown or Word .docx artifact.
Build a Pragmatic stakeholder communication plan and status updates that expose risk early and speak each audience's language. Use when the PM asks to manage stakeholders, plan comms, write an exec/status update, a project status report, a steering-committee update, or “keep everyone aligned”. Covers the Identify→Analyze→Communicate steps, the Influence×Importance matrix, and the four metric categories. Produces a Stakeholder Communication Plan and a Status Update as a Markdown or Word .docx artifact.
Every Tech Twitter read endpoint, plus an offline-searchable local mirror and cited evidence bundles no other tool has. Trigger phrases: `what changed in tech twitter`, `what's trending in tech`, `give me a tech digest`, `what narrative is emerging in AI`, `search tech twitter for`, `use techtwitter`, `run techtwitter`.
CAVEMAN HUNT BAD PROCESS! Me find greedy creature eating fire and rocks. Me bonk them good. Use when tribe say "kill processes", "clean up servers", "save battery", "find resource hogs", "bonk next.js", or "hunt processes". Me bonk known bad creature automatic. Me ask before bonk mystery creature.
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.
Close or transition a consulting engagement through acceptance, handover, knowledge transfer, benefits ownership, financial reconciliation, and lessons learned. Use for successful completion, early termination, suspension, or transition to business-as-usual.
Use when the user has a research proposal (problem + proposed methodology + planned experiments) and wants it iteratively strengthened until it clears a passing grade. ScholarEval grades the proposal against the literature (Soundness + Contribution), a Judge scores that feedback 0-100 on a fixed rubric, and a Reviser rewrites the proposal to fix the worst points without diluting the research question; loops until the grade passes or the budget is hit. Not for generating a proposal from scratch, and not for running a literature survey on its own.
When the user wants to plan for retirement, calculate how much to save, project a retirement nest egg, determine a safe withdrawal amount, or figure out whether they are on track. Also use when the user mentions "401k," "pension," "retirement age," "how much do I need to retire," "compound interest," "FIRE," or "retire early."
Use when the user is torn over a directional decision — first judge whether the direction is right, then consider how to do it well. Typical triggers: "I'm torn about whether to do XX", "I've worked on it a long time but results are poor", "is the direction right", "is it worth persisting", "is this a direction problem or an execution problem". Core framework: "do the right things" (direction judgment, the way) vs "do things right" (execution efficiency, the technique); the two cannot be reversed. Not for: purely execution-level problems (the right direction is already set and only methods are needed), or trivial everyday matters.
Research mountain routes and generate comprehensive route beta reports for North American peaks, aggregating weather forecasts, avalanche conditions, daylight windows, trip reports, and access info from PeakBagger, SummitPost, WTA, AllTrails, and regional avalanche centers. Use when planning a climb, hike, or scramble, or when asked for route beta, trail conditions, peak research, or mountaineering trip planning.
Check whether an argument's premises actually support its conclusion, and identify logical fallacies. Use when reviewing a design decision, technical proposal, product argument, or any reasoning where the conclusion needs to hold up under scrutiny. TRIGGERS: 'validate this argument', 'does this logic hold', 'check my reasoning', 'is this a fallacy', 'find the flaw in this', any proposal or decision where the reasoning chain matters. Pairs well with logic-consistency-check when a full document needs scrutiny.
Identify the right influence approach and construct it for the context. What actually changes minds and drives action. Triggers: 'how do I persuade', 'how do I change their mind', 'what would convince them', 'how do I get buy-in', 'how do I influence', 'influence strategy', 'how do I pitch this', 'what makes a persuasive case', 'how do I get them to say yes'.
Use when the user asks for a literature review, academic deep dive, research report, state-of-the-art survey, topic scoping, comparative analysis of methods/papers, grant background, or any request that needs multi-source scholarly evidence with citations. Also trigger proactively when a user question clearly requires academic grounding (e.g. "what's known about X", "compare approach A vs B in the literature", "summarize the field of Y"). Runs an 8-phase (Phase 0..7), script-driven research workflow across 7 federated sources (OpenAlex, arXiv, Crossref, PubMed, DBLP, bioRxiv, Exa) with optional Semantic Scholar / Brave MCP enrichment, with deduplication, transparent ranking, dual-backend citation chasing (OpenAlex + Semantic Scholar), self-critique, and structured report output with verifiable citations.
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.