Claude Skills
The open format is called Agent Skills and works in Claude Code, Codex, Cursor and other agents — most people know it as Claude Skills.
Every Agent Skill we could find on GitHub, deduplicated by content. 86 696 files from 2 113 authors, of which 68 413 are unique — the rest is the same skill repackaged into someone else's repository. For each one: what it weighs in tokens, whether it ships runnable scripts, and which MCP servers it needs.
Implement tabbed navigation with Syncfusion MAUI TabView. Covers tab setup, customization, selection events, nested tabs, swiping gestures, and visual state management.
Implements Syncfusion .NET MAUI Text Input Layout (SfTextInputLayout). Use when adding decorative elements like floating labels, icons, assistive labels, or containers to Entry, and Editor controls. Covers text input layout setup, hint labels, helper text, error messages, character counter, and password visibility toggle.
Implements Syncfusion .NET MAUI TimePicker (SfTimePicker) control. Use when implementing time selection, time picker controls, or time input UI in .NET MAUI. This skill covers installation, configuration, time formats (14 predefined formats), picker modes (Dialog/RelativeDialog), intervals, time restrictions, looping, events, and customization.
Themes and styles Syncfusion .NET MAUI components. Use when working with SyncfusionThemeResourceDictionary, MaterialLight, MaterialDark, visual themes, or theme switching. This skill covers theme customization, color overrides, theme keys, dark mode, light mode, and branding.
Automates macOS apps via Apple Events using AppleScript (discovery), JXA (legacy), and PyXA (modern Python). Use when asked to "automate Mac apps", "write AppleScript", "JXA scripting", "osascript automation", or "PyXA Python automation". Foundation skill for all macOS app automation.
Automates macOS Messages (iMessage/SMS) via JXA with reliable service→buddy resolution. Use when asked to "automate iMessage", "send Messages via script", "JXA Messages automation", or "read Messages history". Covers send-bug workarounds, UI scripting for attachments, chat.db forensics, and launchd polling bots.
Automates Apple Mail via JXA with AppleScript dictionary discovery. Use when asked to "automate email", "send mail via script", "JXA Mail automation", or "filter email messages". Covers accounts, mailboxes, batch message filtering, composition, attachments, and UI fallback.
Automates macOS Calendar via JXA with AppleScript dictionary discovery. Use when asked to "create calendar events", "automate calendar", "JXA calendar scripting", "EventKit automation", or "PyXA calendar automation". Covers events, calendars, recurrence, time zones, batch operations, and EventKit ObjC bridge.
Automates Microsoft Excel on macOS via JXA with AppleScript dictionary discovery. Use when asked to "automate Excel spreadsheets", "JXA Excel scripting", "Excel macOS automation", or "bulk Excel data operations". Focuses on workbooks, worksheets, ranges, 2D arrays, performance toggles, and VBA escape hatches.
Automates Apple Keynote using JXA with AppleScript dictionary discovery. Use when asked to "create Keynote presentations", "automate slide decks", "JXA Keynote scripting", or "generate presentations programmatically". Covers document lifecycle, slides, text, shapes, images, tables, charts, transitions, and UI scripting fallback.
Automates Google Chrome and Chromium-based browsers via JXA with AppleScript dictionary discovery. Use when asked to "automate Chrome tabs", "control browser with JXA", "Chrome AppleScript automation", "Chromium browser scripting", or "browser tab management". Covers windows, tabs, execute(), tunneling patterns, and permissions.
Automates macOS Contacts via JXA with AppleScript dictionary discovery. Use when asked to "automate contacts", "JXA contacts automation", "macOS address book scripting", "AppleScript contacts", or "Contacts app automation". Covers querying, CRUD, multi-value fields, groups, images, and ObjC bridge fallbacks.
Automates Microsoft PowerPoint via JXA with AppleScript dictionary discovery. Use when asked to "automate PowerPoint presentations", "create slides programmatically", "JXA PowerPoint scripting", or "export PowerPoint to PDF". Covers presentations, slides, shapes, text, tables, export enums, and interop with Excel.
Automates Apple Numbers via JXA with AppleScript dictionary discovery. Use when asked to "automate Numbers spreadsheets", "create spreadsheets programmatically", "JXA Numbers scripting", or "bulk data operations in Numbers". Focuses on sheets, tables, ranges, batch I/O, clipboard shim, and high-performance data workflows.
Automates Apple Pages using JXA with AppleScript dictionary discovery. Use when asked to "automate Pages documents", "create documents programmatically", "JXA Pages scripting", or "export Pages to PDF". Covers documents, templates, text, styles, export, tables, images, and AppleScript bridge fallbacks.
Comprehensive macOS browser automation using PyXA, Playwright, Selenium, and Puppeteer for desktop web testing, scraping, and workflow automation. Use when asked to "automate web browsers", "Selenium Chrome automation", "Playwright testing", "Puppeteer scraping", or "cross-browser automation". Supports Chrome, Edge, Brave, Arc browsers.
Automates Apple Notes via JXA. Use when asked to "create notes programmatically", "automate Notes app", "JXA notes scripting", or "organize notes with automation". Covers accounts/folders/notes, HTML bodies, queries, moves, and Objective-C/UI fallbacks for Notes.app automation on macOS.
Automates Apple Voice Memos (Mac Catalyst, no dictionary) via JXA using filesystem/SQLite access and System Events UI scripting. Use when asked to "automate Voice Memos", "export voice recordings", "access Voice Memos database", or "transcribe voice memos".
Automates Apple Reminders using JavaScript for Automation (JXA). Use when asked to "create reminders programmatically", "automate reminder lists", "JXA Reminders scripting", or "manage reminders via automation". Covers list/reminder management, filtering with 'whose' queries, efficient creation via constructors and push operations, and copy-delete patterns for moving items.
Automates Microsoft Word via JXA with AppleScript dictionary discovery. Use when asked to "automate Word documents", "find and replace in Word", "JXA Word scripting", or "create Word documents programmatically". Covers documents, ranges, find/replace, tables, export, and ObjC bridge patterns.
将用户已授权账号中的抖音视频收藏或用户明确指定的喜欢列表配置并同步到本地 Markdown 或 Obsidian 知识库；默认收藏，只有用户明确说喜欢/点赞才切换来源。首次明确选择推荐的百炼转录、本地 Whisper 或不转录。不得绕过登录、访问他人账号或泄露 Cookie 与私密数据。
为中文微信公众号文章分析内容并生成清晰易懂、真实 3D 毛毡质感且图文一体的头条长封面、1:1 分享页封面与正文配图，同时给出每张正文图应插在哪个原句之后。用于用户提供文章、Markdown 或正文，并要求“公众号封面”“分享封面”“方形封面”“毛毡配图”“文章插图”“为正文配图”“只做封面”“生成 N 张配图”“推荐配图数量”等任务；未提供文章标题时默认根据核心命题生成合适的封面文字，正文图未指定画幅时默认 16:9，也支持用户明确指定 4:3 或 3:4，并使用少量毛毡文字帮助单图理解；适配方法论、教程、专业干货、商业科技、情感叙事、个人成长、生活方式、教育与母婴等内容。
Use only for Bricks Builder-specific questions about elements, hooks, schema, controls, templates, styling, dynamic content, setup, or integrations when the local Bricks Academy corpus should be checked first. Do not use for generic WordPress, PHP, CSS, JavaScript, or unrelated web development questions unless they are clearly about Bricks.
Build, rewrite, QA, and expand one-page HTML/PDF resumes from existing resumes, Word/PDF materials, portfolios, websites, or user notes. Use this skill whenever the user asks to create, iterate, polish, migrate, export, or design resume/CV templates as HTML/PDF. Covers 12 bundled A4 templates, strict layout and typography gates, one-page density adaptation, STAR wording, content preservation rules, QR/avatar handling, and scripted export + screenshot QA.
> Automatically triggered when setting up Python code quality tooling, configuring linters, adding type checking, improving code standards, running code quality checks, setting up ruff setup, mypy configuration, code formatting, linting rules, cyclomatic complexity, dead code detection, file length limits, pre-commit hooks, Makefile targets for quality, uv-based workflows, pyproject.toml configuration, or "check my code quality". "run quality checks", "set up pre-commit", "code smells", "clean up this code", "add code quality", "quality gate", "CI quality pipeline".
> Automatically triggered when running security scans, auditing code for vulnerabilities, checking dependencies for CVEs, reviewing code for security issues, or hardening Python pip-audit, dependency vulnerabilities, OWASP, injection, path traversal, secrets detection, insecure deserialization, auth bypass, or "is this code secure?". "check for CVEs", "audit dependencies", "security lint", "pen test this code", "harden this application", "check for secrets", "SAST scan", "code security scan", "security pipeline", "supply chain security".
> Use when going beyond basic linting to enforce advanced Python code quality gates. import boundaries, dependency hygiene, test quality beyond coverage, mutation testing, docstring coverage, type coverage, AI-generated code detection, AI slop detection, complexipy, jscpd, import-linter, deptry, diff-cover, mutmut, interrogate, sloppylint, refurb, pylint design checks, wily, radon maintainability, pytestarch, griffe, "bulletproof Python", "tighten quality gates", "advanced quality checks", "beyond ruff and mypy", "catch AI-generated code issues", "code duplication", "architectural boundaries", "dependency drift", "test effectiveness". Complements the code-quality skill (ruff, mypy, xenon, vulture, pre-commit) with 20+ additional tools.
> Apply Sam Dumont's personal writing voice and style when drafting reports, blog posts, technical documentation, client communications, Slack messages, LinkedIn posts, or any written content. Use this skill whenever Sam asks to write, draft, review, or improve text in his voice - including phrases like "write this for me", "draft a post", "in my style", "my voice", "write a report", "blog post", "client email", "Slack message", or any content creation task where Sam's personal tone should come through. Also trigger when Sam asks to translate content while maintaining his voice. Works in both English and French.
> Use when starting significant features, evaluating build-vs-buy decisions, reframing failed approaches, or when the user mentions "outcome engineering", "o16g", "outcome-first", "what's the outcome", or "frame this as an outcome". Also use proactively when a task description focuses on implementation ("build X", "add Y") without defining the desired outcome or verification criteria.
> Use when the user asks to check if a band is sketch, fascist, NSBM, or far-right. "check [band] for fascist ties", "is [band] NSBM?", "is [band] fash?", "should I listen to [band]?", "is [band] problematic?", "are [band] nazis?", "RABM check", "band vetting", "is it sketch", "sketch report", "any red flags for [band]", "does [band] have far-right connections", "sketch check", "vet this band", "is [band] safe to support".
Use when writing a technical blog post from raw project data like research notes, session logs, Reddit/LinkedIn drafts, code, hex dumps, or screenshots. Also use when Sam says "write a blog post about [project]" or "turn this into a post".
> Automatically triggered when designing system architecture, planning new projects, creating implementation plans, conducting architecture reviews, or auditing existing architectural patterns, infrastructure decisions, API design, testing strategies, CI/CD pipelines, security architecture, or code organization. Works for Python web APIs, infrastructure/DevOps, Garmin/embedded systems, and frontend projects. Distinguishes between personal projects (strict standards) and client work (adaptive approach).
| Inspect, build, and verify Office documents (PPTX, DOCX, XLSX) using the oxen CLI. (3) Previewing slide/document/sheet content in terminal, (4) Extracting text or data, (5) Verifying build results, (6) User asks about ".pptx", ".docx", ".xlsx" inspection or generation.
| Create and modify PowerPoint presentations (PPTX) through direct XML manipulation. (3) Inserting images or custom shapes, (4) Applying POTX templates for consistent branding, (5) Editing existing PPTX files, (6) Working with slide layouts and placeholders, (7) User asks to make a "presentation", "slides", "deck", or mentions ".pptx". Supports all 11 standard Office slide layouts.
Create excellent technical documentation with Mermaid diagrams. Use when documenting code architecture, API flows, database schemas, state machines, system design, or any technical concept that benefits from visual diagrams. Also use when asked to explain code, create documentation, write README files, or document how systems work.
Executes OpenAI Codex CLI for code analysis, refactoring, and automated editing. Activates when users mention codex commands, code review requests, or automated code transformations requiring advanced reasoning models.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: \"Index this repo\", \"Reanalyze the codebase\", \"Generate a wiki\
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: \"How does X work?\", \"What calls this function?\", \"Show me the auth flow\
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: \"What GitNexus tools are available?\", \"How do I use GitNexus?\
> Facilitate structured brainstorming sessions as a coach and hybrid thinking techniques (SCAMPER, Six Thinking Hats, reversal, analogical thinking, question storming, role playing…), one technique at a time, with the user generating ideas first and the AI building on them with clearly labeled additions — then converge, categorize, and deliver a session document with priorities and next steps. Use this skill whenever the user wants ideas or wants to think out loud together — "brainstorm with me", "give me ideas for…", "help me come up with…", "let's explore options for…", "I'm stuck on the name / the features / the campaign angle" — in any language (e.g. Vietnamese "brainstorm cùng tôi", "cho tôi ý tưởng", "nghĩ cùng tôi xem", "gợi ý phương án giúp tôi"; Spanish "ayúdame a generar ideas"; Japanese 「アイデア出しを手伝って」), even when they never say the word "brainstorm". Trigger for open-ended exploration of a topic, product, name, feature set, campaign, event, career move, or any generative question that does not first require diagnosing why something is broken. Also trigger when the user asks for multiple perspectives on their ideas or a structured devil's-advocate pass — "give me different angles on these ideas", "phản biện mấy ý tưởng này giúp tôi", "party mode" — the skill's party mode handles multi-role ideation and counterpoint. (If the request is "X is failing and we don't know why", root-cause diagnosis comes first — the problem-solver skill in this family leads there; if the question is who the users are and what they need, with real research, design-thinking leads; company-level strategic bets belong to strategy-board.)
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: \"Why is X failing?\", \"Where does this error come from?\", \"Trace this bug\
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: \"Rename this function\", \"Extract this into a module\", \"Refactor this class\", \"Move this to a separate file\
> Audit the reasoning of any document or argument — a memo, proposal, investment analysis, board paper, article, or the user's own draft — and fallacies, and what would falsify it, with every finding anchored to exact quoted text. Runs a commit-first coaching loop that asks for the user's own judgment before revealing the audit, tracks their recurring blind spots in a persistent reasoning profile, and turns every audit into a rep that sharpens the user's thinking instead of replacing it. Use this skill whenever the user wants reasoning examined — "audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft", "what's wrong with this reasoning" — in any language (e.g. 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ì", "đánh giá đề xuất này giúp tôi", "góp ý bản nháp của tôi"; Spanish "analiza los argumentos de esta propuesta"; Chinese "帮我审一下这份提案的论证"; Japanese "この提案の論理をチェックして"; French "analyse les failles de ce raisonnement"), even when they never say "critical thinking". Also trigger when the user drops a document and asks whether to trust or act on it, or asks to see their thinking progress / reasoning profile. (Company-level strategic bets with a full analysis belong to strategy-board; learning a new topic through dialogue belongs to socratic-questor — this skill leads when the question is whether a specific piece of reasoning holds up, and it is the daily-driver for document-level judgment calls.)
> data problem, explore and audit datasets, run defensible statistical analysis, build and validate predictive models, and turn results into decision-ready reports. Use this skill whenever the user asks to analyze, explore, or profile a dataset or CSV/Parquet/Excel file; asks what drives a metric or why a number changed ("why did churn go up?"); wants to test whether a difference is real (A/B tests, experiments, "is this significant?", "how many samples do I need?"); wants a predictive model (churn, forecast, scoring, segmentation, classification, regression); asks to review an existing analysis, notebook, or model for flaws; or needs analysis results written up for decision-makers — in any language ("phân tích dữ liệu", "xây model dự đoán", "kiểm định A/B"), even when they never say "data science" or "statistics".
Score candidate CVs on a 100-point scale against a Job Description. Use this skill when the user wants to evaluate, score, rank, or screen candidate CVs/resumes against a JD. Also trigger when the user mentions 'review CV', 'screen resume', 'rate candidates', 'shortlist', or any context involving matching resumes to job requirements.
>- Deep-read long books and papers using Mortimer Adler's inspectional / analytical / syntopical method, the Recite step from SQ3R, and S. Keshav's three-pass method for papers, with page-anchored notes as external memory so the agent never has to load the whole text into one context window. Use this skill whenever the user asks to read, study, summarize, analyze, review, or answer questions about a long book, textbook, PDF, EPUB, thesis, dissertation, survey paper, or any document of roughly 50+ pages. Also use it when a `<slug>-notes/` workspace from a previous session already sits next to a source file and the user asks a follow-up question about that book — search the existing notes before re-reading anything. Trigger on these requests in whatever language the user writes them — for example Vietnamese "đọc sách", "tóm tắt sách", "phân tích luận án", or equivalent phrasing in any other language. Do not use this skill for short documents (under ~30 pages) that fit comfortably in context — read those directly instead; the pipeline is overhead they don't need.
> Facilitate a full design-thinking engagement — Empathize, Define, Ideate, Prototype, Test — as a disciplined facilitator and thinking partner that observation plans, experiments with pass/fail criteria), the user brings back real data, and every insight traces to registered evidence. Use this skill whenever the user wants to understand users deeply and design a solution or experience for them — "run design thinking", "understand our users", "design user interviews", "synthesize these interview notes", "build personas", "write How-Might-We questions", "brainstorm solutions for…", "prototype this concept", "design an experiment / usability test to validate…", "our users are churning and we don't know why" — in any language ("tư duy thiết kế", "nghiên cứu người dùng", "phỏng vấn khách hàng", "デザイン思考", "设计思维"), even when the user never says "design thinking". Also trigger when the user drops raw interview notes, transcripts, or survey exports and wants them turned into insights, personas, or product decisions. (For "is there a market for X" desk questions, the market-researcher skill leads; this skill leads when the question is who the users are and what to build for them.)
>- Write, restructure, classify, and review documentation using the Diataxis framework. Use this skill whenever the user asks to create, improve, audit, or reorganize docs, documentation, knowledge bases, help centers, onboarding guides, internal process docs, manuals, runbooks, product docs, API/developer docs, tutorials, how-to guides, references, or explanations. Also use it when the user mentions Diataxis, tutorial, how-to, reference, explanation, docs taxonomy, documentation architecture, or asks why a document feels confusing. Do not use it for marketing copy, legal contracts, fiction, sales proposals, press releases, or persuasion-first writing unless the user explicitly wants a Diataxis-style documentation analysis.
> A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.
> scans, market sizing (TAM/SAM/SOM), competitor analysis, customer demand signals, and trend/macro (PESTEL) analysis. Use this skill whenever the user wants to research, size, validate, or enter a market — "is there a market for…", "how big is the market for…", "who are the competitors of…", "should I build/launch/sell…", "validate this business idea", "market research for…", "market entry" — in any language and for any country's market (e.g. "nghiên cứu thị trường", "étude de marché", "市場調査", "análisis de mercado"), even when the user never says the words "market research". Also use it when another skill or workflow (strategy-board, design-thinking, a product brief) needs external market facts delivered into its fact base or research folder.
> facilitator that turns "X is broken and we don't know why" into a precise problem statement, bounds it with Is/Is-Not analysis, finds root causes with the method that fits the problem's shape (Five Whys for linear chains, fishbone for multi-factor tangles, causal loops for systems that fight back), labels every causal claim verified or assumed, designs verification tests, then generates solutions traced to root causes, drives an evidence-cited decision, and plans rollout with pivot triggers. Use this skill whenever the user reports something failing, breaking, slowing, or recurring without a known cause — "sales dropped and we don't know why", "this keeps happening", "orders keep arriving late", "why does X keep failing", "find the root cause", "run a post-mortem", "5 whys" — in any language (e.g. Vietnamese "sao cứ bị vậy hoài", "tìm nguyên nhân gốc", "X đang hỏng "give me ideas to fix falling sales" is a diagnosis request wearing a brainstorm costume. Trigger for operational, process, technical, and business problems with an unknown or unverified cause. (If nothing is broken and the user wants open-ended ideas, brainstorm-coach leads; if the problem is really about understanding users and their behavior — churn driven by what users feel and need — design-thinking leads; company-level strategic bets belong to strategy-board.)
> Act as a disciplined product manager copilot that turns evidence into prioritization with sensitivity analysis, PRDs with story maps and user stories, north-star metrics and OKRs, experiment designs, launch plans with rollback criteria, feedback triage, platform-vs-feature decisions, and light pricing/packaging — all inside a persistent per-product workspace where every number declares its origin. Use this skill whenever the user wants to decide what to build, spec it, or ship it — "write a PRD for…", "prioritize our backlog / these features", "what should we build next", "plan OKRs for the quarter", "define our north star metric", "design an A/B test for…", "plan the launch of…", "triage this pile of customer feedback", "should this be a platform or a feature", "help me manage this product" — in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "lập kế hoạch ra mắt", "プロダクト管理", "产品经理"), even when the user never says "product manager". Also trigger when the user returns to an existing `<product>-pm/` workspace with any product question. (Deep user discovery belongs to design-thinking, desk market facts to market-researcher, company-level strategic bets to strategy-board — this skill leads when the question is what to build, in what order, and how to ship it.)
> Act as a disciplined project-management copilot (PM/PMO) that runs the delivery loop — initiation & charter, planning & scheduling, estimation with reference-class checks, risk management (ROAM), honest status reporting, scope change control, stakeholder communication, meetings turned into tracked actions, lessons learned, and portfolio roll-ups — methodology-agnostic (predictive, agile, hybrid) inside a fixed per-project `_project/` workspace where every status color, percent-complete, and estimate declares its evidence. Use this skill whenever the user wants to start, plan, track, rescue, or report on a project — "kick off this project", "make a project plan / timeline / WBS", "estimate how long this will take", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report for the steering committee", "the deadline slipped, what now", "turn this meeting transcript into action items and decisions", "prepare the steering-committee pack", "review my project portfolio" — in any language ("gestion de projet", "Projektmanagement", "quản lý dự án", "プロジェクト管理", "项目管理", "gestión de proyectos"), even when they never say "project management". Also trigger whenever a `_project/` directory exists in the working tree and the user asks anything about schedule, deadline, risk, status, scope, budget, or stakeholders. (What to build belongs to product-manager; company-level bets to strategy-board — this skill leads when the question is whether committed work will land on time, in scope, on budget, and who needs to know.)
>- Build interactive presentation websites — slide decks projected to a room, controlled by one presenter. Use this skill WHENEVER the user wants to create, build, or design a presentation, slide deck, talk, or "bài thuyết trình / slide / trình chiếu", and also when they ask to add/edit slides, restyle a deck, scaffold a new presentation project, reuse their presentation setup in another repo, or export slides to PDF — even if they don't say the word "slide" but clearly need projected talk visuals (e.g. "I'm giving a talk next week and need visuals", "dựng deck cho buổi chia sẻ", "làm mấy trang chiếu project. Do NOT use it for printable documents, normal web apps, or dashboards meant for individual users to interact with.
> Socratic questioning partner named Gadfly for deep learning through dialogue. Use this skill when the user wants to learn, understand, or explore a topic through questions rather than explanations. Trigger when the user says "teach me about...", "help me understand...", "I want to learn...", "ask me questions about...", "quiz me", "Socratic method", "Gadfly", or wants to deeply understand something through dialogue rather than passive reading. Also trigger when the user provides a text or document and wants to be questioned about it, or wants to check their own understanding of a concept.
> A C-level strategy advisory board, run as a team of named specialist agents, that takes an executive from a raw strategic question to a defended, board-ready recommendation. Use this skill whenever the user faces a significant business decision or wants strategic analysis — market entry, build-vs-buy, M&A, digital transformation, annual planning, portfolio prioritization, pricing, a big investment, a competitive threat, a turnaround. Trigger on requests like "should we invest in / build / buy / enter…", "develop a strategy for…", "evaluate this opportunity", "make the business case", "stress-test this plan", "run a pre-mortem", or "prepare a board presentation" — in any language, even when the user doesn't say the word "strategy". Also trigger when the user names a board member (Drucker, Porter, Christensen, Graham, Grove, Wack, Taleb, Minto) or asks to convene the board / open a boardroom session.
Create high-quality, model-aware system prompts for any LLM (Claude, GPT, Gemini, open-source, etc.). Use this skill whenever the user wants to create, write, build, design, draft, or improve a system prompt, system instructions, or custom instructions for any AI model. Also trigger when the user asks about prompt engineering, prompt design, prompt optimization, or wants to define behavior for an AI assistant, chatbot, agent, or any LLM-powered application — even if they don't explicitly say "system prompt". Covers all use cases including chatbots, agentic systems, tool-use workflows, content generation, data extraction, code assistants, and multi-turn conversations.
> Deploy OpenSearch search applications to Amazon OpenSearch Service or Amazon OpenSearch Serverless. Use this skill when the user wants to provision an OpenSearch domain or serverless collection on AWS, deploy search configurations to AWS, set up Bedrock connectors, configure IAM roles for OpenSearch, migrate a local search setup to AWS, or manage Amazon OpenSearch infrastructure. Activate even if the user says AOS, AOSS, OpenSearch Service, serverless collection, Bedrock connector, SigV4, or AWS deployment without mentioning search.
> Ingest documents at scale into Amazon OpenSearch using OpenSearch Ingestion Service (OSIS) pipelines. Upload pre-generated JSONL chunks to S3 and OSIS indexes them — optionally using semantic_enrichment in the sink to create the index with ASE automatically. Cloud ingestion — uploading raw PDF/DOCX and letting document_extractor parse them in the cloud — is available via private beta. Use this skill when the user wants to ingest documents into a cloud OpenSearch domain or collection, process documents at full volume beyond local limits, or set up an OSIS pipeline. Activate even if the user says OSIS, ingestion pipeline, document extraction, S3 ingestion, managed ingestion, or cloud processing.
Claude Skills — questions
Answers built from the skills we actually parsed.