Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Documents
Edit and review developer documentation for technical accuracy, completeness, structure, clarity, brevity, peer feedback, technical review, technical verification, QA procedure testing, and feedback integration. Use when reviewing, editing, refactoring, or preparing developer docs for release, especially docs with procedures, examples, prerequisites, or high-risk technical claims.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Use this skill for building end-to-end document processing workflows and pipelines using LandingAI ADE. Trigger when users need to: (1) Process batches of documents in parallel or async, (2) Build classify-then-extract pipelines for mixed document types, (3) Prepare parsed documents for RAG systems with chunking and vector DB ingestion, (4) Load extraction results into databases like Snowflake or export to CSV/DataFrames, (5) Visualize extraction results: draw bounding box overlays on pages, crop chunk images, or highlight/annotate specific words or phrases found in documents, (6) Build Streamlit or web UIs for document processing, (7) Find and highlight specific terms within document sections using word-level grounding (e.g. highlight "L2S" in the Introduction, redact PII, annotate extracted values on the original page). This skill complements the document-extraction skill which covers ADE SDK basics. Use document-extraction to write code that executes parse/extract/split operations with more precision and less cost than adding the document image to the prompt and asking the LLM to find the relevant info. Use document-workflows when composing those operations into pipelines, or when you need visualization, annotation, or word-level grounding on parsed documents.
Build document Q&A and searchable knowledge bases with Google Gemini File Search - fully managed RAG with automatic chunking, embeddings, and citations. Upload 100+ file formats (PDF, Word, Excel, code), configure semantic search, and query with natural language. Use when: building document Q&A systems, creating searchable knowledge bases, implementing semantic search without managing embeddings, indexing large document collections (100+ formats), or troubleshooting document immutability errors (delete+re-upload required), storage quota issues (3x input size for embeddings), chunking configuration (500 tokens/chunk recommended), metadata limits (20 key-value pairs max), indexing cost surprises ($0.15/1M tokens one-time), operation polling timeouts (wait for done: true), force delete errors, or model compatibility (Gemini 2.5 Pro/Flash only).
Arrange images or PDF pages into an A4 PDF, crop scrolling document screenshots to the original page boundaries, or convert continuous long images into long-page PDFs. Use this skill when the user needs screenshots merged into a PDF, phone UI and adjacent pages cropped out of court transcript screenshots, or each page to contain only its own content. Do not use for OCR, editing PDF text, or standalone image format conversion
Audit project documentation quality across 8 categories (Hierarchy, SSOT, Compactness, Requirements, Actuality, Legacy, Stack Adaptation, Semantic Content). Delegates to ln-601 for deep semantic verification of project documents. Use when documentation needs quality review, after major doc updates, or as part of ln-100-documents-pipeline. Outputs Compliance Score X/10 per category + Findings + Recommended Actions.
Writes scientific documents and documentation as markdown with embedded Mermaid diagrams as the canonical, git-diffable source format. Covers a markdown style guide, a Mermaid style guide, 24 Mermaid diagram type references (flowchart, sequence, ER, Gantt, state, mindmap, radar, sankey, XY chart, and others), and 9 templates (research paper, status report, decision record, how-to, pull request, issue, kanban, presentation, project documentation). Use when writing a report, manuscript, README, or analysis in markdown. Use when adding a workflow, pipeline, timeline, or architecture diagram to a document. Use when choosing the right Mermaid diagram type or fixing Mermaid syntax such as radar-beta or xychart-beta. Use when starting from a document template or checking citations and heading rules. Not for scatter plots of real data or photorealistic images; use Python plotting or scientific-schematics for those.
Explains the capabilities and limits, supported formats, and ecosystem (CLI / Python API / plugins / Docker / Azure integration) of MarkItDown, Microsoft’s “convert anything to Markdown” tool. Guides the LLM to choose the right path for requests to convert PDF/PPT/Word/Excel/images/audio/web pages/YouTube to Markdown: the markitdown-awesome overview, markitdown-cli command guidance, or the markitdown-ocr LLM Vision OCR path. Use this skill when users mention markitdown, microsoft/markitdown, converting Office documents to markdown, OCR for scans, or related alternatives (textract, unstructured, pandoc).
Bootstrap or maintain MkDocs Material docs sites with GitHub Pages, strict two-pass i18n plus default-language llms.txt, copy-to-LLM, page/nav helpers, and zh-TW translation. Use when setting up or publishing docs, adding bilingual or multilingual docs, repairing nearly empty llms.txt or i18n strict-build failures, or migrating an older mkdocs-site-bootstrap site. Consent-gated; never rewrites existing docs without approval.
Analyses a Non-Disclosure Agreement clause by clause and flags unusual terms, one-sided provisions, and negotiation points. Use when reviewing an NDA, mutual NDA, confidentiality agreement, or non-disclosure deed before signing or countering. Produces a plain English verdict, clause-by-clause risk analysis, and a prioritised negotiation checklist — always with a disclaimer that qualified legal advice is required before signing.
Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions and knowledge from chat context, formats them appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.
PDF processing tool supporting scanned-document preprocessing, OCR dual-layer PDFs, page numbering, PDF merging, decryption, watermark removal and compression. Use this skill when the user needs one-click processing, optimisation or tidy-up of PDF documents. Not for: plain-text PDF content editing, PDF reading and annotation, electronic signatures, or format conversion for purposes other than compression.
Expert in PlantUML diagramming language. Automatically invoke when users need to visualize processes, systems, architectures, workflows, data structures, or relationships between components. This includes when users describe how things connect, request flow documentation, explain system interactions, show lifecycle states, or need to communicate design visually - even if they don't explicitly say "diagram", "PlantUML", or "UML". Covers sequence, class, activity, use case, state, component, object, and flowchart diagrams.
Design presentation slides, infographic pages, and PPT-style visuals as 1600x900 HTML slides with optional PPT export. Use when the agent needs to pick or explain a slide style, recommend styles based on content, generate one or more static HTML slides, support `background_mode` paper or white for compatible light styles, or render finished slides into a high-fidelity image-based PPTX.
Document any business process in a clear, structured format. Use when asked to document a process, write a process guide, create a workflow document, or map out how something works. Produces a complete process document with steps, roles, inputs, outputs, and edge cases.
Reverse-engineer and write a complete, readable, traceable PRD and comprehensive project documentation site based on the existing project directory, source code, tests, product descriptions, user stories, and architecture materials. Use for tasks such as “generate a PRD from the codebase,” “organize project materials into VitePress documentation,” or “complete user stories, use cases, business processes, Mermaid/C4 diagrams, and acceptance criteria.”
Senior Quality Documentation Manager for comprehensive documentation control and regulatory document review. Provides document management system design, change control, configuration management, and regulatory documentation oversight. Use for document control system implementation, regulatory document review, change management, and documentation compliance verification.
Guides writing of competitive research grant proposals for NSF, NIH, DOE, DARPA, and Taiwan NSTC. Covers agency-specific formatting and review criteria, specific aims, project descriptions, significance and innovation narratives, broader impacts, budgets and justifications, timelines, biosketches, and the NSTC CM03 form. Use when drafting a proposal for one of these agencies. Use when writing specific aims or broader impacts statements. Use when preparing a budget justification or milestone plan. Use when responding to a solicitation, BAA, or reviewer comments in a resubmission. Use when checking a draft against page limits and submission requirements. For general manuscript writing, use a scientific writing skill instead.
Write or audit technical text against ASD-STE100 Simplified Technical English so a tired, non-native reader understands it on the first pass: 20-word procedural and 25-word descriptive sentence limits, imperative steps, condition before command, one word for one meaning, and only the approved modals can/will/must. Use for READMEs, runbooks, procedures, error messages, release notes, incident reports, API guides, UI copy, and agent instructions. Trigger on: "STE", "Simplified Technical English", "ASD-STE100", "controlled language", "plain English", "make this clearer", "write for non-native readers", "prep this for translation", "cut the fluff", or any request to check text for compliance. Prefer this over general copy-editing whenever the text instructs, documents, or warns.
Draft Project Manual specification sections from accepted project requirements using CSI MasterFormat identities, three-part sections and review flags. Use for design requirements; use product-cut-sheet for source-faithful product entries and epd-to-spec for EPD requirements.
This skill should be used when generating lesson summaries for educational content. It extracts key concepts, mental models, patterns, and common mistakes from lesson markdown files using a Socratic extraction process. Use this skill when a lesson file needs a `.summary.md` companion file, or when reviewing/refreshing existing summaries.
Implements the Syncfusion ASP.NET MVC PDFViewer for embedding, configuring, and loading PDF documents. Use this when rendering PDFs in ASP.NET MVC applications, embedding viewer controls, or generating Razor page (.cshtml) code for PDF display and interaction.
The Pelosi Tracker. Watches the stock trades members of Congress must disclose under the STOCK Act: reads the House Clerk's public Periodic Transaction Reports (PTRs) as soon as they are posted, alerts once per new filing, and turns each PDF into clean rows (who, owner, stock, ticker, buy or sell, options strike and expiry, trade date, amount range, how many days it took to disclose). Flags trades in stocks you hold. Senate reports are covered by a documented manual route. Use when the user says "what is Pelosi buying", "track Nancy Pelosi", "Congress trades", "politician stock trades", "did any congressman buy X", "alert me when Pelosi files", or "run the Pelosi skill".
Extract all 3rd-party (non-owned) addresses from a TRES Finance environment and export them as an XLSX workbook to help users build their contacts list. Use this skill whenever the user wants to export, list, or identify 3rd-party addresses, counterparties, or external addresses from their transactions — even if they don't say 'contacts'. Also trigger when the user asks to prepare a contacts import file, find unknown addresses, or build an address book from transaction history. Do NOT trigger for viewing existing contacts or searching the address book — only for extracting NEW 3rd-party addresses from transaction data.
Import contacts (address book entries) into TRES Finance from a CSV or XLSX file. Use this skill whenever the user wants to import, upload, or bulk-add contacts, address labels, or address book entries into TRES — whether from a file they filled in after using the export-3rd-party-contacts skill, or from any CSV/XLSX that maps addresses to names. Trigger phrases include: 'import contacts', 'upload contacts', 'add contacts from file', 'import address book', 'load contacts into TRES', 'bulk label addresses', 'import the contacts file', 'upload the filled contacts sheet'. Also trigger when the user says something like 'I filled in the contacts file, now import it' or 'here is my contacts spreadsheet, please upload it to TRES'. Do NOT trigger for exporting or extracting unidentified addresses — that's the export-3rd-party-contacts skill. Do NOT trigger for viewing or searching the existing address book.
Create (generate) any TRES Finance report end-to-end via the tres-mcp MCP server and GraphQL — trigger the export, verify a report row was actually created (guarding against silent failures), poll until done, and return the download link. Trigger this skill on ANY report creation request, including phrases like "create a report", "generate a report", "export", "run a report", "I need a Transaction Ledger / Balances / Reconciliation / Cost Basis / Roll Forward / Staking / Audit report", "pull the data for", "download a report for", "give me a CSV/XLSX of", or whenever the user wants TRES to produce a report file. Use together with tres-report-advisor when the user is unsure which report they need.
The exact column header names required by the TRES Finance bulk transaction CSV upload. Use whenever building, fixing, or validating the header row of a TRES manual transaction or sub-transaction upload CSV — especially after an upload fails with \"Missing required column(s): ...\". Trigger phrases include: 'fix my CSV headers', 'bulk transaction upload failed', 'missing required columns', 'validate TRES upload CSV', 'transaction CSV template headers'. This skill is ONLY about the header naming convention; it does not cover row values or upload workflow. Do NOT trigger for contacts import CSV (use tres-import-contacts), wallet upload CSV (use tres-wallets-upload), or general CSV parsing unrelated to bulk TX upload headers.
Fetch article bodies from a single article URL or an article index/archive page and save them to local Markdown. Must be used first when the user mentions "save article", "save webpage", "batch fetch articles from a page", "pull the first N articles from this archive page", or "save to Obsidian / Clippings / local". Especially suited to public webpages, Substack, blog article pages, and article archive pages. When facing lazy-loaded lists, dynamic pages, or incomplete static fetching, first use browser to collect article URLs, then call the script to save them in batch, prioritizing success rate.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g. adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Tool for querying and exporting financial statements of A-share listed companies. Supports the three main statements — balance sheet, income statement, and cash flow statement — plus financial summaries, with queries by reporting period/year/single quarter and export to Excel. Trigger words: 查财报, 财务报表, 资产负债表, 利润表, 现金流量表, 财务数据, 上市公司财报, 导出财报, 年报, 季报. Use this skill whenever the user mentions any A-share company's financial data, financial statement analysis, or the three main statements.
Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.
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.