Loading...
Loading...
Found 3,347 Skills
Control Home Assistant smart home devices through AI assistants using the Model Context Protocol
Catch-all for anything CawCut-App related via the local `cawcut` CLI: running published Apps, and open-ended requests like "what can <app> do", "what does <app> generate", "what apps are there", "list official apps", browsing/listing available Apps, or checking an App's inputs/outputs. Use when: "/cawcut-app-run", "run my CawCut app", "invoke published app", "list available CawCut apps", "what apps are available", or the user describes a workflow/template-style creative request (ads, campaigns, multi-step templates) that may match a published app. Fetches the live App catalog and scores intent before routing; hands off simple one-step text-to-image/video or image-to-image/video generation with no App match to cawcut-generate, which will hand back here if it later finds a matching App. Requires `cawcut` installed and authenticated. NOT for: OAuth consent alone, or Apps the user cannot access. When unsure whether a request needs an App or raw generation, start here — this skill decides and delegates.
Multi-agent protocol for proving or refuting mathematical statements. Use when trying to prove a mathematical statement with agents, when a claimed lemma keeps dying under scrutiny, or when the true statement itself is still unknown (theory-finding regime).
You MUST use this when writing or editing prose anywhere in a project (docs, READMEs, comments, commit messages, UI copy) and when asked to audit, score, or clean up dash usage. It bans typographic dashes (em and en) in favor of the plain hyphen and grades a project's compliance on a 0-100 scale.
Security report over a window — merged PRs since a date or PR number (default last 7 days), or one branch or spec. Runs `om-auto-sec-report-pr` per unit, aggregates severity-ranked findings, a risk heatmap, and one "go deeper" list into one redacted report, kept local by default or shipped as a docs-only PR. Use for "weekly security report", "security review of everything merged since X".
Find files for unfamiliar repository behavior and regression tests before coding.
Gets Claude talking to a tool nobody built an official connector for. Works out what the system is, checks the Claude connector directory for an existing connector first, and when there isn't one connects the tool through Zapier — never by hand-building against a raw API — with credentials handled safely and approval gates on anything that writes. This is what turns "my ERP isn't supported" into an afternoon. Use this whenever the owner names a tool that isn't connected — including phrasings like "can you connect to my," "make my tools talk to each other," "there's no API for this," "pull data out of my field service software," "I use ServiceTrade and it's not on the list," or "is there any way to get at this data." Reach for it whenever an unsupported system is blocking something else.
Read-only router for "which skill should I use?", "what do I do next?", "how do I do X here?". Builds the answer at run time from the repo's AGENTS.md Task Router, the skills actually installed, optional repo workflow data, and knowledge sources — then recommends and hands back control. Never runs the pipeline itself.
Finds the outlier reels of Instagram accounts or videos of TikTok accounts (3x their own account's median views or more) through Treg and turns the 5 best into remake scripts in the creator's voice. Two modes - /outliers @handle digs one account; /outliers with no account starts from the creator's own reels, uses and grows a competitor watchlist (video-agent/competitors.json, 70 % main language / 30 % second language when they watch two), ranks every account's outliers against its own median and writes 5 scripts into video-agent/scripts/. Use when the user says outliers, find outliers, what blew up for my competitors, what works in my niche, find me videos to remake, ideas from @someone, what blew up on TikTok.
Query available AI models across all configured providers. List models, resolve model aliases, and browse the full model catalog including provider-specific variants.
Use at the START of any bug bounty hunting session, when switching targets, or when feeling lost about what to do next. Master orchestrator that combines the 5-phase non-linear hunting workflow with the critical thinking framework (developer psychology, anomaly detection, What-If experiments). Routes to all other skills based on current hunting phase. Also use when asking "what should I do next" or "where am I in the process."
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.