Coding & Development

Create and incrementally update exam-focused Anki decks from a university course folder with lecture slides, exercises, solutions, and old exams. Supports mathematics/CS question types, stable note IDs, diagrams, and .apkg packages.

Add a gentle automatic fade-in and upward entrance to selected PowerPoint content, staggered by position while keeping titles fixed. Use for sequential reveal or subtle motion. フェードイン、下からの入場、順次表示アニメーションに使用。

Split or package an existing static HTML/CSS/JS prototype into reusable pages or components while preserving its visuals and interactions. Use for structural delivery work; use prototype-maintenance for ongoing module ownership and iteration.

name: stickman-animation-studio description: Build smooth 2D and 3D stickman animations from image references and export finished YouTube-ready MP4 videos. Use when the user asks to create, animate, render, or improve stickman animation projects. Stickman Animation Studio — 2D & 3D MP4 Purpose Create complete, editable stickman animation projects that can be rendered as MP4 videos for YouTube. Sup

Use for ALL vulnerability data analysis, NVD exploration, CVE lookups, CVSS/CWE/CPE inspection, severity distributions, temporal trends, and database building/updating. Triggers on: vulnerability questions, CVE queries, NVD data analysis, CVSS scores, severity breakdowns, CWE/CPE lookups, building/refreshing the NVD cache, EPSS exploitation probability, KEV active exploitation, zero-day analysis, CVD coordination state, vendor vulnerability trends, remediation metrics, any question about the vulnflow library or its data. ALWAYS use when the user names a specific CVE ID (e.g. "tell me about CVE-2021-44228"): answer from the local data, not from memory.

End-to-end third-party packaging for cppget.org (new package, new upstream version, or packaging revision). Use when the user wants to package a third-party C/C++ library or executable for build2, convert CMake/Meson to a cppget.org submission, publish to cppget.org, or runs /build2-package or /build2 package. Do not use for ordinary b/bpkg/bdep project work. Do not use for reviewing someone else's cppget.org submission (that is build2-review).

Maintain an existing interactive prototype by clarifying ownership of pages, components, dialogs, data, state, styles, and validation. Use for ongoing structural iteration and maintenance maps, rather than first-time static delivery packaging.

Generate images, icons, and visual assets locally on Intel hardware.

Load when connecting a client's or your own phone number to the WhatsApp Business Platform (Cloud API) inside Meta Business, or when a connected number "is green but nothing arrives", messages arrive twice, templates fail, or Meta blocks a step. Gives the safe order (portfolio → WhatsApp account → number → app → token → webhook → register with PIN → test), the read-back checks after each step, and a troubleshooting table of real blocks with their official error codes and fixes, each marked as official or field-tested. Triggers on "connect WhatsApp to my app", "onboard client number", "WhatsApp Cloud API setup", "number already registered", "No se pudo asignar el socio", "display name in review", "131042", "133010", "133016", "messages not arriving", "conectar el WhatsApp del cliente", "dar de alta el número", "el bot no recibe mensajes", "Meta no me deja". Not an API reference for sending messages or templates (use a WhatsApp Cloud API reference skill) and not sales copy for the bot (use whatsapp-closer).

Map an app's navigation as a screen flow built from real screenshots, delivered as one standalone HTML file with an infinite, zoomable canvas. Screens are placed as cards with arrows between them, the main navigation is grouped together, and each feature's screens get their own group. Works for one feature or the whole app, on web, iOS, Android or desktop. Use when the user asks for a screen flow, user flow, navigation map, flow diagram, sitemap with screenshots, "map all screens", "how do you get to X", or wants to document or review an app's or feature's navigation visually.

Analyzes NSE/BSE-listed Indian stocks via web search — current news, upcoming government schemes (PLI, budget allocations), company projects/capex, and BSE/NSE corporate announcements — then scores and ranks stocks, recommends entry/exit timing (intraday) or ideal holding period (long-term), and picks the best stock(s) for a given budget. Use this whenever the user asks about Indian stocks, NSE or BSE tickers, "should I buy X", comparing multiple Indian stocks against a budget, Indian stock entry/exit timing, or mentions trading/investing in Indian equities — even if they don't explicitly ask for a "report" or "analysis". Always trigger for requests naming Indian stock tickers or companies alongside words like buy, invest, budget, compare, entry, exit, or hold.

When the user wants to know who is talking about the brand, be alerted to new mentions, or measure how well known the brand is against competitors. Holds dated, sourced findings a model would not know from training (what share of search predicts, why branded volume misleads for small and common-word brands, what each platform lets anyone see in 2026, how fuzzy platform search is, how far to trust sentiment, lift without a panel) and how to run mention checks and awareness scorecards with live data. Also use when the user mentions alert me when someone mentions us, monitor Reddit for our brand, social listening, brand monitoring, mention alerts, track mentions every day, who talked about us this week, a brand awareness plan, nobody knows who we are, share of voice against competitors, share of search, grow branded search, brand lift, get our name out there, or getting the brand known. AI answers alone go to ai-search, rivals' moves to competitor-intel, client reporting to agency.

Use when the user asks for a multiple-choice quiz or practice questions from slides or notes, as a clickable page with green/red answers, review mode, retry of mistakes and PDF export; can include structured and program-analysis questions.

When the user wants more installs from Apple's App Store or Google Play search, or research on apps in a category. Holds dated, sourced findings a model lacks (what each store indexes, App Store tags, custom product pages in search, AI review summaries, more Apple Ads slots since March 2026, conversion benchmarks, rating prompt rules, why store volumes are models) and how to read the store data. Also use when the user mentions ASO, app store optimization, App Store keywords, the keyword field, app title or subtitle, Play Store description, app screenshots or icon tests, product page optimization, store listing experiments, competitor apps, app reviews, replying to reviews, raising an app rating, top charts, Apple Search Ads and organic, apps in ChatGPT, finding app developers to contact, or an ASO plan. Web search goes to seo, AI answers in general to ai-search, rivals beyond the store to competitor-intel, review themes to voice-of-customer, ad budgets to paid-ads.

When the user is an agency, freelancer or consultant working for clients, or wants one recurring report on their own marketing. Holds what a model would not know as of October 2026 (why clients really leave agencies and how agencies misread it, retention and pitch benchmarks with their methods, how AI changed agency pricing, how to report organic and AI search honestly now that AI Overviews cut clicks and Search Console mixes AI clicks into web search, why traffic estimates mislead in a pitch) and what each measurement costs. Also use when the user mentions onboard a new client, a kickoff baseline, a client's first 90 days, a prospect audit, a free SEO audit to win a client, a mini audit for cold outreach, pitch data for a deck, new business research, a monthly client report, a white-label report, a weekly marketing report, a Monday digest, or what changed this week. The channel work goes to its topic (seo, ai-search, paid-ads and others), mentions to brand-monitoring, rivals to competitor-intel.

Port a Minecraft Java mod (any version, jar or source) to the b1.7.3_rewrite mod loader as one .b173mod that runs on client and server, extending the loader and SDK where the mod needs something new. Use when the user says /modport, /port, "port this mod", or hands over a mod jar to bring to beta 1.7.3.

Use for large software engineering work that needs dependency-aware planning and coordinated subagents: implementing a PRD or roadmap, multi-module features, substantial refactors or migrations, or resuming a plan saved under .dag/. Investigates the relevant code, decomposes the work into independently verifiable DAG tasks, runs independent tasks in parallel in isolated git worktrees, and continuously integrates and verifies the results. Also use when only a plan of this scope is requested. Do not use for small or self-contained changes (quick fixes, routine or single-file edits, anything a few tool calls can finish) or non-code tasks.

把老旧 CentOS 7 / CentOS 8（及 RHEL7/8 系）服务器原地升级到最新 AlmaLinux 10（经 ELevate/Leapp 7→8→9→10，CentOS 8 先用 almalinux-deploy 转换），并保证业务、容器、nginx、kubectl 等升级后照常工作。凡是用户提到 CentOS 7 / CentOS 停服 / EOL / 老系统升级 / 迁移到 AlmaLinux / Rocky / CentOS 继任者 / ELevate / leapp / 系统漏洞要升级系统、批量升级阿里云/华为云/AWS 上的 CentOS 服务器，都要使用本技能——即使用户没说"升级"而只说"系统太老了""换个新系统但业务不能停"。In-place upgrade CentOS 7 to AlmaLinux 10 safely, single server or whole fleet.

Profile and optimize Rust runtime performance with reproducible benchmarks. Use whenever someone wants Rust code faster or leaner (slow functions, latency or throughput regressions, allocation churn, CPU hot spots, async stalls), even if nothing has been measured yet. The skill measures first and rejects changes without evidence.

Make a repository's GitHub Actions CI faster and cheaper. Measures a baseline from recent runs with the gh CLI, finds the critical path and wasted runner minutes, matches them to the BerryBox Playbooks, asks which fixes to apply, then applies them one commit per play on a new branch and compares the pull request's runs with the baseline. Use when the user asks to speed up CI, cut GitHub Actions minutes or cost, reduce queue time, fix slow or flaky workflows, or review .github/workflows for performance.

Generate a self-contained guided review JSON artifact from a GitHub pull request URL, with ordered explanations referencing the real diff. Use for a PR walkthrough artifact, not for posting a GitHub review.

Plan a change before any code is written. Sizes the work, asks only the questions the code can't answer, and writes one code-grounded plan (decisions, change map, tasks or stories) under .specshape/, revising it until the user approves. Never writes code. Use when the user wants to plan a ticket, spec, feature or new project, plan one story of an existing plan, or revise a plan.

Use for code reviews, security or reliability audits, and production readiness checks, and before designing or changing authentication, data models, payments, external integrations, background jobs, caching, or deployment. Contains a 150-item checklist covering security, data, concurrency, resilience, messaging, networking, caching, performance, APIs, observability, testing, delivery, disaster recovery, client side, and LLM features.

Publish and share static artifacts (HTML sites, Markdown and plain text) with Portifact, control who can see them and collect reviewer annotations. Use when the user wants to share a plan, report, prototype or document as a link, or mentions Portifact, the portifact CLI or the Portifact MCP server.