Explore skills
Showing 23341–23370 of 71536 skills
Use 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 CodeCodexUse for "are we advertising products about to sell out in our store", "which product ads should we pause for low stock", "move ad budget off low-stock products", "we're paying for clicks on sold-out sizes", or a Cyber Monday stock check against the ads. Use during Black Friday, BFCM, Prime Day or any store sale, when the decision is which product ads to pause or swap before the item runs out. Shopify plus Google Ads Shopping or Performance Max, or Meta catalog ads.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "how did our Black Friday go", "Black Friday sales report", "BFCM post-mortem", "did our Black Friday ads make money after returns", "compare this Black Friday to last year", or "what do we change for next year's sale" — even when the user never says "post-mortem". Use after a Black Friday, Cyber Monday, Prime Day or store sale, when the decision is what to keep and change next time. Google Ads, Facebook Ads, TikTok Ads and Shopify.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "are our ads ready for Black Friday", "what should we fix in the ad accounts before Black Friday", "how should we ramp the Black Friday ad budget", "will our tracking hold up on Cyber Monday", or a BFCM or Prime Day prep check 4–6 weeks out. Use when the decision is what to fix and how to ramp budget before the sale. Google Ads, Facebook Ads and TikTok Ads, with Shopify where connected.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "which campaigns should we scale today on Black Friday", "what should we cut during the sale", "are we on track to spend the Black Friday ad budget", "why did our CPA jump on Cyber Monday", or a daily check inside a BFCM or Prime Day sale. Use when the decision is today's scale, cut or hold, with the wait stated for conversions still arriving. Google Ads, Facebook Ads and TikTok Ads, with Shopify where connected.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "how did our ads do last Black Friday", "which campaigns actually drove store sales last BFCM", "which products carried last year's Black Friday", "when did our Black Friday orders peak last year", or "how much did CPMs rise last Black Friday". Use weeks before a Black Friday, Cyber Monday or Prime Day sale, when the decision is what to repeat and what to drop. Google Ads, Facebook Ads, TikTok Ads and Shopify.
coupler-io/skills
Stars: 41Claude CodeCodexAnalyze marketing performance data using Coupler.io MCP tools (list-dataflows, get-schema, get-data). Use when the user asks to pull or analyze data from Coupler.io dataflows/data sets, generate marketing performance reports, understand campaign ROI, or investigate changes in business metrics. Make sure to use this skill whenever the user mentions Coupler.io data, marketing dashboards, channel comparisons, campaign analysis, or asks questions like "why did conversions drop", "which channel has best ROI", "where should I spend more", "what's working", "show me my marketing numbers", "pull my latest data", even if they don't explicitly say "marketing analytics". For deep paid-ads-only analysis (per-platform ad efficiency, budget pacing, brand vs non-brand, ad fatigue), use the ppc-analytics skill instead — this skill owns the cross-channel view.
coupler-io/skills
Stars: 41Claude CodeCodexUse this skill when the user wants to analyze sales pipeline, review win rates, investigate sales velocity or cycle length, build a sales report, evaluate rep performance, look at lead source quality, or answer questions about their CRM data. Triggers include 'how is the pipeline', 'win rate by segment', 'sales cycle', 'pipeline coverage', 'rep performance', 'forecast accuracy', 'why are deals stalling', 'lead source quality', 'stage conversion', 'pull my Salesforce numbers', 'HubSpot deals report', 'sales report'.
coupler-io/skills
Stars: 41Claude CodeCodexUse for "which of our pages do ChatGPT, Perplexity or Gemini cite", "does our AI search visibility bring traffic, signups or sales", "is our Peec visibility worth anything", "which AI-cited pages or products make us money", "GEO funnel", "AI search to revenue", or when someone uploads Peec AI (or Profound, Otterly, Scrunch and similar) citation exports and wants them tied to results — even when they never say "funnel". Follows your cited URLs to AI-referred, organic, referral and direct sessions in GA4, Search Console clicks and impressions, the GA4 key events you choose, and the business outcome — orders, won deals or payments from Shopify, WooCommerce, HubSpot, Pipedrive, Salesforce, Stripe and similar — and names the stage where the chain breaks. Runs on Coupler.io; missing sources are offered and connected. For AI-referral traffic against organic with no citation data, use ai-traffic-vs-organic-search-report.
coupler-io/skills
Stars: 41Claude CodeCodexBuild a live Cowork artifact (persistent HTML widget) backed by a Coupler.io dataflow. Use this skill whenever the user wants a live dashboard, persistent widget, daily-check page, or interactive explorer over Coupler.io data — including phrases like "live artifact for Coupler", "Coupler dashboard widget", "build a widget over a Coupler dataset", "Coupler.io live dashboard", "build a daily dashboard from a Coupler dataflow", or any time they ask to render Coupler data in a re-openable view that auto-refreshes. Triggers even when the user does not say "skill" or "artifact" but describes the same outcome (e.g. "I want a page I can check every morning that pulls my Coupler data").
coupler-io/skills
Stars: 41Claude 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 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: 70Claude 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: 628Claude CodeCodexComplete research methods for in-depth analysis, long-form reports, revisions and updates.
rrrrrredy/research-toolkit
Stars: 315Claude CodeCodexImplement a Linear issue when given a Linear issue ID or URL. Use when the user invokes /implement-issue or asks to implement, build, or complete a specific Linear issue from an issue key, issue ID, or Linear URL.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexUse this skill to write or revise a README.md for a Shipfox workspace package (libs/*, tools/*). It applies the shared package README standard and repository prose policy. Trigger on write a README, draft README, rewrite README, document this package, or improve the README.
ShipfoxHQ/shipfox
Stars: 89Claude CodeCodexThe checks to run before adding, updating or removing a third-party package, in any ecosystem (npm, cargo, pip, a vendored tool). Covers need, security history, maintenance, install scripts, release age, licence, the size of the tree it brings, and where the dependency is declared. Use before any install or version change, and when choosing between a library and a few lines of your own code. Triggers - "add a dependency", "install a package", "bun add", "cargo add", "bump this package", "which library should we use", "do we need a library for this".
kromatv/kroma
Stars: 81Claude CodeCodexSpawn the comment hunter, fix accepted findings, and offer encodings for claimed constraints.
kromatv/kroma
Stars: 81Claude CodeCodexGround platform and integration code in documented facts instead of memory. Before writing code that depends on how an external platform, SDK, protocol or vendor behaves (key names, manifest fields, event payloads, threading rules, supported formats, store requirements), read the project's reference docs for that area; when the fact is missing, research it from the official source, cite it, and add it to the reference in the same change. Use when implementing or debugging native, OS, device, SDK or third-party integration code, or when a behaviour "should" work a certain way. Triggers - "how does the platform handle", "what key name", "is this supported on", "according to the docs", "port to a new platform", "native module", "why does the TV".
kromatv/kroma
Stars: 81Claude CodeCodexRust best practices. Use when reading or editing any .rs file, designing a crate's public API, choosing an error type, splitting a workspace, or writing async code on tokio. Triggers - "rust best practices", "is this idiomatic", "should this be a newtype", "anyhow or thiserror", "why does the borrow checker", "review this Rust".
kromatv/kroma
Stars: 81Claude CodeCodexSecurity guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
kromatv/kroma
Stars: 81Claude CodeCodexWrite the failing test before the code that satisfies it, for new behaviour and for bug fixes, and stop when the test path is not worth its cost. Covers the red-green loop, what a first test should assert, when to skip the loop honestly, and the evidence to report. Use when starting behaviour that has a cheap test path, or fixing a bug that can be reproduced in a test. Triggers - "tdd", "write a failing test first", "regression test", "reproduce this in a test", "test first".
kromatv/kroma
Stars: 81Claude CodeCodexTypeScript best practices. Use when reading or editing any .ts or .tsx file, designing a module's public types, fixing a type error, choosing between type and interface, or setting up tsconfig, and whenever a diff reaches for any, as, ! or @ts-ignore. Triggers - "typescript best practices", "is this type safe", "how should I type this", "review this TS", "any vs unknown".
kromatv/kroma
Stars: 81Claude CodeCodexFollow the reduced principles when writing or changing code. Every change follows First Make it Work, then Then Make it Right, then Follow Practice. Use when the user runs /ub-mode or asks for the reduced principles.
kromatv/kroma
Stars: 81Claude CodeCodexCut AI tells from any writing. Use for every piece of prose that ships - docs, READMEs, commit messages, PR descriptions, release notes, changelogs, UI copy, chat answers - and as a final pass before handing work back. Triggers - "unslop", "de-slop", "remove the slop", "sounds like ChatGPT", "make it sound human", "too wordy", "cut the fluff". Must always apply.
kromatv/kroma
Stars: 81Claude CodeCodexReview Data Designer changes for correctness, architecture, public contracts, and meaningful test gaps.
NVIDIA-NeMo/DataDesigner
Stars: 2.4kClaude CodeCodex