Explore skills
Showing 23221–23250 of 71509 skills
Screens 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 CodeCodexComprehensive Windows privilege escalation methodology for offensive security engagements. Covers the full attack surface from a standard user shell to NT AUTHORITY\SYSTEM: token impersonation via SeImpersonate and SeAssignPrimaryToken privileges using JuicyPotato, PrintSpoofer, GodPotato, SweetPotato, and RoguePotato; service misconfigurations including unquoted service paths, weak service DACLs, writable service binaries, and insecure service creation permissions; AlwaysInstallElevated MSI exploitation; DLL hijacking through search order abuse, phantom DLL loading, and writable PATH directory injection; UAC bypass techniques via fodhelper.exe, eventvwr.exe, CMSTP, and environment variable manipulation; scheduled task abuse for writable task actions and new task creation; registry autorun exploitation for persistence and escalation; PrintNightmare (CVE-2021-34527) for remote and local privilege escalation; and credential harvesting from SAM database extraction, DPAPI blob decryption, LSA secret dumping, and Credential Manager enumeration. Integrates automated enumeration with WinPEAS, PowerUp, SharpUp, Seatbelt, and BeRoot. Each technique includes detection signatures and defender-side visibility for purple team operations. Maps to MITRE ATT&CK T1548 (Abuse Elevation Control Mechanism) and T1574 (Hijack Execution Flow). Designed for authorized penetration testing, red team engagements, and CTF competitions where you hold a standard user shell and need to escalate to SYSTEM or local Administrator.
SnailSploit/Claude-Red
Stars: 11kClaude 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 CodeCodexUse this skill when the user wants to analyze financial performance, review P&L health, monitor MRR/ARR, investigate margin or cost trends, build a finance report, check cash flow or runway, or answer questions about their accounting/billing data. Triggers include 'how is revenue trending', 'gross margin', 'MRR breakdown', 'churn impact on ARR', 'why did costs go up', 'operating expenses', 'cash runway', 'P&L review', 'EBITDA', 'cost per acquisition trend', 'pull my QuickBooks numbers', 'finance report'.
coupler-io/skills
Stars: 41Claude CodeCodexUse for QuickBooks questions like "how much working capital do we have in QuickBooks", "where is our cash tied up", "what's our current ratio", "how many days do customers take to pay us", "are we paying vendors too early", "what changed on the QuickBooks balance sheet this month", or "why is cash down when we made a profit" — even when the user never says "balance sheet". Use when the decision is whether the business can meet its short-term obligations and where cash is sitting. QuickBooks only; for Xero use xero-balance-sheet-and-working-capital.
coupler-io/skills
Stars: 41Claude CodeCodexUse for QuickBooks questions like "are our QuickBooks books clean", "can I trust the numbers in QuickBooks", "are we ready to close the month in QuickBooks", "does the QuickBooks trial balance balance", "how much is in Uncategorized Expense", "what's still uncleared in QuickBooks", "does receivables match the AR aging", or "did anything change before the closing date" — and before trusting any QuickBooks profit, cash or balance sheet figure, even when the user never says "audit" or "close". Use when the decision is whether the QuickBooks books can be reported on yet, not what they say. QuickBooks only; for Xero use xero-books-health-and-close-check.
coupler-io/skills
Stars: 41Claude CodeCodexUse for QuickBooks questions like "are we on budget in QuickBooks", "how did we do against budget last month", "which costs are over budget", "budget vs actuals in QuickBooks", "where are we year to date against plan", "will we hit the annual budget", or a monthly variance review — even when the user never says "variance". Use when the decision is which lines are off plan, by how much, and whether the full year still lands. Needs a budget entered in QuickBooks. QuickBooks only; for Xero use xero-budget-vs-actual-variance.
coupler-io/skills
Stars: 41Claude CodeCodexUse for questions across several QuickBooks companies like "combine our QuickBooks companies", "group P&L across all our QuickBooks entities", "consolidated balance sheet for the group", "how is the group doing across our QuickBooks companies", "eliminate intercompany between our QuickBooks entities", or "put our US and Canada QuickBooks books in one currency" — even when the user never says "consolidation". Use when the decision needs one set of group numbers from two or more QuickBooks companies. QuickBooks only, wholly owned entities; for Xero use xero-multi-entity-consolidation.
coupler-io/skills
Stars: 41Claude CodeCodexUse for QuickBooks questions like "how did we do last month in QuickBooks", "why did profit drop in QuickBooks", "what moved on our QuickBooks P&L", "why are costs up this month", "what's our gross margin in QuickBooks", "how does this month compare to last year", or a monthly P&L read from QuickBooks — even when the user never says "P&L". Use when the decision is what moved profit, by how much, and whether the move is real or a coding change. QuickBooks only; for Xero use xero-profit-and-loss-review.
coupler-io/skills
Stars: 41Claude CodeCodexUse for Xero questions like "how much working capital do we have in Xero", "where is our cash tied up", "what's our current ratio", "how many days do customers take to pay us", "are we paying suppliers too early", "what changed on the Xero balance sheet this month", or "why is cash down when we made a profit" — even when the user never says "balance sheet". Use when the decision is whether the business can meet its short-term obligations and where cash is sitting. Xero only; for QuickBooks use quickbooks-balance-sheet-and-working-capital.
coupler-io/skills
Stars: 41Claude CodeCodexUse for Xero questions like "are our Xero books clean", "can I trust the numbers in Xero", "are we ready to close the month in Xero", "does the Xero trial balance balance", "what's sitting in suspense in Xero", "what's still unreconciled in Xero", "does receivables in Xero match the open invoices", or "did anything change in a locked period" — and before trusting any Xero profit, cash or balance sheet figure, even when the user never says "audit" or "close". Use when the decision is whether the Xero books can be reported on yet, not what they say. Xero only; for QuickBooks use quickbooks-books-health-and-close-check.
coupler-io/skills
Stars: 41Claude CodeCodexUse for Xero questions like "are we on budget in Xero", "how did we do against budget last month", "which costs are over budget", "budget vs actual in Xero", "where are we year to date against plan", "will we hit the annual budget", or a monthly variance review — even when the user never says "variance". Use when the decision is which lines are off plan, by how much, and whether the full year still lands. Needs a budget entered in Xero. Xero only; for QuickBooks use quickbooks-budget-vs-actual-variance.
coupler-io/skills
Stars: 41Claude CodeCodexUse for questions across several Xero organisations like "combine our Xero companies", "group P&L across all our Xero entities", "consolidated balance sheet for the group", "how is the group doing across our Xero organisations", "eliminate intercompany between our Xero entities", or "put our UK and US Xero books in one currency" — even when the user never says "consolidation". Use when the decision needs one set of group numbers from two or more Xero organisations. Xero only, wholly owned entities; for QuickBooks use quickbooks-multi-entity-consolidation.
coupler-io/skills
Stars: 41Claude CodeCodexUse for Xero questions like "how did we do last month in Xero", "why did profit drop in Xero", "what moved on our Xero P&L", "why are costs up this month", "what's our gross margin in Xero", "how does this month compare to last year", or a monthly P&L read from Xero — even when the user never says "P&L". Use when the decision is what moved profit, by how much, and whether the move is real or a coding change. Xero only; for QuickBooks use quickbooks-profit-and-loss-review.
coupler-io/skills
Stars: 41Claude CodeCodex