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. 79 600 files from 1 763 authors, of which 61 947 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.
> Home Assistant custom integration development in Python. Covers custom_components, DataUpdateCoordinator, config_flow, OAuth2, conversation agent, HACS publishing, device registry, entity platforms, services, repair issues, diagnostics, Bluetooth integrations, and multi-coordinator patterns.
Fetches live AI crypto trading signals with entry price, stop-loss, take-profit, leverage, confidence scores, and automated verification. Covers 50+ coins including BTC, ETH, SOL. Use when the user asks for crypto signals, trade ideas, market direction, portfolio analysis, or wants to build a trading bot.
>- Apple HIG guidance for presentation components including alerts, action sheets, popovers, sheets, and digit entry views. Use this skill when the user says "should I use an alert or a sheet," "how do I show a confirmation dialog," "when should I use a popover," "my modals are annoying users," or asks about alert design, action sheet, popover, sheet, modal, dialog, digit entry, confirmation dialog, warning dialog, modal presentation, non-modal content, hig-components-menus, hig-components-controls, hig-components-search, hig-patterns.
>- notifications, complications, home screen quick actions, top shelf, watch faces, "notification design", "complication", "home screen quick action", "top shelf", "watch face", "app clip", "app shortcut", "system experience". Also use when the user says "how do I design a widget," "what should my notification look like," "how do Live Activities work," "should I make an App Clip," or asks about surfaces outside the main app. interaction patterns, hig-technologies for Siri and system integration.
>- Apple HIG guidance for navigation-related components including search fields, page controls, and path controls. Use this skill when the user says "how should search work in my app," "I need a breadcrumb," "how do I paginate content," or asks about search field, search bar, page control, path control, breadcrumb, navigation component, search UX, search suggestions, search scopes, paginated hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.
>- Apple Human Interface Guidelines for layout and navigation components. Use this skill when the user asks about "sidebar", "split view", "tab bar", "tab view", "scroll view", "window design", "panel", "list view", "table view", "column view", "outline view", "navigation structure", "app layout", "boxes", "ornaments", or organizing content hierarchically in Apple apps. Also use when the user says "how should I organize my app", "what navigation pattern should I use", "my layout breaks on iPad", "how do I build a sidebar", "should I use tabs or a sidebar", or "my app doesn't adapt to different screen sizes". navigation, hig-patterns for multitasking and full-screen, hig-components-content for content display.
>- Apple HIG guidance for menu and button components including menus, context menus, dock menus, edit menus, the menu bar, toolbars, action buttons, pop-up buttons, pull-down buttons, disclosure controls, and standard buttons. Use this skill when the user says "how should my buttons look," "what goes in the menu bar," "should I use a context menu or action sheet," "how do I design a toolbar," or asks about button design, menu design, context menu, toolbar, menu bar, action button, pop-up button, pull-down button, disclosure control, dock menu, edit hig-components-search, hig-components-controls, hig-components-dialogs.
>- Apple HIG guidance for status and progress UI components including progress indicators, "progress bar", "loading spinner", "status bar", "activity ring", "progress display", determinate vs indeterminate progress, loading states, or fitness tracking rings. Also use when the user says "how do I show loading state," "should I use a spinner or progress bar," "what goes in the status bar," or asks about activity indicators. hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.
>- Apple Human Interface Guidelines for content display components. Use this skill when the user asks about "charts component", "collection view", "image view", "web view", "color well", "image well", "activity view", "lockup", "data visualization", "content display", displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says "how should I display charts", "what's the best way to show images", "should I use a web view", "how do I build a grid of items", "what component shows media", or "how do I present a share sheet". visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
>- Apple HIG guidance for selection and input controls including pickers, toggles, sliders, steppers, segmented controls, combo boxes, text fields, text views, labels, token fields, virtual keyboards, rating indicators, and gauges. Use this skill when the user says "picker or segmented control," "how should my form look," "what keyboard type should I use," "toggle vs checkbox," or asks about picker design, toggle, switch, slider, stepper, text field, text input, segmented control, combo box, label, token field, virtual keyboard, rating indicator, gauge, form design, input validation, or control state management. hig-components-search.
>- Apple Human Interface Guidelines interaction and UX patterns. Use this skill when the user asks about "onboarding flow", "user onboarding", "app launch", "loading state", "drag and drop", "search pattern", "settings design", "notifications", "modality", "multitasking", "feedback pattern", "haptics", "undo redo", "file management", data entry, sharing, collaboration, full screen, audio, video, haptic feedback, ratings, printing, help, or account management in Apple apps. Also use when the user says "how should onboarding work", "my app takes too long to load", "should I use a modal here", "how do I handle errors", "when should I ask for permissions", "how to show progress", or "what's the right way to confirm a delete". hig-components-layout for navigation, hig-components-content for data display.
>- Create or update a shared Apple design context document that other HIG skills use to tailor guidance. Use when the user says "set up my project context," "what platforms am I targeting," "configure HIG settings," or when starting a new Apple platform project. Also activates when other HIG skills need project context but none exists yet. This skill creates .claude/apple-design-context.md so that hig-foundations, hig-platforms, hig-components-*, hig-inputs, and hig-technologies can provide targeted advice without repetitive questions.
>- HomeKit, ARKit, machine learning, generative AI, iCloud, Sign in with Apple, SharePlay, CarPlay, Game Center, in-app purchase, NFC, Wallet, VoiceOver, Maps, "HealthKit", "HomeKit", "ARKit", "augmented reality", "machine learning", "generative AI", "iCloud sync", "Sign in with Apple", "SharePlay", "CarPlay", "in-app purchase", "NFC", "VoiceOver", "Maps", "Mac Catalyst". Also use when the user says "how do I integrate Siri," "what are the Apple Pay guidelines," "how should my AR experience work," "how do I use Sign in with Apple," or asks about any Apple framework or service integration.
>- Apple Human Interface Guidelines for platform-specific design. Use this skill when the user asks about "designing for iOS", "iPad app design", "macOS design", "tvOS", "visionOS", "watchOS", "Apple platform", "which platform", platform differences, platform-specific conventions, or multi-platform app design. Also use when the user says "should I design differently for iPad vs iPhone", "how does my app work on visionOS", "what's different about macOS apps", "porting my app to another platform", "universal app design", or "what input methods does this platform use". hig-components-layout for navigation structures, hig-components-content for content display.
>- keyboards, game controllers, pointers, Digital Crown, eye tracking, focus system, remotes, spatial interactions, gyroscope, accelerometer, and nearby interactions. "game controller", "pointer support", "mouse support", "trackpad", "Digital Crown", "eye tracking", "visionOS input", "focus system", "remote control", "gyroscope", "spatial interaction". Also use when the user says "what gestures should I support," "how do I add keyboard shortcuts," "how does input work on Apple TV," "should I support Apple Pencil," or asks about input device handling. hig-technologies for VoiceOver and Siri.
>- Apple Human Interface Guidelines design foundations. Use this skill when the user asks about "HIG color", "Apple typography", "SF Symbols", "dark mode guidelines", "accessible design", "Apple design foundations", "app icon", "layout guidelines", "materials", "motion", "privacy", "right to left", "RTL", "inclusive design", branding, images, spatial layout, or writing style. Also use when the user says "my colors look wrong in dark mode", "what font should I use", "is my app accessible enough", "how do I support Dynamic Type", "what contrast ratio do I need", "how do I pick system colors", or "my icons don't match the system style". patterns, hig-components-layout for structural components, hig-components-content for display.
Your habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or reviews code, debugs, plans, or writes commits. If .dna.md does not exist yet, start the onboarding conversation before doing anything else. Active in almost every working session.
Report deck generator / data-report presentation builder — turns a data report into a 16:9 web-based slide deck (1600×900 design canvas, auto-scaled to the browser), playable fullscreen with one-click PDF export. Per-slide split source + physical data separation + switchable themes + ECharts charts. **Always use this skill** when the user asks to "make a monthly/quarterly report", "make a work-report deck", "turn data into a web/PDF presentation", or wants to reuse a "one file per slide, data stored separately, themes switchable" deck template. Even if the user never says "PPT" or "slides", any time the task is to turn "several datasets + conclusions" into a presentable/shareable web report, follow this skill's workflow.
汇报 PPT 生成器 / 数据报告演示稿生成工具——把数据汇报做成 16:9 网页版 PPT（设计稿 1600×900，浏览器自适应缩放），可全屏播放、一键导出 PDF。分页拆分源码 + 数据物理分离 + 多主题可切换 + ECharts 图表。当用户要"做月度/季度汇报"、"做工作汇报 PPT"、"把数据做成网页/PDF 形式的演示稿"，或希望复用一套"每页一个文件、数据单独存放、主题可换"的 PPT 模板时，**务必使用本 skill**。即使用户没说"PPT"二字，只要任务是把"多组数据 + 结论"产出为可演示/可分享的网页报告，也按本 skill 的工作流走。
Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.
Prioritize assumptions by risk and importance. Use after assumption mapping to decide what to test first.
Surface and categorize assumptions underlying product strategy. Use early in development to document what you're betting on.
Turn ideas into designs through collaborative dialogue. Use before any creative work - features, components, or modifications.
Identify the pivotal obstacle between current state and desired future. Use when developing strategy.
Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.
Analyze competitors using Porter's four-component model - drivers, assumptions, strategy, capabilities.
Generate rigorous stakeholder challenge questions for proposal or meeting preparation.
Create structured records of decisions with expected outcomes, probabilities, and quit conditions. Use for important decisions.
Classify decisions as Hat/Haircut/Tattoo by reversibility. Use to calibrate how much analysis a decision deserves.
Define clear decision rights - Decider, Approver, Veto, Consulted, Informed. Use when clarifying who decides.
Improve executive updates for clarity, decision impact, and concise speaking flow.
Check Google Calendar for today's schedule. Use during daily planning or when user asks about their calendar.
Design robust experiments to test product hypotheses. Define metrics, sample size, and success criteria.
Design implementation-ready frontend solutions with UX intent, component structure, responsive behavior, accessibility, and handoff criteria.
Prepare for challenging conversations using Prepare-Listen-Empathize-Clarify-Solve framework.
Sync new Granola meetings to local Knowledge folder. Use during daily planning, when user asks "what should I do today", or asks to review/sync meetings.
Clean up raw interview transcripts while preserving meaning and speaker voice. Use after conducting interviews.
Analyze interviews using Jobs to Be Done framework. Extract push, pull, anxiety, and habit forces.
Generate influence strategies using Cialdini's seven principles. Use when you need to influence toward an outcome.
Formulate clear, testable hypotheses for product experiments. Use when designing experiments to validate solutions.
Identify potential hidden agendas of stakeholders. Use before high-stakes meetings with complex motivations.
Summarize meetings using IDEAS framework - Insights, Decisions, Engagements, Actions, Summary. Use after any meeting.
Cluster forces from multiple JTBD interviews to identify patterns. Use after extracting from multiple interviews.
Structure thinking using Mutually Exclusive, Collectively Exhaustive categories. Use when breaking down problems or ensuring complete coverage.
Develop a limit-based product strategy with convergence milestones, acceleration levers, assumptions, and phased execution.
Sync Linear issues with local tasks. Use during daily planning or when user asks about Linear issues.
Behavioral guardrails to reduce common LLM coding mistakes with a caution-first approach.
Map meeting-specific power dynamics, influence ranking, and tactical recommendations.
Design audience-specific framing, drafts, and communication sequence for stakeholder updates.
Normalize and collect complete Opportunity Solution Tree inputs before OST synthesis.
Transform research into Opportunity Solution Tree (Teresa Torres method). Map outcomes, opportunities, solutions, and experiments.
Select one target opportunity from an OST using evidence-based weighted scoring and tie-breakers.
Write a structured PRD for high-risk, cross-team, or multi-sprint initiatives before implementation.
Uncover root causes through recursive Why questioning and consequence exploration. Use before acting on problems.
Break down complex problems into actionable recommendations using deductive and inductive analysis.
Map stakeholders by power and interest to plan engagement strategy. Use when starting multi-stakeholder initiatives.
Design efficient early signals to validate assumptions. Find the fastest way to learn if you're right.
Check Slack for important messages and activity. Use during daily planning or when user asks about Slack updates.
Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.
Four-phase debugging process - root cause first, then fix. Use when encountering bugs or unexpected behavior.
Claude Skills — questions
Answers built from the skills we actually parsed.