Skills worth trusting.
Agent skills from Anthropic, OpenAI, skills.sh, ClawHub, SkillsMP and other reputable sources. Savant assesses them for security risks and evaluates model-generated test cases using independent scoring. Workspaces import any skill into their own repositories through a reviewed pull request. Every listing on each hub is enumerated; packages are fetched, scanned and evaluated most-popular first as daily capacity allows.
tiktok-growth
Use to grow a TikTok account — the TikTok-specific growth strategy that diagnoses where growth is stuck and orchestrates the other skills to fix it. Run when the user says "grow on TikTok," "TikTok growth," "get more followers/views on TikTok," "my TikTok isn't growing," "go viral on TikTok," or "TikTok strategy." Reads brand-profile, social-strategy, and audience first. Built on the 2026 reality that TikTok is an interest graph — follower count is not a ranking factor; completion rate and rewatches drive reach, and search/SEO is a major evergreen pillar. Diagnoses the broken stage of the test-and-expand loop and routes to the right skill (tiktok-script, hook-writer, profile-optimization, content-calendar, hashtag-strategy, trend-jacking, viral-reverse-engineering). Judges via native TikTok analytics — not WoopSocial analytics — and treats followers as a business asset, not the reach mechanism.
competitive-pricing-strategy
Build an evidence-based competitive pricing strategy for ecommerce products. Use when a seller asks how to position a price against competitors, set regular and promotional prices, protect contribution margin, design bundles or price tiers, respond to competitor moves, or coordinate prices across Amazon, Shopify, TikTok Shop, Walmart, eBay, or other channels. Do not use for automated repricing implementation or claims of a mathematically proven optimal price without sufficient data.
symfony:quality-checks
Run code quality tools: PHP-CS-Fixer for style, PHPStan for static analysis, and type safety checks
capacitor-plugin-upgrade-v5-to-v6
Upgrades a Capacitor plugin library from v5 to v6 using `npx @capacitor/plugin-migration-v5-to-v6@latest`, then the manual checklist - `@capacitor/*` dev deps to `latest-6`, `compileSdkVersion` replaced by `compileSdk`, compile/target SDK 34 defaults, AGP 8.2.1, Gradle 8.2.1, Kotlin 1.9.10, plus code changes - `addListener` in `definitions.ts` returns only `Promise<PluginListenerHandle>` (drop `& PluginListenerHandle`), remove `CAP_PLUGIN_METHOD(removeAllListeners, ...)` from the `.m` file, and optional experimental SPM support via `Package.swift`. Use when a plugin targets Capacitor 5 and must support 6. Do not use for app upgrades, other major versions, or non-Capacitor libraries.
repeated-component-alignment
Cards, rows, tiles and cells are fixed slot models that stay aligned when content length varies. Use when building or reviewing any repeated component.
cross-platform-repurposing
Use to turn one piece of content into multiple platform-native posts — adapt, never copy-paste. Run when the user says "repurpose this," "turn this into posts for every platform," "cross-post," "make this work on TikTok/LinkedIn/X too," "one idea into a week of content," "turn this blog/video/podcast into social posts," or wants to fan content out. Reads brand-profile and voice first, extracts the core idea, then re-natives it for each platform (different hook, format, length, mechanics, CTA) using the content skills, and hands the fan-out to scheduling-and-queue. This is the multiplier that makes a content operation sustainable — but every version must stand on its own and feel native, never duplicated.
social-strategy
Use to set a brand's overall social media strategy — which channels to focus on (and which to ignore), what to achieve, the angle to win, and a realistic operating cadence. The top-level plan that sits above content pillars and the calendar. Run when the user says "social strategy," "social media strategy," "which platforms should I be on," "what's my plan," "should I be on TikTok/LinkedIn," or is starting or resetting their social presence. Reads brand-profile, audience-research, and content-pillars first. Makes real choices and trade-offs — especially what NOT to do — ties goals to the business not vanity metrics, and is honest that WoopSocial has no analytics (measurement is the platforms' native analytics). Produces a social-strategy.md. It names the objective; to turn it into SMART targets, KPIs, and North Star metrics, use goals-and-kpis. Works for any business.
refactor
Code refactoring workflow - analyze → plan → implement → review → validate
helm-generator
Create, scaffold, or generate Helm charts, Chart.yaml, values.yaml, templates, helpers.
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
asb-interview-goals
Facilitates the first step of a proven customer-interview method: deciding exactly what you're trying to learn, written as numbered goal questions (G1, G2, …) that your hypotheses and interview questions will later be designed to answer. Interviews the user about their business — new idea or established company, B2B or B2C — then drafts a tailored goal-question list, critiques and revises it with them, and preserves the result in a GOALS.md file. Load when the user wants to interview customers, plan customer discovery or customer development, validate a startup idea, or answer unaskable questions like what to charge, how to position, who the ideal customer is, or what to build. Do NOT load for job or hiring interviews, for writing survey questionnaires, for analyzing customer interviews that have already been conducted, or when a goal-question list already exists and the user wants the next step (hypotheses).
account-opening-workflow
Design and operate back-office account opening pipelines from application intake through custodian submission and activation. Use when building account opening automation, reducing NIGO rejection rates from custodians or clearing firms, defining document requirements for trusts, entities, IRAs, or estate accounts, setting up multi-custodian account opening across Schwab, Fidelity, or Pershing, troubleshooting account opening failures or processing delays, or benchmarking cycle times and first-submission acceptance rates. For risk-based approval tiers and compliance screening requirements, see account-opening-compliance.
design-systems-frontend-architecture
Use when building reusable frontend systems, design tokens, component contracts, responsive layouts, CSS strategy, or design-system documentation and governance.
godot-2d-animation
Expert patterns for 2D animation in Godot using AnimatedSprite2D and skeletal cutout rigs. Use when implementing sprite frame animations, procedural animation (squash/stretch), cutout bone hierarchies, or frame-perfect timing systems. Trigger keywords: AnimatedSprite2D, SpriteFrames, animation_finished, animation_looped, frame_changed, frame_progress, set_frame_and_progress, cutout animation, skeletal 2D, Bone2D, procedural animation, animation state machine, advance(0).
godot-2d-animation
Expert patterns for 2D animation in Godot using AnimatedSprite2D and skeletal cutout rigs. Use when implementing sprite frame animations, procedural animation (squash/stretch), cutout bone hierarchies, or frame-perfect timing systems. Trigger keywords: AnimatedSprite2D, SpriteFrames, animation_finished, animation_looped, frame_changed, frame_progress, set_frame_and_progress, cutout animation, skeletal 2D, Bone2D, procedural animation, animation state machine, advance(0).
thumbnail-design
Design YouTube video thumbnails that earn the click — mobile-legible, one focal point, honest. Use when someone wants to design a YouTube thumbnail, improve CTR, brief a thumbnail, choose thumbnail text, or plan thumbnail A/B testing. Designs and briefs high-CTR thumbnails and writes the A/B test plan: a thumbnail is a promise, not a poster, designed as a unit with the title and legible on mobile. Uses the CLICK framework. Reads brand-profile + the video/title first. A HUMAN or an image/design tool (nano-banana/ideogram/Canva/designer) creates the final raster; the YouTube custom thumbnail is uploaded NATIVELY in Studio (WoopSocial has no thumbnail field) and Test & Compare is native; TikTok/IG-Reel covers use WoopSocial's cover field via those format skills. No clickbait, no unconsented real-person/deepfake faces, CTR never fabricated. Distinct from youtube-publishing-and-metadata (the metadata) and nano-banana/ideogram (which generate the raster this briefs).
design-and-templates
The reusable on-brand template-SYSTEM skill -- build a brand kit + a small set of reusable templates so a non-designer can produce consistent on-brand graphics fast across formats. Use when someone wants templates, a brand kit, a consistent visual system, or help choosing/using a design tool (Canva/Adobe Express/Figma). For social, consistency + speed beat bespoke. Uses the BRAND framework. Reads brand-profile first. The agent designs the SYSTEM (brand-kit tokens, template set, hierarchy rules, workflow); a design tool or the image tools produce the actual graphics; the finished asset enters the WoopSocial flow (WoopSocial publishes -- it does NOT design or generate). Honest about the ~70-80% on-brand ceiling and AI copyright limits. Distinct from brand-profile (the identity source), thumbnail-design + pinterest-pin-design (single asset types), carousel-writer (copy vs visual frame), and image-prompt + the image tools (generation vs layout).
recipe-send-personalized-emails
Read recipient data from Google Sheets and send personalized Gmail messages to each row.
gws-apps-script-push
Google Apps Script: Upload local files to an Apps Script project.
four-steps
Applies Steve Blank's Customer Development methodology from The Four Steps to the Epiphany. Use when a startup is searching for customers and a business model before scaling. Covers Customer Discovery, Customer Validation, Customer Creation, and Company Building. Triggers include 'we built it but no one's buying', 'should we hire salespeople yet', 'how do we find our first customers', 'we're burning cash and sales aren't scaling', 'are we in a new or existing market', 'when do we scale'. NOT for companies that have already crossed the chasm into mainstream (use Crossing the Chasm instead), not for optimizing an existing sales funnel, not for product development methodology (this is its companion, not replacement).
asb-interview-questions
Facilitates the third step of a proven customer-interview method: translating hypotheses into open-ended, unbiased interview questions — each a miniature experiment designed to test one hypothesis without leading the witness. Two modes: given a single hypothesis, it grills the question into shape and outputs the final question in chat; given a HYPOTHESES.md file, it iterates the whole list, grouping related hypotheses, and maintains a QUESTIONS.md file (numbered Q1, Q2, … mapped to H-numbers) as a live, resumable artifact. Load when the user has hypotheses and wants interview questions, asks how to phrase a question for customers without biasing the answer, or says 'turn my hypotheses into questions' or 'help me ask about X without leading.' Do NOT load for writing goal questions or hypotheses (earlier steps), for conducting or analyzing the interviews themselves, for survey/questionnaire design, or for job interviews.
asb-carol-strengths
Facilitates the second step of a proven ideal-customer (ICP) method: distilling raw company observations into the few deep-truth attributes that matter, then classifying each as a strength, a weakness, or deliberately both. Takes an observations list (O1, O2, … — file or pasted), proposes attributes one at a time with their supporting observations, kills generic ones with the Opposite Test ('we love our customers' dies), classifies each with a concrete rubric (a third of the market sees it that way, or some customers buy/refuse for it alone), and records the result in STRENGTHS-WEAKNESSES.md (S1, S2, … / W1, W2, …). Load when the user has raw observations and wants to distill them, asks 'what are our real strengths and weaknesses,' or wants to classify what they learned from the honest-look exercise. Do NOT load to gather the raw observations (the previous step), to derive keystones or deal-breakers from classified attributes (later steps), or for a person's individual strengths and weaknesses.
asb-interview-hypotheses
Facilitates the second step of a proven customer-interview method: recording the user's current best guesses — hypotheses — as numbered, falsifiable statements (H1, H2, …), each mapped to the goal questions it addresses, so interviews can confirm or contradict them instead of confirmation bias quietly filtering what's heard. Takes a GOALS.md goal-question list as input (file or pasted), elicits what the user believes goal by goal, sharpens vague beliefs into testable claims, prunes to hypotheses whose resolution would actually change what the user builds, targets, charges, or says, and preserves the result in HYPOTHESES.md. Load when the user has goal questions and wants to write hypotheses, list their assumptions, or record predictions before interviewing customers — 'I have my goals, what's next,' 'help me write down what I believe about my customers.' Do NOT load for writing the interview questions themselves, for analyzing interviews already conducted, or for statistical hypothesis testing.
memo
IRAC-scaffolded case analysis memo with research gaps flagged — the scaffold, not the analysis. Rule blocks are RESEARCH NEEDED, Application is STUDENT ANALYSIS prompts, Conclusion is blank. Use when a student needs to scaffold a case analysis memo, write up their analysis, or build an IRAC memo for a case.
recipe-search-and-export-emails
Find Gmail messages matching a query and export them for review.
databricks-serverless-migration
Migrate Databricks workloads from classic compute to serverless compute. Use when migrating notebooks, jobs, pipelines, or Scala JARs (`spark_jar_task`) from classic clusters to serverless, checking if existing code is serverless-compatible, or writing new serverless-compatible code. Provides concrete fixes for the serverless Spark Connect architecture and guides the full migration. Not for classic DBR version upgrades or cluster configuration changes within classic compute.
tab-navigation
Tabs swap views under a shared context. Use when designing tabbed layouts, settings pages, detail views or dashboards with several data views.
blue-ocean-strategy
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant. Use when reframing competitive strategy, escaping commoditization, designing a new category, or applying Strategy Canvas, ERRC, Six Paths, Three Tiers of Noncustomers, Buyer Utility Map, or Strategic Sequence. Includes selection-bias caveats and inline decline notes for iconic cases that later collapsed.
tool-note-and-vote
Structured group-decision mechanic that captures silent ideation, voting summaries, and Decider sign-off in a single bundled artifact. Use when a small team needs to make a fast decision with diverse input, when groupthink is a risk, or when a workshop moment demands silent contribution before discussion. Applicable to Foundation Sprint, Design Sprint, and any participatory decision context.
hig-components-status
Apple HIG guidance for status and progress UI components including progress indicators, status bars, and activity rings. Use this skill when asked about: "progress indicator", "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. Cross-references: hig-components-system for widgets and complications, hig-inputs for gesture-driven progress controls, hig-technologies for HealthKit and activity ring data integration.
mold
Turn a high-leverage design decision into a validated spec through grounded dialogue. Use it when a leverage trigger fires (auth, irreversible effects, concurrency, contracts, destructive ops, a new slice, a cross-slice dependency, an invariant gap) or when the user asks for a spec or design. Typical phrases include "let's design X", "shape this into a spec", "what should the API for Z look like", and "/mold". A feature ask with zero fired triggers is a `/cook` mini-spec, not a mold; route it through `/cheese`. Do NOT use it for free-form discussion without artifact intent (`/culture`), direct implementation (`/cook`), or research-only questions (`/briesearch`). Ceremony scales to the ask through `references/tiers.md`, so a small clear change gets a validated mini-spec without a write-approval turn.
cure
Apply selected fixes from an /age report, findings list, or CI failure. Run the project gates and hand a clean result to /plate. Use when the user wants selected findings resolved. Do not use for review, test authoring, or direct publication.
threejs-perf
Three.js performance optimization patterns for draw calls, scene traversal, and instancing. Use when optimizing 3D scenes with 100+ repeated objects, thousands of moving entities, or draw calls above 500. Loaded by threejs-game, viral-game, and make-game for performance guidance.
macos-settings-ui
Build a proper macOS settings/preferences window with liquid glass support for macOS 26 (Tahoe). Use this skill whenever the user asks to create a settings window, preferences UI, settings view, or preferences pane for a macOS app. Also trigger when the user mentions "liquid glass settings", "NavigationSplitView settings", "grouped Form settings", "macOS settings layout", or wants to add/fix/rebuild a settings screen in any native macOS SwiftUI app. This includes phrases like "add settings to my app", "create a preferences window", "my settings look wrong", "fix my settings UI", or even just "I need a settings view". If the user is building a macOS app and mentions settings or preferences in any context, use this skill.
customware-ai
Use this skill when adding or changing AI chat, text generation, reasoning, tools, model selection, or structured JSON output in a Customware-generated React Router and Hono app. It covers the server-only Customware AI Gateway, AI SDK with the OpenRouter adapter, AI Elements UI, supported model choices, and mandatory live model and structured-output checks.
profile-optimization
Use to optimize a social media profile so it converts visitors into followers and followers into leads — bio, handle, name/headline field, profile picture, banner/header, link-in-bio, CTA, pinned posts, and highlights. Run when the user says "optimize my profile/bio," "write my bio," "my Instagram/LinkedIn/TikTok bio," "profile," "link in bio," "my profile isn't converting," asks about creator mode or a professional/business account, or wants their account to convert better. Reads brand-profile, voice, audience, and social-strategy first. Treats the profile as a conversion landing page — 3-second clarity, searchable-field keywords, a who/what/why bio with one CTA, a goal-matched link, and specs for the visuals, pinned posts, and highlights. Advisory: produces a ready-to-apply per-platform spec (WoopSocial publishes posts/media; it does not edit profile fields). Judges results via native profile insights, not WoopSocial analytics.
azure-well-architected
Expert guidance for designing, assessing, and optimizing Azure workloads using Azure Well Architected. Covers design review checklists, recommendations, design principles, tradeoffs, service guides, workload patterns, and assessment questions. Use when designing AI, HPC, SaaS, AVD/AVS workloads, choosing regions/AZs, or configuring core Azure services, and other Azure Well Architected related development tasks.
cheese
Route an idea, path, pull request, issue, failure, question, or bare `/cheese` to the correct workflow skill. Use this skill for `/cheese`, routing requests, help requests, or opening messages without a named workflow skill.
ultracook
Retired — /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.
pipefy-observability
Use this skill when the user wants to check AI agent logs, automation execution logs, org-level usage stats, AI credit consumption, or export automation job history.
get-shit-done
Structured spec-driven workflow for planning and executing software projects with Claude Code.
sap-hana-ml
SAP HANA Machine Learning Python Client (hana-ml) development skill. Use when: Building ML solutions with SAP HANA's in-database machine learning using Python hana-ml library for PAL/APL algorithms, DataFrame operations, AutoML, model persistence, and visualization. Keywords: hana-ml, SAP HANA, machine learning, PAL, APL, predictive analytics, HANA DataFrame, ConnectionContext, classification, regression, clustering, time series, ARIMA, gradient boosting, AutoML, SHAP, model storage
tool-foundation-sprint-brief
Pre-sprint brief that locks scope, the decision the sprint must unlock, team and role assignments, logistics, inputs to bring, and success criteria before Day 1 of a Foundation Sprint. Use after the readiness verdict is Go and before the sprint begins. Produces a one-page artifact the team and Decider sign off on as the contract for the next two days.
tool-foundation-sprint-founding-hypothesis
Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical template; paraphrase is not accepted in v0.1.0. The Founding Hypothesis is the spine artifact the sprint exists to produce.
hig-components-search
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 content navigation, or file path hierarchy display. Cross-references: hig-components-menus, hig-components-controls, hig-components-dialogs, hig-patterns.
pipefy-automations
Use this skill when the user wants to create, read, update, or delete traditional automations (if/then rules) or AI automations (prompt-driven). For AI agents (conversational), see `pipefy-ai-agents`.
risk-management
Portfolio-level risk controls, drawdown management, exposure limits, and circuit breakers for crypto trading
dbos-typescript
DBOS TypeScript SDK for building reliable, fault-tolerant applications with durable workflows. Use this skill when writing TypeScript code with DBOS, creating workflows and steps, using queues, using DBOSClient from external applications, or building applications that need to be resilient to failures.