3.4K skills · sorted by relevance
Automate Conversion Tools operations using Rube MCP, a connection for agent tools. Find actions that match a task, check their input requirements and connection status, and execute them through Composio.
Finalize a prepared release by dating and versioning its changelog section, updating configured version files with bumpversion, and creating a release commit and tag. Verify the results and leave them ready to push.
Automate Conversion Tools operations using Rube MCP, a connection for agent tools. Find actions that match a task, check their input requirements and connection status, and execute them through Composio.
Add, extend, or review OpenAI Ads conversion tracking for purchases, signups, and other confirmed outcomes. The skill covers browser Pixel events, server-side Conversions API events, duplicate-event prevention, secret handling, and local verification with a setup report.
Delegate release work to a subagent that runs the claude-mem skills version-bump and childhood in order. Use it to coordinate those two stages as a single automated task.
Check Remotion’s current version in its source file and review documentation references for the upcoming release. The skill establishes that the next release is a patch version, helping guide version references in the docs.
Full-funnel paid advertising operations for B2B SaaS. Use this skill for PPC strategy, Google Ads optimization, LinkedIn Ads, social media advertising, programmatic buying, creative strategy, creative concept diversity for Meta Advantage+ (why six variants of one ad are not a diverse library, and what to brief instead), creator-made ad creative on a spend-share deal, attribution modeling, budget allocation, budget pacing and planned-vs-delivered reconciliation, audience overlap and campaign self-competition audits, suppression lists, ROAS improvement, media spend optimization, and the media no auction sells — newsletter and podcast sponsorships, community and industry-publication placements, paid review-site listings on G2 and Capterra, and pay-per-lead content syndication. It also covers buying on the AI answer surface — ads inside Google AI Overviews and AI Mode that existing Search, Shopping and Performance Max campaigns already serve into with no opt-out, no placement targeting and no segmented reporting, and ChatGPT Ads and Microsoft Copilot as separate opt-in platforms with their own plan-tier reach limits, no negative keywords, and a landing-page crawler gate. It also owns the conversion signal the bidding algorithms learn from — CRM pipeline stages (SQL, opportunity, closed-won) sent back to Google Ads, LinkedIn, Meta and Microsoft Ads through offline conversion import, enhanced conversions for leads, the Google Data Manager API and the LinkedIn Conversions API, with click-ID capture, stage values, dedupe, EEA consent signals and retractions. It also gates connected TV (CTV) and streaming video for B2B — whether a reach medium belongs in the plan, how a vendor ties a TV household to a target account (member data, IP-to-account graph or contextual), the server-side ad insertion (SSAI) fraud questions, Programmatic Guaranteed deals, and a holdout lift test because CTV has no click. It also runs person-led paid social — LinkedIn Thought Leader Ads and Meta partnership ads that put spend behind an employee's or creator's post — on a paid-usage term, an in-post disclosure check and an end-date register, because the platform approval carries no term. Also triggers on: CTV, connected TV, OTT, streaming TV ads, should we run CTV, LinkedIn CTV, B2B CTV, account-based CTV, SSAI fraud, thought leader ads, boost an employee's post, sponsor a creator's post, partnership ads, whitelisting, creator usage rights, PPC, Google Ads, LinkedIn Ads, social ads, programmatic, ad creative, attribution, media budget, paid campaigns, ROAS, CPA, ad spend, newsletter sponsorship, podcast sponsorship, community sponsorship, sponsor a newsletter, content syndication, pay-per-lead, cost per lead vendor, media kit, rate card, insertion order, direct buy, publisher partnership, make-good, G2 paid listing, Capterra ads, review site advertising, sponsorship ROI, budget pacing, we underspent our budget, are our campaigns competing with each other, audience overlap, self-competition, campaign cannibalization, suppression list, exclusion list, ad frequency across channels, how many ad accounts do we have, ads in AI Overviews, AI Mode ads, ChatGPT Ads, OpenAI Ads Manager, Copilot ads, conversational ads, should we advertise on ChatGPT, can we buy our way into the AI answer, our ads are showing in AI Overviews and we cannot report on it, context hints, OAI-AdsBot, our ad landing page fails review, robots.txt is blocking our ads, our paid leads are junk, Google Ads is optimizing for the wrong leads, offline conversion import, OCI, enhanced conversions for leads, send CRM stages back to Google Ads, upload SQLs to LinkedIn, LinkedIn Conversions API, LinkedIn CAPI, Meta conversion leads, CRM to ad platform, gclid, li_fat_id, msclkid, value-based bidding, optimize for pipeline not form fills, low match rate, conversion lag.
The English summary is being prepared. Showing the original description.
Coordinate a Claude Code plugin release by updating version numbers across manifests, checking the build, creating a Git tag and GitHub release, and regenerating the changelog. The workflow also publishes to npm and verifies the published version.
Prepare an AionUi release by checking AionCore assets, updating versions, and generating a changelog. Run quality checks, create a pull request with automatic merging enabled, then tag the merged release to trigger its build.
Diagnose declines in Google Ads conversions, conversion value, and leads by comparing periods, traffic, device breakdowns, impression share, and account changes. Use live account data through the Google Ads MCP Server or receive queries and diagnostic guidance for manual execution.
Audit how advertising platforms, GA4, and app measurement tools assign credit for conversions. Compare event definitions, reporting windows, and duplicate handling to explain discrepancies and produce an evidence-based measurement improvement plan.
Configuring Salesforce lead management and conversion in Setup: lead settings, web-to-lead, conversion field mapping, lead queues, auto-response rules, lead processes. Trigger keywords: web-to-lead, lead conversion, lead field mapping, lead settings, lead process, lead queue, lead auto-response. NOT for Apex that controls what conversion creates - use apex/lead-conversion-customization. NOT for lead assignment rule logic - use admin/assignment-rules. NOT for duplicate rule configuration - use admin/duplicate-management. Also covers: LeadConvertSettings objectMapping XML, LeadConfigSettings, LeadStatus StandardValueSet converted flag, lead process BusinessProcess, Database.convertLead bulk conversion limits.
The English summary is being prepared. Showing the original description.
Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without bumping the version", or anything involving the version history. Calls out today's limitations honestly: there is no pointer flip; "rollback" means forking the old query into a new top version.
The English summary is being prepared. Showing the original description.
Cut a release of the Lyrion Dashboard. Use this whenever a task is about shipping a new version — bumping the version, tagging, the Release workflow, or how the Android APK and the Docker image get built and published. Covers the single source of truth for the version, the manual `Release` → publish → `android.yml` + `docker.yml` chain, the versionCode packing, and the F-Droid constraint that keeps versions static in source. Reach for it before touching `VERSION`, `release.yml`, or the Android `versionName`/`versionCode`.
The English summary is being prepared. Showing the original description.
Documents minimum SDK/OS version requirements for all OneKey platforms. Use when checking platform compatibility, understanding deployment targets, verifying version requirements, or when user asks if their device can run the project. Triggers on minimum version, SDK version, API level, deployment target, platform requirements, iOS version, Android version, Chrome version, Electron version, can I run, environment check, device compatibility, check environment.
The English summary is being prepared. Showing the original description.
Update Mediabunny and its related packages throughout Remotion, including templates, CLI version references, and the documentation compatibility table. The workflow checks the latest published version, aligns the relevant entries, and finishes by installing dependencies with Bun.
Prepare the next Prisma 8 release by updating workspace versions, assembling upgrade guides, and drafting release notes. Open release and documentation pull requests for maintainer review; merging the release request triggers automated publication.
Choose a game engine and version, record the choice in project configuration, and prepare reference documents for newer releases. The skill also supports refreshing those references and guiding migration between engine versions.
Compare the installed Claude Code version with release notes and recent bug reports to decide whether to stay, update, or use a specific version. Recommendations account for reported problems, relevant fixes, and how Claude Code was installed.
Audit Snapchat Ads measurement, mobile and app campaigns, creative, AR and catalog formats, audiences, and budgets. Produce prioritized recommendations with supporting evidence, missing inputs, and brand safety concerns clearly identified.
Verify Claude Agent SDK build and release scripts without network access. Run command-line workflows in an isolated environment with substitute commands to check version validation, installer handling, and retries without overwriting the developer’s installed Claude binary.
Build in-game changelogs that connect release notes and displayed versions to successful production deployments. Reconstruct supported history, integrate menu navigation and accessible controls, and verify version consistency and behavior on desktop and mobile.
Enhancement overlay — version the WHOLE deployable LLM-app artifact as one bundle: prompts + compiled programs + model snapshot pins + retrieval config + eval-set version, versioned together so a deploy is reproducible and rollback is atomic. Activate when preparing to deploy an LLM app, when asking "what exactly is running in prod right now?", when a deploy must be reproducible months later, or when an incident needs a clean rollback. The core reframe: an LLM app artifact is NOT an ML model — it is a manifest over many independently-mutable parts, not one weights file. Do NOT activate for one-off prompt edits with no deploy, for a single-component demo, or where a vendor owns the whole prompt lifecycle. For versioning ONE compiled prompt use [[agentsop-per-model-artifacts]]; for the CI comparison mechanism use [[agentsop-regression-gate]]. Search keywords: prompt versioning, reproducible deploy, what is running in prod, rollback LLM app, model pinning, prompt registry, version prompts and config.
The English summary is being prepared. Showing the original description.
Fix "backend exists on a draft version but isn't reachable from the new Compute deploy" bugs after `fastly compute publish`. Use when: (1) You ran `fastly service backend create --autoclone` (or any dashboard/CLI change that creates a draft version) but did not activate that draft, (2) You then ran `fastly compute publish` which appeared successful but your backend / ACL / header / dictionary change is missing from the active version, (3) Compute code returns backend-not-found errors or misroutes requests, (4) You're surprised to see your draft version number "skipped over" in the version chain. Root cause: `fastly compute publish` clones from the currently-active version, not from the latest draft, so dashboard changes made in an un-activated draft get stranded.
The English summary is being prepared. Showing the original description.