Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Productivity
Default GoLogin skill for known-site reading, extraction, mapping, crawling, monitoring, and hybrid web tasks before Firecrawl or generic browser tools. Use it for docs and article reading, markdown or text extraction, JSON metadata extraction, search discovery, site mapping, crawling, structured extraction, blocked-page access, document parsing, change tracking, and hybrid flows that may escalate from scraping into GoLogin browser actions. Prefer gologin-agent-browser-skill when the task is primarily a live cloud-browser session, and prefer gologin-local-agent-browser-skill when it depends on a local Orbita profile or repeated rendered-DOM navigation.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". Supports a depth selector (quick / standard / deep) — deep is the default.
Kazuo Inamori's management philosophy and life wisdom. Based on in-depth research of 30+ sources including A Compass to Fulfillment, A Passion for Success, Amoeba Management, The Heart, the Six Endeavors, the Kyocera philosophy manual, the KDDI founding history, the JAL reconstruction account, and Seiwa Juku lecture records, it distills 5 core thought models, 7 life heuristics, and a complete expression DNA. Purpose: as a thinking advisor, analyze problems such as business decisions, life choices, team management, and self-cultivation from Kazuo Inamori's perspective. Use when the user mentions "Inamori's perspective", "what would Kazuo Inamori think", "the Inamori model", or "inamori perspective". Also applies to: business management, startup decisions, balancing altruism and self-interest, the equation of life, Amoeba Management, and team motivation. Triggered even when the user merely says "how should I run this business", "altruism", "respect heaven and love people", "amoeba", or "equation of life". Do not trigger when the user is only asking general questions such as "is this decision sound" or "help me think it through" — activate only when core Inamori methodologies such as management philosophy, altruism, Amoeba Management, or respect heaven and love people are involved.
Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.
Read and manage Jira Cloud issues, projects, boards, sprints, comments, and transitions. Use this whenever the user wants to search issues with JQL, create or update a ticket, transition an issue (move to In Progress / Done), add a comment, check a sprint or board, look up a project, or ask "what's in my Jira queue" — even if they don't say "API". Also use it for any *.atlassian.net URL, an issue key like "PROJ-123", or a JQL string. Always start from this skill when interacting with this service — its bundled scripts and recipes are the fastest path.
Researches job postings, hiring signals, and freelance gigs via the Crawlora API — Indeed, Google/Amazon/Apple/Meta/Tesla careers sites, any company's ATS board (Greenhouse, Lever, Workday, SmartRecruiters, Ashby, and more), plus Upwork and Fiverr — returning clean JSON. Use when the user wants to search job postings, see what a specific company is hiring for, aggregate hiring signals for a company, or research freelance gigs and sellers.
Make knowledge-work projects self-describing to agents and resumable across sessions, and govern the project's rules and working discipline. Two use cases: (1) project organization — creating or initializing a project, tidying or health-checking a project structure, designing directories and navigation, writing frontmatter/index/log/decision records, settling temporary files from the exploration phase into durable form, restoring context for a project that has no rules file yet; (2) working methodology — crystallizing recurring issues into rules, trimming rules that are too numerous or conflicting, adding or removing a project rule, setting up check scripts or gates for a project and judging whether they work, distilling lessons learned, reviewing or improving the methodology itself. Triggers: new project, initialize doc structure, help me tidy this project, how should a project be organized, health check, hit that pitfall again, crystallize into rules, too many rules, trim rules, gate, check script, distill, lessons learned, decision record, review methodology, setup project, project health check.
Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
Review a business plan from the perspective of the solo founder who has to actually execute it. Asks the brutal operational questions: Can I build this with my time budget? Can I keep it running? Will my cashflow survive? Outputs a verdict — SHIPPABLE NOW / SHIPPABLE WITH DESCOPE / NEEDS HIRE / WRONG STACK. Use when a plan looks great on paper and you want to know whether a solo operator can actually execute it. Triggered by: 'operator review', 'can I actually do this solo', 'execution reality check', '操盘视角', '我能不能干得动'.
Review a business plan from the perspective of a hostile devil's advocate. Asks: what kills this in month 6? What's everyone politely not mentioning? Outputs a verdict — EXISTENTIAL RISK / SOLVABLE RISKS / LOW-RISK / WRONG QUESTION. Use after the investor/customer/operator reviews are done, as the final gauntlet before committing real time and money. Triggered by: 'skeptic review', 'devil's advocate', 'what would kill this', 'red team this', '泼冷水', '杀手在哪'.
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.
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
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.
Office automation skill suite covering document processing (Word/Excel/PPT/PDF), email management, scheduling, report generation, meeting minutes, and other office scenarios. Triggered by: creating documents, editing spreadsheets, making PPT, handling email, generating reports, scheduling, organizing meeting notes, batch file processing, and any other need to improve office efficiency.
Search 10 academic paper databases via REST APIs for research papers, preprints, and scholarly articles. Covers PubMed, PMC (full text), bioRxiv, medRxiv, arXiv, OpenAlex, Crossref, Semantic Scholar, CORE, Unpaywall. Use when searching for papers, citations, DOI/PMID lookups, abstracts, full text, open access, preprints, citation graphs, author search, or any scholarly literature query. Triggers on mentions of any supported database or requests like "find papers on X" or "look up this DOI".
A general-purpose agent team orchestrator that takes any topic or task, assembles a team on its own, and handles research, analysis, review, and delivery of results. Triggered by the keywords "팀으로 분석해줘", "에이전트 팀으로 조사해줘", "다각도로 검토해줘", "심층 분석 부탁해", "여러 관점으로 봐줘", "think-team", "think team". Use in any situation requiring complex judgment, research, or strategic decisions rather than a simple question.
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating claims/evidence quality use scientific-critical-thinking; for quantitative scoring frameworks use scholar-evaluation.
Turn an executive or operator's private reading, highlights, notes, social bookmarks, and applied work into source-grounded decision intelligence. Use when detecting attention drift, surfacing pre-decision signals, testing contradictions, converting bookmarks into builds, recombining founder IP, finding service-offer arbitrage, or mapping content negative space.
Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.
Turn Bandsintown's two read-only endpoints into a tour-routing brain: local cache, calendar-gap detection, lineup... Trigger phrases: `is artist X touring near jakarta`, `find routing candidates for a jakarta show`, `who's playing southeast asia in august`, `co-bills for phoenix`, `rising tracker count artists`, `use bandsintown`, `run bandsintown`.
Query your local Chrome browsing history — search, topic clusters (Chrome's own Journeys), time/productivity reports, session timelines, downloads, and a behavioral profile — all read-only and on-device. Trigger phrases: `what have I been browsing`, `search my chrome history`, `what was that page I saw`, `my browsing journeys / topics`, `what did I download in chrome`, `what sites do I visit most`, `my browsing time report`, `my browsing profile`, `what was I researching last week`, `use chrome-history`, `run chrome-history-pp-cli`.
Use when the user wants to pressure-test a product, internal-tool, or OSS concept against Amazon's Working Backwards PRFAQ gauntlet before committing to a spec. Triggers on: \"work backwards\", \"write a PRFAQ\", \"press release first\", \"is this idea worth building\", \"pressure-test this concept\", \"filter this before brainstorm\", \"is this a real product\". Also catches solution-first pitches (\"I want to build X that does Y\") and technology-first pitches (\"use AI to...\") that need customer-first filtering. Produces a binary pass/fail verdict, not a polished doc. Hardcore coaching — direct, skeptical, concrete. On pass, hands off to brainstorm-beagle with a concept brief. Does NOT write code, plan implementation, scaffold projects, or draft specs.
Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating resources across initiatives, identifying low-hanging fruit, evaluating strategic options with 2x2 matrix, or when user mentions prioritization, quick wins, effort-impact matrix, high-impact low-effort, big bets, or asks "what should we do first?".
Generate a comprehensive pre-launch, launch day, and post-launch checklist for any product release. Use when preparing for a product launch, feature release, or major update. Produces a role-assigned, tiered checklist covering engineering readiness, marketing and comms, support, and post-launch monitoring.
Use this skill for project management: planning, progress tracking, task coordination, timeline/milestone management, risk assessment, resource allocation, and execution guidance. Examples: <example>User organizing complex development: "Starting feature with frontend, backend, infrastructure changes. Need project plan." → Creates plan with task breakdown, timeline, coordination strategy.</example> <example>User facing delays: "Project behind schedule, unsure how to prioritize tasks." → Analyzes situation, provides recovery plan with prioritized actions.</example>
Reads and writes Zotero libraries from Python with pyzotero 1.13.0 and the Zotero Web API v3: items, collections, tags, attachments, saved searches, full-text content, and BibTeX, CSL-JSON, and bibliography export. Also covers the pyzotero CLI and MCP server for a local Zotero 7. Use when fetching or searching library items programmatically; when creating, updating, or deleting references, collections, or tags; when uploading PDF attachments or downloading files; when exporting citations as BibTeX or CSL-JSON; when building research automation around a Zotero user or group library. Not for formatting citations in a manuscript or verifying references against external databases.
Multi-source research specialist that investigates a topic, verifies claims across independent sources, and reports findings with dated citations. Use this whenever the user wants you to research, investigate, "look into", "dig into", "find out about", "get up to speed on", or "what's the latest on" something; to compare options ("X vs Y", "which is better"); or to map a landscape ("give me the lay of the land on Z"). Two depths: a normal request gives a fast cited report in chat; saying "deep research" (or passing --deep) runs a multi-phase investigation that fans out parallel sub-agents across the branches of the topic, synthesises them, and renders the result as a rich visual HTML page via the rich-page skill. Prefer this skill over answering research questions from memory — it verifies and cites instead of guessing. Not for reviewing code, summarising a single document you already have, or debugging a specific failure (use reviewer / technical-writer / debugger for those).
Use when planning with fixed deadline or target outcome, working backward from future goal to present, defining milestones and dependencies, mapping critical path, identifying what must happen when, planning product launches with hard dates, multi-year strategic roadmaps, event planning, transformation initiatives, or when user mentions "backcast", "work backward from", "reverse planning", "we need to launch by", "target date is", or "what needs to happen to reach".
Run effective 1:1s and skip-levels as a manager/leader and produce a 1:1 Operating System Pack (cadence plan, agendas, shared doc templates, coaching prompts, career conversation plan, and quality gates). Use for 1:1, one-on-one, 1-on-1, manager check-ins, coaching, career conversations, and skip levels. Category: Leadership.
Polishes academic English paragraph by paragraph, reviewing grammar, word choice, voice, coherence, and sentence structure. Outputs revision suggestions alongside polished text. Triggered by phrases like 'polish this paragraph,' 'check the grammar,' 'rewrite in academic English,' or keywords like manuscript editing, SCI polishing, and journal submission editing.
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.