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.
Guide for creating AL tests for Microsoft Dynamics 365 Business Central. Use this when asked to write, create, or generate AL test codeunits, test procedures, or test automation for Business Central.
> Лёгкий советник «раздвигающий шторки» — premortem-сессия которая находит дыры в плане с разных углов, предлагает варианты решений по каждой и помогает юзеру быстро принять осознанные решения. История запусков сохраняется в ./docs/premortem/. Use when user types «премортем», «premortem», «найди дыры в плане», «посмотри со стороны на план», «what could kill this plan». questions; creative editing of a draft; already-irreversible decisions.
> Track and analyze FII/DII daily buy/sell flows in Indian markets. Use when user asks about institutional flows, FII selling/buying trends, DII activity, or institutional impact on Nifty/market direction.
Analyze news headlines, policy announcements, or geopolitical events to build 18-month probabilistic scenarios for Indian markets. Use when the user provides a headline or asks about the market impact of RBI policy, government announcements, global events, budget, or sector-specific news on NSE/BSE stocks.
Use when user requests analysis of Indian stocks, fundamental assessment, technical review, comparisons, or investment reports for NSE/BSE listed companies.
> Options strategy analysis for Indian F&O markets (NSE). Use when user requests options strategy recommendations, P/L analysis, Greeks calculation, risk management, or F&O strategy planning for Nifty, Bank Nifty, or stock options.
Track and analyze Indian stock market news, corporate announcements, SEBI circulars, bulk/block deals, and earnings calendars. Auto-fetches headlines from MoneyControl, Economic Times, LiveMint, BSE/NSE filings. Use when the user asks about recent news, corporate actions, upcoming events, or wants a daily market news briefing for NSE/BSE.
> Expert guidance for systematic backtesting of trading strategies on Indian markets (NSE/BSE). Use when developing strategies, testing robustness, avoiding overfitting, or validating trading ideas.
Screen Nifty 500 stocks for Mark Minervini's Volatility Contraction Pattern (VCP) — identifying Stage 2 uptrends with tightening price ranges and declining volume before potential breakouts. Use this skill when the user requests VCP screening, Minervini-style setups, Stage 2 breakout candidates, or volatility contraction patterns on NSE/BSE stocks.
> Analyze Indian market breadth health using advance/decline data, stocks above moving averages, new highs/lows, and sector participation. Use when assessing rally quality, market participation width, or equity exposure levels for NSE/BSE.
This skill should be used when analyzing weekly price charts for Indian stocks (NSE/BSE), indices (Nifty 50, Bank Nifty, Sensex), or any other instrument. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance levels, scenario planning, or probability assessments based purely on chart data without consideration of news or fundamental factors.
> Weekly F&O trade planning skill for Indian markets. Analyzes news/macro events, identifies trending sectors and instruments, determines probable direction, suggests option strategy with entry/exit levels, and manages stop-loss and profit booking after position entry. Use when user wants a weekly trade idea, F&O direction call, or ongoing position management for Nifty, Bank Nifty, or stock options.
Transform conversations and discussions into structured Notion documentation
Parse specifications and create implementation plans with task tracking in Notion
Prepare for meetings by gathering context and creating comprehensive agendas
Research topics and document findings in Notion with organized structure and sources
Comprehensive, research-backed Hinge dating profile optimization. Use when someone wants to improve their Hinge profile, audit an existing profile, write better prompts/captions, select and order photos strategically, or understand why they're not getting quality matches. This is the thorough process (~45 mins) - discovery interview, honest market math, photo strategy, copy creation, settings cleanup, and implementation support. Grounded in peer-reviewed behavioral research, platform data, and signaling theory.
> and rendered preview PDFs. Use when the user needs a cohesive design system before building a deck, presentation, document, or any visual project. Works for consulting engagements, product pitches, personal brands, or any context requiring a unified visual language. Produces a markdown design brief, a JS config, and a preview PDF.
> Create presentation decks as high-fidelity PDF files using web technology (HTML, CSS, Tailwind, Font Awesome). Use when the user wants a polished, pixel-perfect deck with responsive layouts, rich typography, icons, and modern design. For editable PPTX output, use deck-design-ppt instead.
> Create new presentation decks as native editable PPTX files with consulting-quality design. Use when the user wants to build a new slide deck, presentation, or pitch deck from a brief or topic. For editing existing .pptx files, use the pptx skill instead.
> Think and deliver like a management consultant from McKinsey, BCG, or Bain. hypothesis-driven decomposition, (2) Run strategy analysis with professional McKinsey verdict-first, BCG framework-first, or Bain decision-first, board presentations, conference talks. Produces structured analysis and deliverable CONTENT. For visual production, hand off to a delivery skill for slides, documents, or spreadsheets.
Use at the start of any multi-step task and during exploration — before reading files, searching, or re-checking completed work, especially when tempted to read whole files, re-verify known facts, or run independent lookups one at a time.
Use before claiming anything works, is fixed, is done, or passes; before status updates on changes you haven't run; before agreeing with someone else's claim about your work; and before state-changing commands like restarts, deletes, or config edits.
Use when writing or editing code in an existing codebase — before adding comments, docstrings, try/catch blocks, validation, logging, or TODOs the surrounding file doesn't have, and before explaining your style choices in the reply.
Use before ending any turn that used tools or produced a deliverable — when tempted to ask "Want me to…?", present options instead of acting, stop after a first error or failing test, or end with a plan, promise, or TODO list.
Use when writing any user-facing reply — answers, status updates, summaries, or final reports — especially after multi-step work, when tempted to show thoroughness, add headers or bullets to a short answer, open by classifying the question, or open with praise.
Use when implementing any change in existing code — when tempted to clean up nearby code, add unrequested validation or options, fix something "arguably in scope", or when the diff is growing past what was asked.
| Use this skill for ANY financial market, investment, or macro-economic analysis. BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.
Automated QA testing using playwright-cli (CLI tool, NOT MCP tools). Provisions a test user, opens a headless browser, logs in, navigates to target pages, takes screenshots, and generates a REPORT.md. Two modes: VERIFY (reproduce a bug before fixing) and CHECK (confirm a fix works). Use this skill whenever the user says 'QA this', 'test this fix', 'verify this bug', 'smoke test', 'check if this works', 'reproduce this issue', 'run playwright QA', or 'playwright-qa-cli'. Also triggered from /fix-ticket at pre-fix and post-fix stages. Works for any page or user flow — not limited to specific features.
Agent Teams PR review with Devil's Advocate. Spawns 5 team members — 4 specialist reviewers + 1 adversarial challenger — to produce confidence-rated findings. Only findings that survive cross-examination make the final report.
> Create KPI docs, compensation structures, screening questions, and hiring templates for any contractor role. Use this skill whenever the user wants to hire someone, set KPIs, define compensation, create a job post, write screening questions, or build a hiring doc — for ANY role including community managers, YouTube managers, producers, marketers, developers, VAs, or any contractor. Also trigger when the user says "set KPI", "hiring doc", "job post", "comp structure", "screening questions", or "Fiverr post".
Automated review-fix loop that spawns 8 reviewers in parallel, fixes quick-fix items automatically, and accumulates strategic items for user decision. Iterates until no issues remain or max iterations reached.
Automate the full Jira bug-fix pipeline end-to-end. Use when the user says 'fix ticket', 'fix PROJ-123', 'fix this bug', 'resolve PROJ-XXX', 'fix and ship this ticket', or passes a Jira ticket ID for autonomous bug resolution. Reads the Jira ticket, implements the fix, reviews it, commits, moves the ticket to QA, assigns to QA engineer, and comments with a summary. Also use when the user wants to automate the fix-review-commit-handoff cycle for any Jira bug ticket.
This skill should be used when the user asks to "develop a feature", "implement a ticket", "build PROJ-123", "run the development pipeline", "develop this ticket end to end", or wants fully autonomous feature implementation with parallel research agents, planning, phased implementation, review, and PR creation. Zero checkpoints; pauses only on blockers.
Scan all unresolved Sentry errors, group by root cause, fix in batch with TDD, and resolve in Sentry after deploy. Use when the user says 'fix sentry errors', 'scan sentry', 'resolve sentry issues', 'fix all errors', 'sentry cleanup', or wants to proactively fix production errors from Sentry monitoring.
Competitor content gap analysis — extracts ALL comments from competitor and your own YouTube videos, identifies what audiences want but aren't getting, ranks gaps by engagement, and proposes video ideas. Use when the user says "scoop," "content gap," "analyze competitor videos," "what should my next video be about," "find content gaps," or "competitor analysis.
Formats all Telegram bot replies to be short, scannable, and properly styled with MarkdownV2. Use when replying to Telegram messages via the Telegram MCP plugin — ensures bold, emojis, bullet points, and correct special character escaping.
Home network architecture from scratch — gateway placement, switch and AP selection, IP addressing scheme design, DHCP scoping, and common setup mistakes for homelab beginners.
BGP neighbor state analysis, stuck session troubleshooting, AS path inspection, route filtering, and peering issue diagnosis on Cisco IOS/IOS-XE and multi-vendor devices.
Multi-vendor network device SSH automation using Python Netmiko — connecting, sending commands, parsing output, handling enable mode, error handling, and batch operations across device lists.
Pre-deployment validation of Cisco IOS/IOS-XE configuration — catching missing saves, mismatched ACLs, overlapping subnets, duplicate IPs, missing route-maps, and dangerous commands before they cause outages.
Cisco IOS and IOS-XE configuration syntax, show commands, privilege levels, config mode navigation, wildcard masks, and the most common operational gotchas.
Diagnosing network interface errors including CRC errors, input/output drops, runts, giants, duplex mismatches, flapping, and speed negotiation failures on Cisco IOS/IOS-XE devices.
| Extract artists from concert/festival lineups and create playlists to preview their music.
| (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays
| brainstorm, ideate, generate ideas, run a design thinking session, create How Might We statements, use SCAMPER, do Crazy 8s, mind map, storyboard, define a problem statement, create empathy maps, build prototypes, test assumptions, run design sprints, reframe problems, do "worst possible idea", use "yes and" building, explore analogous inspiration, conduct user interviews, synthesize insights, create POV statements, plan user tests, iterate on concepts, or facilitate any creative problem-solving session.
Make responses easy to start, scan, and complete - action first, numbered steps, minimal cognitive load, no repetition or filler. Use for ANY request that would otherwise get a long or multi-part answer: how-to and setup questions, multi-step tasks, comparing options, planning work, debugging walkthroughs, or explaining a system. Also use when the user invokes it directly, says they have ADHD, asks to be brief or to cut the fluff, or shows signs of executive dysfunction, overwhelm, decision paralysis, or task paralysis ("I don't know where to start", "this is too much", "I keep putting this off", "just tell me what to do").
> 🤖 Data Science & AI/ML skill suite derived from alirezarezvani/claude-skills. Data pipelines, model training, evaluation, MLOps and analytical reporting. Provides 10 specialised commands for data-science, machine-learning, analytics workflows.
> 📈 SEO & Content Marketing skill suite derived from borghei/Claude-Skills. Keyword research, content audits, SERP analysis, technical SEO and content strategy. Provides 10 specialised commands for seo, content, marketing workflows.
Autonomously research an ML task and run MANY bounded experiments to find the best config — a fixed-budget edit→train→eval→keep-or-discard loop in the spirit of karpathy/autoresearch, wrapped in the ml-intern orchestrator model and fanned out with a Claude Code dynamic workflow. Runs LONG: an iterative generational loop (mims-harvard/AutoScientists style) where parallel agent teams propose hypotheses, peer-critique them before spending any GPU, share findings on a common board, promote a champion, and keep going until budget/stagnation/convergence. Triggers when the user wants to "run many experiments", "sweep / search for the best config", "beat a benchmark", "do an ablation", "autoresearch X", "run for a long time / overnight / for days", or "find what improves metric Y on dataset Z". Deep-researches existing solutions across the internet FIRST (fan-out web search + PapersWithCode + GitHub, sources cross-checked into a cited DEEPRESEARCH.md), then ASKS where to get GPUs ("cards") and data before spending any compute, generates an experiment matrix seeded from diverse literature angles, runs it as a background workflow under an explicit budget, keeps a running leaderboard + shared findings board, verifies winners, and reports the best config. Reuses ml-intern's notify.sh + hf_push.sh for milestone alerts and HF Hub publishing.
Design an end-to-end MotherDuck data pipeline. Use for ETL/ELT workflows -- choosing raw, staging, and analytics boundaries, bulk ingestion paths, transformation sequencing, dlt/dbt integration, publication targets, or whether DuckLake is actually required.
Design a MotherDuck-backed customer-facing analytics app. Use for embedded analytics, multi-tenant SaaS reporting, or product analytics for external users -- whenever the decision depends on per-customer isolation, backend routing, service-account boundaries, read scaling, or Hypertenancy-style patterns.
Create, edit, manage, share, or embed MotherDuck Dives — live React + SQL dashboards, charts, and data apps saved in the workspace. Use for any dashboard, chart, KPI display, or data visualization over MotherDuck data, and for Dive authoring mechanics such as get_dive_guide, useSQLQuery, local preview, version history, Dives-as-code, required resources, team sharing, or embedded Dive sessions.
DuckDB SQL reference for MotherDuck. Use when you need exact DuckDB syntax or function behavior, friendly SQL features like QUALIFY, GROUP BY ALL, or list/struct types, MotherDuck-specific SQL such as shares, secrets, snapshots, or UNDROP, or to fix SQL errors and PostgreSQL-style SQL that fails on MotherDuck.
Connect to MotherDuck from any application. Use when setting up database connectivity via the Postgres endpoint (recommended), pg_duckdb, native DuckDB API, or JDBC. Covers connection strings, authentication, SSL, and environment variable configuration.
Build a live MotherDuck dashboard as a Dive. Use when composing one shareable KPI, trend, and breakdown story over existing MotherDuck data, especially when the result should stay a saved workspace artifact rather than a full application.
Create, schedule, run, and debug MotherDuck Flights — Python jobs that run on MotherDuck compute. Use whenever someone wants to create a flight, schedule a Python script or recurring job on MotherDuck, set up scheduled ingestion from Postgres, dlt sources, S3, BigQuery, Snowflake, or APIs, refresh aggregates or transformations on a cron, or operate flights with get_flight_guide, create_flight, run_flight, flight logs, secrets, schedules, and versions.
Design or redesign a MotherDuck Dive as a responsive, reusable analytics interface. Use when a Dive must be mobile-friendly from the start, support light and dark modes, reserve space for filters, use restrained Power BI-style information design, embed small charts inside metric components, or work across customers without one-off layout changes.
Design and build database schemas and data models in MotherDuck. Produces a file-based SQL project scaffold with a model manifest. Use for any schema design or data modeling task — creating tables, choosing data types, star schemas, wide denormalized tables, raw/staging/analytics layers, dbt-style transformation projects, or restructuring data for analytics workloads.
Deliver repeatable MotherDuck architectures across multiple clients. Use when a consultancy, agency, or multi-client product team needs to standardize isolation, provisioning, regional deployment, sharing boundaries, and client-specific exceptions across client engagements.
Claude Skills — questions
Answers built from the skills we actually parsed.