Explore skills
Showing 25921–25950 of 77104 skills
Create a GitHub pull request from staged task changes or an already-committed current branch. Deliver source/config/ reference changes together with their computed source-owned `bin_artifacts` closure. PR validation routing is owned by the default-branch trusted workflow; snapshots, gamedata, and manifests are Release-derived only.
mrc4tt/CS2_VibeSignatures
Stars: 4Claude CodeCodexCreate a new find-XXXX preprocessor Python script from scratch (no existing SKILL.md), add configs/<GAMEVER>.yaml skill and symbol entries. Covers xref-string-based and LLM_DECOMPILE-based discovery patterns. Use when a GitHub issue or user instruction specifies a new function to find.
mrc4tt/CS2_VibeSignatures
Stars: 4Claude CodeCodexBatch-dump vtables from IDA Pro MCP by searching mangled symbol patterns, then write a merged YAML file beside the binary. Use this skill when you need to find and export all vtables matching a name pattern (e.g., all GameSystem vtables) in one shot. Triggers: dump vtables, batch vtable dump, export vtables, dump all vtables matching pattern
mrc4tt/CS2_VibeSignatures
Stars: 4Claude CodeCodexUpdate ClickUp User Documentation and internal support playbooks from a space/folder/doc link
daledesilva/obsidian_ink
Stars: 1.3kClaude CodeCodexHouse rules and craft for LaTeX Beamer slide decks (lectures, seminars, talks), drawn from the author's own Overleaf edits and published slide-design guidance. Covers storyboarding, frame titles, slide prose, word and frame budgets, layout without overfull boxes, XeLaTeX fonts and Korean (xeCJK), color, figures and screenshots, Overleaf source hygiene, speaker notes, and a build-and-QA loop with a contact sheet. Use when writing, editing, reviewing, or building a Beamer deck, theme, or storyboard. A course skill supplies course facts and the frame skeleton; this skill supplies the craft. Not for HTML or PowerPoint decks, posters, or papers.
scdenney/open-science-skills
Stars: 71Claude CodeCodexShow a nice greeting message with a timestamp. Use this when the user wants to greet or say hello, optionally to a certain subject <subject> and in a certain language <language>.
rse/ase
Stars: 77Claude CodeCodexScreens biomedical / life-science papers for signs of data fabrication, image manipulation, and statistical anomalies, using the detection techniques distilled from the field's canonical exposure platforms (PubPeer, Data Colada, Science Integrity Digest, For Better Science) and tools (ImageTwin/Proofig, statcheck, GRIM/GRIMMER, Problematic Paper Screener, Seek & Blastn). Use when asked to check a paper/figure for image duplication, blot splicing, impossible statistics, paper-mill or tortured-phrase signals, research integrity, or "is this data faked"; or when a user shares a figure, Western blot, supplementary dataset, or DOI and asks whether it looks manipulated. Reports observable anomalies as questions for clarification — it never accuses anyone of fraud.
agentsope/SkillAlchemy
Stars: 484Claude CodeCodexUse when implementing a PlayCanvas feature the project does not use yet, to find and adapt the official example matching the installed version.
playcanvas/skills
Stars: 43Claude CodeCodexUse when loading glTF/GLB models or textures in PlayCanvas, choosing Draco or Basis/KTX2 compression, or setting up decoders and preloading.
playcanvas/skills
Stars: 43Claude CodeCodexUse before writing PlayCanvas behaviour from scratch, to reuse the scripts and helpers the installed Engine already ships.
playcanvas/skills
Stars: 43Claude CodeCodexUse when someone asks "does this sound AI?", "check if this is AI-written", "what gives this away as AI", "run ai-check on this", or "score this text". Also use when reviewing a draft for AI tells before publishing, or when a piece of text reads as suspiciously polished, generic, or pattern-y and the user wants a forensic breakdown of why.
harshaneel/humanize
Stars: 631Claude CodeCodexReview Data Designer changes for correctness, architecture, public contracts, and meaningful test gaps.
NVIDIA-NeMo/DataDesigner
Stars: 2.4kClaude CodeCodexPrevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps. Use when generating, reviewing, refactoring, or migrating IaC and when building delivery/testing pipelines.
LukasNiessen/terrashark
Stars: 704Claude CodeCodexUse this skill when the user wants to create a new dataflow, set up a new data import, connect a new data source to a destination, pull data from an integration into Google Sheets or BigQuery or another destination, or configure a source-to-destination data pipeline. Triggers include: 'import my HubSpot data', 'set up a Stripe export', 'create a pipeline from X to Y', 'I want to pull data from [source]', 'create a new dataflow', 'connect [source] to [destination]', 'set up a data flow for [source]'.
coupler-io/skills
Stars: 41Claude CodeCodexUse this skill when the user wants to explore a dataset's context, or write or update documentation for the data it holds. Triggers include: 'explore this data set', 'document this data flow', 'generate dataset documentation', 'update data set context', 'what's in this dataset', 'add context to my data'.
coupler-io/skills
Stars: 41Claude CodeCodexUse this skill when the user needs Google Ads data that no packaged report type carries, or asks for a Custom GAQL source. Triggers include: 'I need a Google Ads field that isn't in any report', 'can I get hourly Google Ads data', 'break conversions down by action at ad group level', 'product-level Shopping data', 'write me a GAQL query', 'query the Google Ads API directly', or another Google Ads skill reporting that a metric exists in no report type. Configures the source; the analysis belongs to the skill that asked.
coupler-io/skills
Stars: 41Claude CodeCodexUse this skill to produce a structured business report from analysis output and validate it before delivery — turning metrics, findings, and recommendations into a scannable, decision-ready document, then sanity-checking arithmetic, units, claims, and consistency. Industry-agnostic; works for marketing, ecom, finance, sales, or any analytics output. Compose with a domain bundle (e.g., ecom-analytics + report-generation) for domain-flavored reports. Triggers include 'write a report', 'summarize this analysis', 'put this in a report format', 'create a TL;DR', 'monthly business review', 'weekly performance report', 'executive summary', 'structured update on …', 'turn this into a report', 'sanity-check these numbers', 'validate this analysis', 'does this add up', 'review this for accuracy'.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "when should we reorder in Cin7", "what's our reorder point for each SKU", "how many weeks of stock do we have in Cin7", "what will run out before the next delivery", "is our Cin7 reorder level set right", "how much safety stock do we need", or "what do we need to order this week" — even when the user never says "reorder point". Use when the decision is what to order, how much, and by when, per SKU and location. Cin7 Core only.
coupler-io/skills
Stars: 41Claude CodeCodexUse this skill when the user wants to analyze e-commerce performance, review funnel conversion, investigate AOV or repeat-purchase trends, build an ecom report, check sales velocity, understand customer cohorts and retention, or answer questions about their store's sales data. Triggers include 'how is my store performing', 'what's my conversion rate', 'cart abandonment', 'AOV trend', 'repeat purchase rate', 'why did revenue drop', 'cohort retention', 'top products', 'new vs returning customer revenue', 'lifetime value', 'pull my Shopify numbers', 'ecom report'.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "how many support tickets per order do we get", "why is our Gorgias volume up", "what are customers contacting us about", "how much of our support is where-is-my-order", "is our contact rate getting better", "which channel brings the most Gorgias tickets", or "what should we fix to cut support tickets for our store" — even when the user never says "contact rate". Use when the decision is which cause of support volume to fix first. Needs Gorgias and the store's Shopify orders.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "is our Klaviyo sending healthy", "are our emails going to spam", "why is our Klaviyo bounce rate up", "which campaign got spam complaints", "are we at risk with Gmail", "too many unsubscribes from Klaviyo", "should we sunset unengaged subscribers", or "check our email list health" — even when the user never says "deliverability". Use when the decision is whether sending is safe and which campaigns, flows or segments to stop or narrow. Klaviyo email only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "how are our Klaviyo flows doing", "is our abandoned cart flow good", "which Klaviyo flow underperforms", "how does our welcome series compare", "what should our flow revenue per recipient be", "which flows are we missing in Klaviyo", or "is our winback flow worth keeping" — even when the user never says "benchmark". Use when the decision is which automated flow to fix, build or leave alone. Klaviyo only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "how much of our store revenue comes from Klaviyo", "what share of Shopify sales is email and SMS", "is our Klaviyo pulling its weight", "flows vs campaigns revenue for our store", "what percent of store revenue is retention marketing", or "is email revenue going up as a share of the store" — even when the user never says "contribution". Use when the decision is whether email and SMS earn their place and whether effort goes to flows or campaigns. Needs Klaviyo and the store's Shopify data.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "what's our repeat rate", "do customers come back", "which campaign brings customers who buy again", "what's our customer lifetime value", "how long until the second order", "do discounted customers stick around", "are our cohorts getting worse", or "how much revenue comes from repeat customers" — even when the user never says "retention" or "cohort". Use when the decision is where acquisition money goes, or when retention email timing needs a number. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "are our store discounts worth it", "which discount codes work in our shop", "how much are we giving away in Shopify discounts", "is the welcome code bringing new customers", "how deep are our promo discounts", "do discounted orders have a bigger basket", "what discount can our store afford", or "did the sale make money" — even when the user never says "discount". Use when the decision is which codes and automatic discounts to keep, cut or resize, and what depth the store's margin can carry. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "what's about to run out", "what should I reorder", "when do I need to place the order", "how much stock do I have", "what's my inventory worth", "which SKUs are overstocked", "how much cash is sitting in dead stock", or "what's my sell-through" — even when the user never says "inventory". Use when the decision is what to order and by when, or whether a sales fall is a stock problem rather than a demand problem. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "which products are selling", "what are my best sellers", "which variants should I drop", "what's my margin by product", "which size sells", "how did the launch do", "what's my revenue concentration", or "sales by vendor" — even when the user never says "variant". Use when the decision is what to reorder, drop, promote or mark down, or when a store-level move needs tracing to the products behind it. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "what's our store's return rate", "which products get returned most in the shop", "which size gets sent back", "how much are refunds costing the store", "are returned items going back on the shelf", "why are our Shopify refunds up", "refunds vs returns for our store", or "how much stock do we write off from returns" — even when the user never says "returns". Use when the decision is which products, variants or policies to fix because of what comes back, and whether returned goods are recovered or lost. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "which countries buy from our store", "sales by country in Shopify", "how is our UK store market doing", "which states order most from the shop", "is international worth it for our store", "do customers in Germany return more", "how many orders are paid in local currency", or "should we localise the shop for a new market" — even when the user never says "geo" or "market". Use when the decision is which markets to invest in, localise, fix or stop serving. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodexUse for Shopify store questions like "how did the store do last month", "why did our store revenue drop", "what's our store's average order value", "how many orders did the shop take last week", "what's our store's refund rate", or a weekly or monthly trading check on the shop — even when the user never says "performance". Use when the decision is whether store revenue moved and which of orders, order size or returns moved it. Shopify only.
coupler-io/skills
Stars: 41Claude CodeCodex