symmetric-cipher-attacks SignedBy yaklang · original, unchanged Symmetric cipher attack playbook. Use when exploiting block cipher mode weaknesses (CBC padding oracle, ECB cut-and-paste, bit flipping), stream cipher key reuse, or meet-in-the-middle attacks. MIT View symmetric-cipher-attacks talking-head-and-piece-to-camera SignedBy social-media-skills · original, unchanged The on-camera delivery craft — helping a real human film themselves talking to a lens and look like themselves doing it. Use when someone wants a "talking head video" or "piece to camera," says "film myself" or "I look stiff on camera," asks about a teleprompter, framing, lighting, audio, or retakes, or wants to batch-film videos. Uses the TAKES framework. Phone-first: gear is almost never the bottleneck. Reads brand-profile + voice-builder first; takes its script from short-form-video-script (that writes it, this delivers it). The agent coaches setup + delivery, formats prompter/beat-map scripts, and plans batch days; the HUMAN films and picks the take (the agent cannot see footage); WoopSocial publishes the finished file. Camera-shy? Route honestly to heygen/synthesia or faceless formats. Never fabricates "that take looks great." Distinct from scripting-and-storyboarding (the shoot plan), heygen/synthesia (avatars), and captions-and-clipping/capcut/descript (the edit). MIT View talking-head-and-piece-to-camera tavily-research SignedBy tavily-ai · original, unchanged Conduct comprehensive AI-powered research with citations via the Tavily CLI. Use this skill when the user wants deep research, a detailed report, a comparison, market analysis, literature review, or says "research", "investigate", "analyze in depth", "compare X vs Y", "what does the market look like for", or needs multi-source synthesis with explicit citations. Returns a structured report grounded in web sources. Takes 30-120 seconds. For quick fact-finding, use tavily-search instead.
MIT View tavily-research tech-employer-branding SignedBy samber · original, unchanged Designs an employer-brand strategy for attracting software engineers - the engineering EVP, the channel plan (engineering blog, OSS presence, referrals, conference talks, compensation-transparency artifacts), a verification-surface audit (employer-review sites, compensation databases, anonymous forums), and the measurement baseline. Use whenever someone raises "engineering employer brand", "why can't we attract engineers", "developer hiring content strategy", "should we publish salary bands", "tech recruiting brand", or engineering offer-acceptance dropping - even if they frame it as a recruiting problem. Covers early-stage through big-company stages, junior through staff-level targeting. Not DevRel program strategy - use samber/developer-relations-skills@devrel-strategy. MIT View tech-employer-branding tech-press-relations SignedBy samber · original, unchanged Runs press and light analyst relations for a developer-facing product - news qualification, the angle, a reporter-to-beat media map, the pitch, embargo and exclusive handling, the press page and briefing pack, and what coverage is honestly worth. Use whenever someone raises tech press relations, getting press coverage, pitching a journalist, a tech media pitch, building a media list, a press kit, an embargo briefing, announcing a funding round, a launch coverage plan, an analyst briefing, or "how do we get written about" - even if they only say they want to be in the news. Nothing to do with pull requests. Not the announcement post itself - use samber/developer-relations-skills@engineering-blog-post. MIT View tech-press-relations test-automator SignedBy zhaono1 · original, unchanged Test automation framework expert for creating and maintaining automated tests. Use when user asks to write tests, automate testing, or improve test coverage. MIT View test-automator threads-growth SignedBy social-media-skills · original, unchanged The Threads account-growth strategy skill -- the channel layer above threads-post. Use when someone wants to grow a Threads account, understand the Threads algorithm, fix reach, plan cadence, or set a Threads strategy. Threads is conversation-first, and the #1 growth lever is Mosseri's "reply more than you post": replies are weighted heaviest and first-hour engagement velocity is the top ranking factor. Uses the TALKS framework. Reads brand-profile + goals-and-kpis first. The agent strategizes the channel + drafts original posts (published via WoopSocial) and suggested replies; BUT the reply flywheel is human/community-management (no reply surface in WoopSocial), and Communities/DMs/dashboards/analytics are native. No engagement-bait, original not recycled, positive tone, metrics never fabricated, growth compounds over 60-90 days. Distinct from threads-post (the single-post craft) and community-management (the reply execution); uses Threads as a discovery funnel into instagram-growth. MIT View threads-growth threads-post SignedBy social-media-skills · original, unchanged Write and publish single posts on Meta's Threads — the Threads format-execution skill. Use when someone wants a "Threads post," to "post to Threads," grow on Meta's Threads, or publish a Threads post via WoopSocial. Writes a Threads-native conversation post (text <=500 + optional media) built to earn replies — Threads is conversation-first: replies outweigh likes and engagement velocity drives distribution. Uses the REPLY framework. Reads brand-profile + goals-and-kpis first. WoopSocial publishes ONE Threads post (no native multi-post chain, no polls/voice/GIF, no reply surface); the replying that drives reach is a human/community-management job; metrics never fabricated; no engagement bait. Distinct from thread-writer (a user saying "write a thread" wants that multi-post X chain, not this), x-growth (sibling text platform, different culture) and caption-writer (text only). MIT View threads-post thread-writer SignedBy social-media-skills · original, unchanged Use to write a thread — a connected sequence of posts on X/Twitter or Threads that tells one story or makes one argument across multiple posts. Run when the user says "write a thread," "turn this into a thread," "X thread," "Twitter thread," "thread about X," or has a multi-beat idea that won't fit one post. Reads brand-profile and voice first, uses hook-writer for the opening post (which must hook AND promise the payoff), builds one cohesive idea where every post earns the next, and lands a close with one CTA. Knows when a single post beats a thread. Naming trap: "write a thread" means this multi-post chain; "post on/to Threads" means a single post on Meta's Threads app — use threads-post for that. For a single caption use caption-writer; for just the opening hook use hook-writer. MIT View thread-writer threat-hunting SignedBy zhaoxuya520 · original, unchanged Use for blue-team threat hunting, detection engineering with Sigma/YARA, SIEM query design, and incident detection validation. MIT View threat-hunting threat-intelligence SignedBy zhaoxuya520 · original, unchanged Use for authorized OSINT and cyber threat intelligence that enriches IOCs, campaigns, impersonation, scams, or threat actors from public sources. Includes bounded X/Twitter search through Xquik, source preservation, corroboration, and evidence handoff. MIT View threat-intelligence thumbnail-design SignedBy social-media-skills · original, unchanged 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). MIT View thumbnail-design tigris-sdk-guide SignedBy tigrisdata · original, unchanged Use when choosing between Tigris-native SDKs and AWS S3-compatible SDKs — covers which SDK to use per language, CLI preference, and when AWS SDKs are the only option MIT View tigris-sdk-guide tigris-security-access-control SignedBy tigrisdata · original, unchanged Use when configuring CORS, rotating access keys, setting bucket policies, or securing Tigris storage — covers key lifecycle, roles, CORS rules, presigned URL security, audit checklist MIT View tigris-security-access-control tiktok-photo-mode SignedBy social-media-skills · original, unchanged The TikTok Photo Mode format-execution skill. Use when someone wants a "TikTok photo carousel," "photo mode," "TikTok slideshow," "swipeable TikTok post," or to publish a multi-image TikTok post via WoopSocial (postType PHOTO). Builds a TikTok-native carousel that wins on completion rate — hook slide 1, progressive reveal with cliffhangers, reward + one CTA — AND sets the exact WoopSocial PHOTO publish config (privacy, comments, music, truthful disclosure flags). Uses the SWIPE framework. Reads brand-profile + goals-and-kpis first. The agent writes the slide plan + overlay copy + caption + config; the IMAGES are made by a human/image skill, not WoopSocial; WoopSocial publishes the native PHOTO post; metrics never fabricated and photo mode is never promised as a reach hack. Distinct from tiktok-script (VIDEO) and carousel-writer (cross-platform copy). MIT View tiktok-photo-mode trace-to-training-data SignedBy wshobson · original, unchanged Convert evaluation traces and production logs into SFT examples and preference pairs. Use when graded traces or failure examples exist and need to become training data, when applying rejection sampling to model outputs, or when building DPO pairs from passing and failing runs. MIT View trace-to-training-data translate-pdf SignedBy wshuyi · original, unchanged Translate PDF documents to any language while preserving original structure, layout, and styling (colors, backgrounds, positions).
Use when user wants to: (1) translate a PDF to another language, (2) convert PDF from one language to another, (3) create translated version of PDF document.
Triggers: "translate PDF", "PDF翻译", "把PDF翻译成", "translate this PDF to Chinese/English/Japanese", "翻译成中文/英文"
MIT View translate-pdf trend-jacking SignedBy social-media-skills · original, unchanged Use to ride a trend — a trending sound, format, meme, hashtag, news moment, or cultural conversation — to earn reach by attaching the brand to something already getting attention (a.k.a. trendjacking / newsjacking). Run when the user says "trend," "trending," "jump on this trend," "trendjack," "newsjack," "is this trend worth doing," "make this go viral," or wants to react to a current moment. Reads brand-profile, voice, and audience first, then runs three gates — FIT, SAFETY, and TIMING — before executing a fast, on-brand remix and handing to the right content skill (tiktok-script, reels-script, caption-writer) and scheduling-and-queue. Refuses to trendjack tragedies or divisive moments and won't force irrelevant trends; live trend discovery needs current scanning — this skill vets and executes. For meme-format craft, cultural fluency, and meme IP/likeness judgment ("make a meme," "is this meme safe"), route to meme-and-culture. MIT View trend-jacking trpc-router SignedBy trpc · original, unchanged Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
MIT View trpc-router typesafe-ai SignedBy typesafe-ai · original, unchanged Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives. Its System One models, including Jev, turn natural language and application state into typed judgments and probabilities that code can combine. Use when a feature needs programmable common sense, when brainstorming what AI could make possible in an app, or when an LLM prompt-and-parse step could become a structured decision. Applications include routing, ranking, extraction, verification, and interactive experiences; these are starting points, not the limits. Read live docs and cookbooks to find useful patterns and discover new combinations.
MIT View typesafe-ai tzst SignedBy xixu-me · original, unchanged Use when the user needs to create, extract, flatten, list, test, install, script, or troubleshoot `tzst` CLI workflows for `.tzst` or `.tar.zst` archives, including compression levels, streaming mode, extraction filters, conflict resolution, JSON output, or standalone binary setup, even if they describe the archive task without naming `tzst`. MIT View tzst ux-friction SignedBy dylantarre · original, unchanged Use when animation causes user confusion, delays task completion, or creates frustration MIT View ux-friction venice-api-overview SignedBy veniceai · original, unchanged High-level map of the Venice.ai API - base URL, which auth mode each endpoint accepts (API key, x402 wallet, or none), endpoint categories (including decisions, voice changer, and retired routes), response headers (rate limit, balance, deprecation, x402), pricing model, error shape, and versioning. Load this first when starting any Venice integration. MIT View venice-api-overview venice-audio-transcription SignedBy veniceai · original, unchanged Transcribe audio files to text via POST /audio/transcriptions. Covers supported models (Parakeet, Whisper, Wizper, Scribe, xAI STT), accepted containers (wav/flac/m4a/aac/mp4/mp3/ogg/webm), response formats (json/text only), per-model timestamps (word/segment/char), language hints, the 25 MB cap, and per-audio-second pricing. OpenAI-compatible multipart. MIT View venice-audio-transcription venice-augment SignedBy veniceai · original, unchanged Venice augmentation endpoints for agent pipelines. Covers POST /augment/text-parser (extract text from PDF/EPUB/DOCX/PPTX/XLSX/XLS, plain text and source code; multipart, up to 25MB; JSON or plain-text response), POST /augment/scrape (fetch a URL and return markdown; blocks X/Reddit and private/internal URLs), and POST /augment/search (Brave ZDR or anonymized Google; structured title/url/content/date results, limit up to 20 but effectively capped at 10 Brave / 5 Google). $0.01 per successful call, 20 req/min on scrape and search, privacy, and error shapes. MIT View venice-augment venice-chat SignedBy veniceai · original, unchanged Call POST /chat/completions on Venice. Covers the OpenAI-compatible request shape, Venice-only venice_parameters (web search, scraping, citations, E2EE, characters, thinking control, X search), anon_user_id, multimodal inputs (images/audio/video/files), tool calls, reasoning controls (reasoning_effort, reasoning.enabled), streaming, prompt caching, structured output, per-model caps, and model feature suffixes. MIT View venice-chat venice-embeddings SignedBy veniceai · original, unchanged Call POST /embeddings on Venice. Covers request shape (input, model, encoding_format, dimensions, user), text-only input (token arrays rejected), per-input and batch limits, per-model dimensions/privacy, the text-embedding-ada-002 alias, API-key privacy gating, OpenAI/LangChain compatibility, response compression (gzip/br), and practical usage for retrieval, clustering, and RAG. MIT View venice-embeddings venice-errors SignedBy veniceai · original, unchanged Handle Venice API errors correctly. Covers the error body shapes (StandardError, DetailedError with validation details/issues, OpenAI-style context_length_exceeded, upstream provider rejections with request_id including TypeSafe/FastAPI validation errors, ContentViolationError, ProviderContentPolicyError, PayloadTooLargeError, the two x402 402 bodies), every meaningful status code (400-504, including 410 for retired endpoints), the three families of rate-limit headers, the per-key error budget (FAILED_REQUESTS / UNSUPPORTED_FEATURE_REQUESTS), Retry-After on overloaded models, SSE stream errors, and a backoff strategy that won't trip the error budget. MIT View venice-errors venice-image-generate SignedBy veniceai · original, unchanged Generate images with Venice. Covers POST /image/generate (Venice-native), POST /images/generations (OpenAI-compatible), GET /image/styles (style presets), request fields (prompt, width/height, aspect_ratio, resolution, quality, cfg_scale, steps, seed, variants, style_preset, style_references, enhance_prompt, safe_mode, hide_watermark, format, return_binary), per-model constraints from GET /models, response formats and headers. MIT View venice-image-generate video-to-sfx SignedBy sonilo-ai · original, unchanged Generate sound effects matched to a video using Sonilo — footsteps, impacts, ambience, foley — optionally scripted to specific timed segments, returning either the audio or a new video with the SFX muxed in. Use when the user has footage that needs sound design. For SFX from a text description alone, use the text-to-sfx skill; for music, use video-to-music. MIT View video-to-sfx viral-instagram-reels SignedBy vyralcontent · original, unchanged Plan, write, and diagnose Instagram Reels that earn cold-audience reach. Use whenever someone wants a reels script or reels hook for a specific Reel, is debugging why a Reel flopped, wants to know if a draft is worth testing with Trial Reels before going public, or needs a reels caption tuned for the post-hashtag instagram algorithm. Built around what Mosseri has publicly named as the signal hierarchy (watch time, sends per reach, likes per reach), the Trial Reels test-then-publish loop, the Original Content Guidelines and 30-day recovery window, the Edits app, and Reels Insights metrics (skip rate, share rate, followers from this post). Covers a Reels-specific reels strategy: send-driving CTAs, originality without watermarks, audio licensing by account type, captions as the primary SEO signal, and the anti-patterns that quietly cap distribution. Pattern-based guidance, not a virality promise. MIT View viral-instagram-reels viral-short-form-ideas SignedBy vyralcontent · original, unchanged Generate short-form video ideas at volume and stop the blank-page problem for good. Use whenever someone says they're stuck for ideas, asks for 20 TikTok ideas or Reels ideas or YouTube Shorts ideas for their niche, wants a content brainstorm, needs help building a content pillar system or content matrix, wants to turn one idea into 5 angles, asks what to post this week, or wants a real idea generator workflow instead of staring at a notes app. Runs the systems prolific creators actually use: pillars, mining (comments, Reddit, search autocomplete, competitor outliers), repurposing, evergreen vs trend balance. Pattern-based guidance grounded in how short-form ideation tends to work; never run out of ideas is the goal, virality is not promised. MIT View viral-short-form-ideas viral-youtube-shorts SignedBy vyralcontent · original, unchanged Write and diagnose YouTube Shorts that hold attention on the Shorts Feed and route viewers into your long-form. Use when someone wants a shorts script, a shorts hook tuned for VVSA and the first 3 seconds, a fix for a flopping short, a read on whether to link a short to a long-form video, or a plan to build the shorts to long form funnel for their channel. Covers what the youtube shorts algorithm rewards now that the Shorts feed runs separately from long-form, how shorts retention is measured, and the youtube shorts strategy choices that move RPM (licensed music split, Creator Pool math, Engaged Views). Pattern-based viral shorts guidance grounded in how shorts tend to perform. MIT View viral-youtube-shorts vision-sft SignedBy wshobson · original, unchanged Fine-tune vision-language models (VLMs) with supervised learning on image+text data. Use when adapting a VLM to a visual domain or task, configuring frozen-vision-tower LoRA, or debugging a VLM fine-tune that trains without learning. MIT View vision-sft vm-and-bytecode-reverse SignedBy yaklang · original, unchanged Custom VM and bytecode reverse engineering playbook. Use when CTF challenges or protected software implement custom virtual machines with proprietary bytecode, dispatcher loops, or maze-style challenges. MIT View vm-and-bytecode-reverse vue-application-structure SignedBy aj-geddes · original, unchanged Structure Vue 3 applications using Composition API, component organization, and TypeScript. Use when building scalable Vue applications with proper separation of concerns.
MIT View vue-application-structure web-cache-deception SignedBy yaklang · original, unchanged Web cache deception and poisoning playbook. Use when CDN, reverse proxy, or application caching may serve sensitive authenticated content to other users due to path confusion or cache key manipulation. MIT View web-cache-deception wiki-ingest SignedBy sanyuan0704 · original, unchanged Compile articles, documents, or notes into a structured wiki knowledge base. Use when user says 'ingest to wiki', 'compile to knowledge base', 'update wiki', 'wiki ingest', 'add this to wiki', or invokes /wiki-ingest. Supports single or batch ingest. Triggers: wiki, ingest, knowledge base, compile, digest, index, catalog. MIT View wiki-ingest writing-style-and-tone SignedBy social-media-skills · original, unchanged The writing-craft skill — style and tone as applied technique: rhythm, specificity, tone modulation, and the edit passes that make writing read as human. Use when someone's posts "sound like ChatGPT," a draft needs a style edit, they ask how to write differently per platform or moment without losing the brand voice, writing is grammatically perfect but exhausting, a manager wants em dashes banned or detector scores chased, or any AI-assisted draft needs its mandatory quality pass. Uses the STYLE framework. Reads voice-builder + brand-profile + the format skill first. Tells must be read as a cluster with judgment — no single marker proves AI, and detectors misflag real writers; the winning move is substance so owned the question never arises. Voice is identity; tone is register. The agent drafts; the HUMAN supplies lived specifics and final say; never invents anecdotes or staged typos. Distinct from voice-builder, hook-writer, the format skills, and content-research-and-sourcing. MIT View writing-style-and-tone x-growth SignedBy social-media-skills · original, unchanged The X/Twitter growth playbook for 2026. Use when someone wants to "grow on X / Twitter," "get more reach/followers/impressions on X," "an X content/posting strategy," "should I get X Premium," "how the X algorithm works," or how to use replies/quote-posts/long-form/video to grow. Conversation is the engine (replies and first-hour velocity), Premium is effectively a baseline, and links go in the first reply. Uses the SPARK framework. Reads brand-profile + voice-builder first. The agent drafts posts + reply copy; a human does the live replying/quote-posts/community engagement; WoopSocial schedules posts; metrics come from native X analytics; nothing is fabricated. Complements thread-writer (thread-format craft). MIT View x-growth youtube-long-form SignedBy social-media-skills · original, unchanged The growth engine for YouTube long-form video in 2026. Use when someone asks to "grow my YouTube channel," "get more views on my videos," "plan/script a YouTube video," "improve my CTR or retention," "why did my video flop," or wants a long-form strategy. Produces packaging concepts + scripts; the human films/edits/designs the thumbnail; publishing routes through scheduling-and-queue -> WoopSocial; analytics and session features live in YouTube Studio. The opposite engine from, and sibling to, youtube-shorts. MIT View youtube-long-form youtube-publishing-and-metadata SignedBy social-media-skills · original, unchanged The YouTube publish-metadata skill. Use when someone wants to "write a YouTube title/description," "set tags/category/privacy," "optimize YouTube SEO/metadata," set made-for-kids, or publish a YouTube video via WoopSocial. Writes the metadata (title, description+chapters, tags) and sets category/privacy/madeForKids — YouTube is a search engine, so metadata is the launchpad, and madeForKids is a COPPA/FTC legal flag set truthfully. Uses the INDEX framework. Reads brand-profile + goals-and-kpis + the script/video first. The video file + script are inputs (not WoopSocial); the thumbnail and A/B title testing are native YouTube Studio; WoopSocial publishes via the YouTube fields; metrics never fabricated. Distinct from youtube-long-form/youtube-shorts (the script) and thumbnail-design (the thumbnail). MIT View youtube-publishing-and-metadata youtube-shorts SignedBy social-media-skills · original, unchanged The growth engine for YouTube Shorts in 2026. Use when someone asks to "grow on Shorts," "get views on YouTube Shorts," "write a Shorts script," "why did my Short flop," "make a vertical YouTube video," or wants a Shorts strategy. Drafts the script; the human films/ edits; publishing routes through scheduling-and-queue -> WoopSocial; analytics are read natively in YouTube Studio. Fully decoupled from, and sibling to, youtube-long-form. MIT View youtube-shorts ziniao-device SignedBy ziniao-open · original, unchanged 紫鸟设备管理:代理设备(IP)的查询、添加、修改、绑定/解绑、购买续费和自动续费。当用户需要查看代理设备列表、添加/修改自有代理、绑定设备到店铺或管理设备费用时使用。 MIT View ziniao-device ziniao-store SignedBy ziniao-open · original, unchanged Use when a request concerns the local 紫鸟/ZClaw browser, a store name or ID, listing/resolving/opening/reusing/closing a store browser, or a store-scoped task that starts from a store. Do not use for server-side account CRUD or for a webpage task on an already-open store. MIT View ziniao-store active-directory-certificate-services SignedBy yaklang · original, unchanged AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence. MIT View active-directory-certificate-services agent-md-refactor SignedBy softaworks · original, unchanged Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation. MIT View agent-md-refactor ai-image-editing SignedBy social-media-skills · original, unchanged The AI image-editing router — inpainting/object removal, background removal, upscaling, outpainting, old-photo restoration, and retouch, routed task-first to the right engine. Use when someone wants to remove an object/person from a photo, cut out backgrounds, upscale an image, extend an image to new aspect ratios, restore an old photo, fix a generated image, or asks which editing tool to use. Uses the TOUCH framework. Reads brand-profile + design-and-templates first. The agent names the task, routes to the right engine, writes the spec, and can call APIs where connected; the HUMAN judges every result at 100%; WoopSocial publishes. Honesty spine: an edited real photo is an edited claim — creative upscalers hallucinate detail (never on products/documents), no defect concealment, body-retouch disclosure honored, no watermark/provenance stripping. Distinct from image-prompt/flux/nano-banana (generation), canva (the design workflow), and before-after-and-transformation (the claim rules). MIT View ai-image-editing ai-video SignedBy social-media-skills · original, unchanged The model-agnostic AI-video router and brief — the counterpart to image-prompt. Use when someone asks "which AI video tool should I use," "make an AI video," "generate B-roll / a talking-head / a voiceover," "turn this long video into Shorts," or needs a video brief. Routes the job to the right tool by fit and writes a portable brief; the tool generates, the human assembles, WoopSocial schedules/publishes. Sits above the tool skills: veo-3, kling, luma (generative scenes), heygen, synthesia (avatars), ai-voiceover, captions-and-clipping. A real human on camera routes to talking-head-and-piece-to-camera. Never routes to discontinued tools. MIT View ai-video ai-voiceover SignedBy social-media-skills · original, unchanged The AI narration / voiceover mini-skill (ElevenLabs-led). Use when someone wants an "AI voiceover," "narration," "text-to-speech for a video," "voice for my Reel/Short/explainer," "clone my voice," or to "dub a video into other languages." Picks the voice and model, writes for the ear, and directs the delivery; ElevenLabs generates the audio, the human mixes/reviews, WoopSocial schedules/publishes. Sits below the ai-video router, sibling to veo-3 and heygen. Consented voices only; disclose AI voice in ads/political. MIT View ai-voiceover analytics-and-reporting SignedBy social-media-skills · original, unchanged Social media analytics and reporting — read native platform data honestly and turn it into next actions. Use when someone wants to "check my analytics," "see how my posts are doing," "build a social media report," "which content is working," "what metrics/KPIs should I track," or to turn performance data into next steps. Measures goal-mapped SIGNAL metrics (saves, shares, watch time/retention, engagement-rate-by-reach, follower-growth-rate, CTR, conversions) — not vanity (followers/impressions/likes) — and closes the loop. Uses the METER framework. Reads brand-profile + social-strategy (goals) first. WoopSocial has NO analytics surface, so this reads NATIVE platform dashboards (+ GA4/UTM) and interprets numbers the human provides; it NEVER fabricates a metric. Feeds content-recycling, experimentation, competitor-analysis, and every growth skill. Distinct from goals-and-kpis (sets targets) and experimentation (runs tests). MIT View analytics-and-reporting api-authorization-and-bola SignedBy yaklang · original, unchanged API authorization and BOLA testing playbook. Use when APIs expose object identifiers, nested resources, hidden writable fields, or weak function-level authorization. MIT View api-authorization-and-bola api-recon-and-docs SignedBy yaklang · original, unchanged API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing. MIT View api-recon-and-docs api-sec SignedBy yaklang · original, unchanged Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill. MIT View api-sec architecting-solutions SignedBy zhaono1 · original, unchanged Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead. MIT View architecting-solutions architecture-patterns SignedBy wshobson · original, unchanged Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers. MIT View architecture-patterns attack-path-stitcher SignedBy transilienceai · original, unchanged Stitches confirmed single-asset findings into multi-hop attack paths across the organization. Builds a graph where nodes are assets and edges are confirmed exploit hops citing the findings that enable them. MIT View attack-path-stitcher before-after-and-transformation SignedBy social-media-skills · original, unchanged The transformation / before-after content format — structure a credible, honest, satisfying transformation (fitness, beauty, business results, skill progress, makeovers, client glow-ups, product before/after). Use when someone wants a before/after, a transformation post, a client-results reveal, a progress/journey story, or a makeover. Most powerful format AND most abused/distrusted — honesty is the edge; FTC enforcement is live. Uses the SHIFT framework. Reads brand-profile + social-proof-and-testimonials (consent + FTC substantiation) + short-form-video-script first. Agent structures + specs; human/tool produces the real media; WoopSocial publishes. Never stages/exaggerates the before, hides aids, cherry-picks, or fabricates a result; "results not typical" alone is insufficient — disclose the actual typical result; consent + YMYL required. Distinct from social-proof-and-testimonials, short-form-video- script, infographic-and-data-viz, and storytelling-and-narrative. MIT View before-after-and-transformation behind-the-scenes-and-founder SignedBy social-media-skills · original, unchanged The transparency content type — turn what's actually happening inside the business into founder/personal-brand content that builds trust: build-in-public updates, founder story, how-it's-made content, team culture, and honest struggle posts. Use when someone wants behind the scenes, build in public, founder content, a personal brand post, or a day in the life. People follow people — founder-voice content out-performs brand-page content because it's specific and true. Uses the REVEAL framework. Reads brand-profile + voice-builder first. The agent finds the real moment, sharpens specifics + stakes, checks the transparency tier (share vs never: customer data, team conflicts, legal), and frames it in founder-voice; the human owns the reveal permanently; WoopSocial publishes. Never fabricates a struggle, performs vulnerability for reach, or exposes customer/team/legal matters. Distinct from contrarian-and-opinion, storytelling-and-narrative, social-proof, and the format writers. MIT View behind-the-scenes-and-founder binary-diff SignedBy zhaoxuya520 · original, unchanged 跨版本符号迁移与二进制差分。当你有旧版本的符号/逆向结果,需要快速迁移到新版本时使用。
适用场景:内核缺 PDB 用旧版符号推导、程序更新后批量迁移函数名、应用更新后快速定位新偏移。
核心方法:用 LLM 做结构化差异比对,程序化输入输出,成本极低(200 函数 ~1 元)。
触发关键词:符号迁移、bindiff、跨版本、PDB 缺失、函数偏移迁移、symbol migration、binary diff、版本对比。
MIT View binary-diff binary-ninja-reverse SignedBy zhaoxuya520 · original, unchanged Use for authorized binary analysis in Binary Ninja, including HLIL/MLIL/LLIL inspection, strings/imports/exports, cross-references, types, patch review, Python API automation, and optional Binary Ninja MCP or localhost HTTP integration. MIT View binary-ninja-reverse blender-mcp SignedBy vladmdgolam · original, unchanged Blender MCP expert for scene inspection, Python scripting, GLTF export, and material/animation extraction. Activate when: (1) using Blender MCP tools (get_scene_info, execute_python, screenshot, etc.), (2) writing Blender Python scripts for extraction or manipulation, (3) exporting scenes to GLTF/GLB for web (Three.js, R3F), (4) debugging material or texture export losses, (5) optimizing GLB files with gltf-transform, (6) using asset integrations (PolyHaven, Sketchfab, Hyper3D Rodin, Hunyuan3D). Covers critical export gotchas, material mapping survival, texture optimization pipeline, headless CLI patterns, and known failure modes. MIT View blender-mcp book-illustrator SignedBy jamesrochabrun · original, unchanged Expert children's book illustrator guide with 2024-2025 best practices, focusing on age-appropriate styles, color theory, character design, and visual storytelling for kids books that captivate young readers. MIT View book-illustrator book-study SignedBy sanyuan0704 · original, unchanged Reading coach: guides users through books systematically with knowledge compilation, mastery testing, spaced repetition, and knowledge querying. Use when user says 'read this book with me', 'book study', 'start studying X', 'reading plan', 'ingest this chapter', 'review what I read', 'quiz me on the book', 'what did the book say about X', or invokes /book-study. Supports sub-commands: ingest, query, review, compare, status. Triggers: book, study, read, chapter, ingest, review, quiz, reading plan, book notes. MIT View book-study browser-extension-reverse SignedBy zhaoxuya520 · original, unchanged Use for authorized reverse engineering of browser extensions (Chrome/Firefox) including manifest analysis, background workers, and extension-based credential or traffic logic recovery. MIT View browser-extension-reverse c4-architecture SignedBy softaworks · original, unchanged Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, create C4 diagrams, or generate context/container/component/deployment diagrams. Triggers include "architecture diagram", "C4 diagram", "system context", "container diagram", "component diagram", "deployment diagram", "document architecture", "visualize architecture". MIT View c4-architecture canva SignedBy social-media-skills · original, unchanged The Canva craft skill — produce on-brand social graphics, carousels, quote cards, infographics, and thumbnails at scale without a designer, and escape the "Canva look." Use when someone wants to design in Canva, make social graphics, set up a Brand Kit, batch-produce graphics (Bulk Create), resize one design for every platform (Magic Resize), use Canva's AI (Magic Studio), or asks why their posts look like a template. Uses the SCALE framework. Reads brand-profile + design-and-templates + voice-builder first. The agent specs, and creates designs directly where the Canva MCP/Connect APIs are connected; the human approves every visual; the export publishes via WoopSocial. Never strips watermarks, impersonates another brand, or uses unpermitted likeness; AI-disclosure + accessibility floor apply. Distinct from design-and-templates (the brand system this executes), image-prompt + the image tools (dedicated generation), ai-image-editing (the edit router), and capcut/descript (video editing). MIT View canva capacity-planning SignedBy aj-geddes · original, unchanged Analyze team capacity, plan resource allocation, and balance workload across projects. Forecast staffing needs and optimize team utilization while maintaining sustainable pace.
MIT View capacity-planning capcut SignedBy social-media-skills · original, unchanged The CapCut craft skill — edit short-form social video (TikTok, Reels, Shorts) fast and safely: retention-paced cuts, auto-captions, beat-synced sound, exports. Use when someone wants to edit in CapCut, cut a reel/short, set up auto-captions, use CapCut's AI tools, pick a plan, or asks whether CapCut music/assets or client work are safe commercially. Uses the EDITS framework. Reads short-form-video-script + brand-profile/design-and-templates + voice-builder first. The agent plans the edit and flags the licensing/ToS gates; the HUMAN executes in CapCut and approves; WoopSocial publishes the finished export. Safety spine: client/NDA work edits locally, never synced (the ToS licenses uploads), and music licensing has fine print — never pirated assets, non-consensual lip-sync, or uncorrected captions. Distinct from short-form-video-script (the script), captions-and-clipping/opus-clip (clipping long video), descript (long-form), canva (graphics), and ai-video/veo-3/kling/runway (generation). MIT View capcut captions-and-clipping SignedBy social-media-skills · original, unchanged The long-form-to-Shorts + sound-off captions mini-skill (Opus Clip / CapCut / Submagic). Use when someone wants to "clip my podcast/webinar/long video into Shorts," "make TikToks/Reels from a YouTube video," "add captions/subtitles to a video," "repurpose long-form into short-form," or "auto-generate clips." Tools clip and caption; a human reviews; WoopSocial schedules/publishes. Below the ai-video router; sibling to veo-3, heygen, ai-voiceover. This is the general craft: route OpusClip-specific pipelines (credits, Virality Score, tiers) to opus-clip, hands-on short-form editing to capcut, and the long-form talk edit itself to descript. Export clean (no watermark); disclose AI-edited video. MIT View captions-and-clipping carousel-writer SignedBy social-media-skills · original, unchanged Use to write a carousel — a swipeable multi-slide post (Instagram carousel, LinkedIn document/PDF carousel, or TikTok photo carousel) — one of the highest-save, highest-dwell formats. Run when the user says "write a carousel," "carousel post," "slides for X," "LinkedIn document/PDF post," "swipe post," "turn this into a carousel," or wants multi-slide teaching or story content. Reads brand-profile and voice first; the cover slide hooks and promises the swipe (via hook-writer); each slide advances one idea and earns the next swipe; ends on a save-leaning CTA. Specifies the design direction and bundles an image-generation prompt pack (Nano Banana / Ideogram) for the slide visuals. Hands the caption to caption-writer and scheduling to scheduling-and-queue. MIT View carousel-writer changelog-writing SignedBy samber · original, unchanged Turns raw commits, pull requests and tickets into release notes developers actually read - a scannable record of what shipped, what it means in practice, and what breaks. Use whenever the user mentions a changelog, CHANGELOG.md, release notes, a GitHub release body for a tag, a hosted "what's new" page, app-store release notes, Keep a Changelog, or Common Changelog, or asks what to write for a release they just cut - even when the commit history is messy and follows no commit convention. Not for version bumping, tagging or publishing pipelines. Do NOT use for a full breaking-change upgrade guide - use samber/developer-relations-skills@version-migration-guide; for a narrative release post use samber/developer-relations-skills@engineering-blog-post. MIT View changelog-writing code-review-expert SignedBy sanyuan0704 · original, unchanged Expert code review of current git changes with a senior engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. MIT View code-review-expert code-to-spec SignedBy smallnest · original, unchanged Reverse-engineer a SPEC document from an existing project. Analyzes code, config, tests, and structure to produce a comprehensive specification. Triggers on: code-to-spec, reverse spec, generate spec, 逆向规格, 生成规格文档, 生成设计文档, 生成设计方案, extract spec, document this project, what does this project do. MIT View code-to-spec collabs-and-cross-promotion SignedBy social-media-skills · original, unchanged Creator collabs and cross-promotion — organic creator-to-creator partnerships that swap audiences. Use when someone wants to set up a collab, audience swap, cross-promotion, shoutout swap, joint giveaway, guest spot, joint video/series, a YouTube/IG collab post, or co-promo with another creator. Picks a complementary, similar-size, values-aligned partner, agrees the plan before creating, and co-creates shared-value content (not a bare shoutout) on a coordinated schedule. Uses the UNITE framework. Reads brand-profile + goals-and-kpis first. WoopSocial publishes each partner's OWN posts to their OWN accounts; it does NOT create native IG Collab co-authored posts, run giveaways, duet/stitch, or manage the agreement. A pure mutual collab isn't a sponsorship, but payment/free product makes it one -> disclose -> ugc-and-influencer; partnerships must be genuine; metrics never fabricated. Distinct from ugc-and-influencer (brand->creator) and creator-monetization (the creator's income). MIT View collabs-and-cross-promotion command-creator SignedBy softaworks · original, unchanged This skill should be used when creating a Claude Code slash command. Use when users ask to "create a command", "make a slash command", "add a command", or want to document a workflow as a reusable command. Essential for creating optimized, agent-executable slash commands with proper structure and best practices. MIT View command-creator commit-work SignedBy softaworks · original, unchanged Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits. MIT View commit-work community-management SignedBy social-media-skills · original, unchanged Use to build a genuine community — turning an audience into people who interact with each other, not just with the brand. Run when the user asks how to build community, foster belonging/loyalty, create superfans, start a group/Discord channel, get members talking to each other, or move beyond chasing followers/virality. Reads brand-profile/social-strategy/audience-research. Community outperforms virality, measured by relationship depth/retention, not follower count. Covers the audience-to-community distinction (member-to-member interaction), choosing the space (in-feed -> semi-owned -> owned groups/Discord), recurring rituals, building belonging, and nurturing superfans into advocates. KPIs read natively, never fabricated. Advisory: WoopSocial schedules the content but does NOT run Discord/Slack or show analytics — the human runs the community, the agent drafts. Never fake community; get consent before spotlighting. Pairs with reply-and-comment-writer and crisis-and-moderation. MIT View community-management conference-cfp-submission SignedBy samber · original, unchanged Turns a talk idea into a submission-ready conference proposal for one specific event, or helps choose which conferences to target and plan a submission calendar across several - track fit, title options, an attendee-facing abstract, verb-first takeaways, the reviewer-only fields, a credibility package, and a self-review against the committee's own criteria. Use whenever the user mentions a CFP, a call for papers, a conference proposal, a talk abstract, a session description, submitting to KubeCon, PyCon or FOSDEM, which conference to submit to, planning a CFP season, or says their proposals keep getting rejected - even if they only ask to shorten an abstract. Covers community-run and vendor-run events. Do NOT use for structuring the accepted talk (samber/developer-relations-skills@tech-talk-outline) or its demo (samber/developer-relations-skills@developer-live-demo-design). MIT View conference-cfp-submission content-pillars SignedBy social-media-skills · original, unchanged Use to define a brand's content pillars — the 3–5 recurring themes it posts about — the strategic backbone between the brand profile and the content calendar. Run when the user says "content pillars," "content buckets," "what should I post about," "content themes," "content strategy," "pillars," or before planning a batch or calendar. Reads brand-profile first and derives pillars from positioning, point of view, audience, and proof — real ownable themes, never generic "educational / behind-the-scenes / promotional" buckets (those are intents and formats, not pillars). Produces a content-pillars.md that batch-content-plan and the content skills read. Works for any business: B2B, ecommerce, local, personal brand, nonprofit. MIT View content-pillars content-recycling SignedBy social-media-skills · original, unchanged Content recycling — resurface, update, and repost proven evergreen content over time. Use when someone wants to "get more mileage out of old posts," "recycle/repost our best content," "resurface evergreen pieces," "update and republish an old post," or build a recycling queue of proven winners. Recycles the INSIGHT refreshed (new hook/format/updated data) on a deliberate cadence — never an identical repost. Distinct from cross-platform-repurposing (same moment, many platforms) and captions-and-clipping (long-form -> short clips). Reads brand-profile + voice-builder first. The agent drafts the refresh; a human reviews; WoopSocial schedules/publishes (delete+recreate, no update); winners are picked from native analytics; nothing is fabricated. MIT View content-recycling content-research-and-sourcing SignedBy social-media-skills · original, unchanged The research-and-sourcing craft — verify the substance of a piece before it publishes: trace stats to primary sources, kill zombie stats, catch AI-hallucinated citations, and attribute properly on social. Use when someone has a stat-heavy draft to make publish-ready, wants to check if a viral statistic is real, asks how to cite sources, used AI research output, or is making health/finance claims. Uses the FACTS framework. Reads brand-profile + the piece's format skill first. AI-supplied citations are guilty until verified; a working link is not verification; aggregators are leads, not the source; where none exists, reframe as owned observation or commission data. The agent verifies where it has search; the human clicks links where it doesn't; verification happens before scheduling; WoopSocial publishes. Never invents studies or reuses retracted stats. Distinct from idea-generation, data-and-original-research, quote-cards, and infographic-and-data-viz. MIT View content-research-and-sourcing contrarian-and-opinion SignedBy social-media-skills · original, unchanged The point-of-view content type — articulate, sharpen, and argue a genuinely-held contrarian stance / hot take / opinion / thought-leadership position that builds authority and real debate. Use when someone wants a POV, a hot take, an "unpopular opinion", a contrarian angle, an opinion piece, or to stop sounding like everyone else and build thought leadership. Uses the STAND framework. Reads brand-profile + voice-builder first. The agent argues the human's OWN opinion with evidence; the human owns the stance and the live debate; WoopSocial publishes. Never manufactures a stance, controversy, or ragebait; no strawmen, punching down, or defamation; opinion stays clearly opinion and factual claims must be true. Distinct from hook-writer (the opening-line mechanic this feeds), educational-content-and-how-to (teaches a process), storytelling-and-narrative (narrative vs argument), and behind-the-scenes-and-founder (personal story vs argued position). MIT View contrarian-and-opinion create-pr SignedBy zhaono1 · original, unchanged Creates pull requests with bilingual documentation checks. Use when user asks to create PR, make a pull request, or submit changes for review. Ensures English and Chinese README files stay in sync when user-facing skill catalog changes require it. MIT View create-pr creator-monetization SignedBy social-media-skills · original, unchanged Creator monetization — build a diversified revenue portfolio from an audience: memberships, products, brand deals, platform payouts. Use when someone wants to "make money as a creator," "monetize my audience," "start a membership/community," "sell a course/digital product," "get brand deals / set my rates," or build diversified creator income. Builds a revenue STACK rather than chasing a viral payout, using the STACK framework. Reads brand-profile + goals-and-kpis first. WoopSocial does NOT process payments, host products/memberships, or pay creators: the agent chooses/sequences streams, designs offers + media kit, and drafts promo posts; WoopSocial publishes the promo/launch posts; infrastructure is external; income is never promised or fabricated; sponsorships are disclosed (FTC). Distinct from email-and-newsletter (the owned channel), lead-magnets-and-funnels (funnel mechanics), and ugc-and-influencer (the BRAND side of creator deals — this is the creator side). MIT View creator-monetization crisis-and-moderation SignedBy social-media-skills · original, unchanged Use when something goes wrong on social — the crisis-and-moderation playbook for negative moments, pile-ons, misinformation/deepfakes about the brand, offensive-post backlash, and community moderation. Run when the user says "we're getting piled on," "someone's spreading false info about us," "should we delete/hide this," "a deepfake of our brand," or needs to moderate a community. Reads brand-profile/voice. Confirm facts and triage severity first; acknowledge fast; speak human, not legalese; correct misinformation with evidence, not an apology; moderate fairly (hide abuse, leave honest criticism). HIGH-STAKES and human-in-the-loop: a crisis is when the agent must NOT act autonomously — it triages, drafts holding statements, and can pause/reschedule posts via scheduling-and-queue, while a HUMAN (and legal/leadership for high-severity) approves everything and moderates in-platform. WoopSocial has no comment/inbox/moderation surface; never auto-respond or fabricate facts. MIT View crisis-and-moderation crlf-injection SignedBy yaklang · original, unchanged CRLF injection playbook. Use when user input reaches HTTP response headers, Location redirects, Set-Cookie values, or log files where carriage-return/line-feed characters can split or inject content. MIT View crlf-injection cross-platform-repurposing SignedBy social-media-skills · original, unchanged 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. MIT View cross-platform-repurposing csv-formula-injection SignedBy yaklang · original, unchanged CSV/spreadsheet formula injection (DDE, Excel/LibreOffice, Google Sheets IMPORT*). Use when exports, imports, or user fields feed spreadsheets or reporting tools. MIT View csv-formula-injection dashfix SignedBy sentimony · original, unchanged You MUST use this when writing or substantively editing prose in a project (docs, READMEs, UI copy) and when asked to audit, count, score, or clean up dash usage - it enforces the plain hyphen over typographic dashes in text of any language. MIT View dashfix database-security SignedBy zhaoxuya520 · original, unchanged Use for authorized database security assessment covering PostgreSQL/MySQL/MSSQL/Mongo/Redis exposure, authz, UDF/command paths, and misconfiguration review. MIT View database-security database-sharding SignedBy aj-geddes · original, unchanged Implement database sharding for horizontal scalability. Use when scaling large databases, distributing data across multiple servers, or designing sharded architectures.
MIT View database-sharding dataset-curation SignedBy wshobson · original, unchanged Prepare, format, and validate datasets for supervised fine-tuning and preference training. Use when converting raw data into training format, applying chat templates, configuring sequence packing, generating synthetic training data, or writing a dataset card before a run. MIT View dataset-curation db-migration-helper SignedBy wu529778790 · original, unchanged Use when generating database migration SQL from model or schema changes — compares current vs desired schema, detects diffs, outputs reversible safe migrations. MIT View db-migration-helper defi-attack-patterns SignedBy yaklang · original, unchanged DeFi attack pattern playbook. Use when analyzing flash loan attacks, price oracle manipulation, MEV sandwich attacks, governance exploits, bridge vulnerabilities, and token standard edge cases in decentralized finance protocols. MIT View defi-attack-patterns dependency-tracking SignedBy aj-geddes · original, unchanged Map, track, and manage project dependencies across teams, systems, and organizations. Identify critical path items and prevent blocking issues through proactive dependency management.
MIT View dependency-tracking dependency-updater SignedBy softaworks · original, unchanged Smart dependency management for any language. Auto-detects project type, applies safe updates automatically, prompts for major versions, diagnoses and fixes dependency issues. MIT View dependency-updater developer-case-study SignedBy samber · original, unchanged Turns a customer's real production deployment into a technical case study engineers believe - measured numbers tied to how they were measured, before-and-after architecture, published limitations, and cleared naming and quote approval. Use whenever the user mentions a customer case study, a technical case study, a developer adoption or success story, a reference customer, or wants to turn a user interview, migration or production rollout into published proof - even if they only say "a post about how Acme uses us". Do NOT use for a post about your own system - use samber/developer-relations-skills@engineering-blog-post; for your own project's ongoing progress use samber/developer-relations-skills@build-in-public. MIT View developer-case-study developer-champions SignedBy samber · original, unchanged Designs an unpaid, perks-only developer champions or ambassador program end to end - readiness check, intake model, published selection criteria, behaviour-based obligations, an access-first perk ladder, fixed terms with renewal and alumni status, and a cohort scorecard. Use whenever the user mentions an ambassador or champions program, MVP-style recognition, community heroes, "how do we recognise our top community members", what perks ambassadors should get, an ambassador program that went quiet, or removing an inactive champion - even if they never say "champion". Not for paid creator, affiliate or revenue-share partnerships. For measuring the community itself use samber/developer-relations-skills@developer-community-health. MIT View developer-champions developer-community-launch SignedBy samber · original, unchanged Decides whether, where and when to launch a developer community, then plans its seeding and first 90 days - venue selection, founding-member seeding, go/no-go criteria, the cheaper no-community alternatives, and shutdown criteria. Use whenever someone asks whether to start a Discord, Slack or forum for their users, which community platform to pick, how to launch or seed a developer community from zero, or how to reach critical mass - even if they only say "we should have a Discord". Do NOT use for a community that already exists; measurement is samber/developer-relations-skills@developer-community-health and moderation is samber/developer-relations-skills@developer-community-moderation. MIT View developer-community-launch developer-ecosystem-strategy SignedBy samber · original, unchanged Decides whether, when and how far a developer product should open into a platform other companies build on - extension points, partner-built integrations, third-party apps, a complement ecosystem - and what that permanently obliges you to. Use whenever someone asks if the product should become a platform, whether to open extension points or an app model to third parties, how to start an integration ecosystem, why nobody builds on the API, whether partners should build the connectors, or how much value complementors must keep - even if they only say "we want an integrations story". Not marketplace operations or API design. Do NOT use for the revenue model - use samber/developer-relations-skills@devtools-business-model. MIT View developer-ecosystem-strategy developer-education-strategy SignedBy samber · original, unchanged Decides whether and how to invest in structured developer education, such as learning paths, a developer academy, hands-on labs, badges or a full certification program - instead of more ad-hoc content, then designs its operating model, staffing, refresh cadence, measurement and kill rules. Use whenever someone mentions a developer academy, certification, a developer curriculum, training for developers, learning paths, skill badges or credentials, "should we certify our users", partner or SI enablement training, or scaling developer onboarding beyond docs - even if they only say "we need more training content". Covers B2B, partner and bottom-up motions. Never writes the courses themselves. Use samber/developer-relations-skills@developer-tutorial for a lesson. MIT View developer-education-strategy developer-first-gtm SignedBy samber · original, unchanged Designs the go-to-market motion for a developer-facing product - bottom-up self-serve adoption, developer-influenced sales, top-down with developer proof, or ecosystem-mediated distribution - plus the self-serve entry, the developer-to-buyer handoff rule and the land-and-expand path. Use whenever a founder, devrel or growth owner asks how developer adoption turns into revenue, whether to go bottom-up or hire sales, when to contact a free user, why signups are high and paid accounts flat, or how landed teams expand across an enterprise - even if they only say "our funnel is broken". Not price points - use samber/developer-relations-skills@devtools-pricing-strategy. MIT View developer-first-gtm developer-keyword-research SignedBy samber · original, unchanged Builds a prioritized keyword list for technical search queries (error strings, "how to X in Y" tasks, integration intents, comparisons, migrations) mined from docs search logs, support tickets, issue trackers and first-party query data rather than keyword-tool volume. Use whenever the user asks what developers actually search for, wants keywords for a developer tool, API, SDK or docs site, an error-message keyword list, demand sizing for a technical topic, or which docs pages to create from search demand - even if they never say "keyword". Does not write the pages. Do NOT use for on-page or docs-site SEO - use samber/developer-relations-skills@docs-seo. MIT View developer-keyword-research developer-portal-design SignedBy samber · original, unchanged Design an external developer portal as a product surface, not a documentation site - information architecture for business evaluators and integrating engineers, the signup-to-first-call onboarding path governed by time to first call (TTFC), placement of each self-service surface (key dashboard, request logs, sandbox, usage metering, docs entry points), portal search with an AI answer assistant, RBAC and multi-tenant hierarchy, and the build-vs-buy platform decision. Use whenever the user mentions a developer portal, developer console, API dashboard, developer onboarding, or time to first call - even if they never say "portal". External API-consumer portals only, not internal service catalogs. MIT View developer-portal-design developer-segmentation SignedBy samber · original, unchanged Cuts a developer audience into a few named, sized and ranked segments - the two dimensions worth cutting on, a size range with a confidence tier, the user/champion/approver/buyer split inside each, a weighted score, one primary and one secondary segment, and a written anti-segment. Use whenever someone asks who their developers actually are, which developer audience to serve first, how big a language ecosystem or persona is, whether to target hobbyists or enterprise platform teams, who signs when the developer is not the buyer, or why content reaches everyone and converts nobody - even if they only say "who is this for". Not the journey map - use samber/developer-relations-skills@developer-journey-map. MIT View developer-segmentation developer-tutorial SignedBy samber · original, unchanged Writes or audits a teaching tutorial for a developer product - one new concept per step, checkpoints the learner can verify and resume from, guidance that fades, troubleshooting hooks, and a demonstrable skill at the end. Use whenever the user mentions a tutorial, a build-along or hands-on guide, a "learn X by building Y" article, a workshop or lab handout, a developer course lesson, or says nobody finishes their tutorial - even if they just say "write a guide that teaches this". Do NOT use for a zero-to-first-success quickstart (samber/developer-relations-skills@developer-quickstart-guide) or a video script (samber/developer-relations-skills@technical-video-script). MIT View developer-tutorial develop-userscripts SignedBy xixu-me · original, unchanged Use when building, debugging, packaging, or publishing browser userscripts for Tampermonkey or ScriptCat, including GM APIs, metadata blocks, permission issues, @match/@grant/@connect setup, ScriptCat background or scheduled scripts, UserConfig blocks, or subscription workflows. MIT View develop-userscripts devrel-analytics SignedBy samber · original, unchanged Builds the tracking plan that instruments developer-relations surfaces - docs, blog, repositories, package registries, community venues, and off-web appearances - with an event taxonomy, an identity spine, link-tagging discipline, source-confidence labelling, and funnel views. Use when the user says "devrel tracking plan", "docs analytics", "utm discipline", "event taxonomy for our docs", "our GitHub numbers don't match analytics", "how do we instrument the developer funnel", "join docs traffic to signups", or wants to know why devrel numbers disagree between tools. Instrumentation layer only - which KPIs deserve a target belongs to samber/developer-relations-skills@devrel-metrics. MIT View devrel-analytics devrel-career SignedBy samber · original, unchanged Plans, lands and advances a developer relations career from the candidate side - developer advocate, developer evangelist, DevRel engineer, community manager, developer educator, DX engineer. Covers portfolio audits against real hiring signals, a zero-to-hireable artefact curriculum, the six-rung IC ladder, the interview formats DevRel loops use (talk round, content and coding take-homes, DevRel-opinion round), gatekeeper and pit-trap patterns in postings, and offer evaluation weighing reporting line before pay. Use whenever someone asks how to break into DevRel, prep a developer advocate interview, build a DevRel portfolio, choose a track, plan the next rung, or weigh a DevRel offer - even if they only say "should I take this advocate job". Not a job-search tool. MIT View devrel-career devrel-competitor-analysis SignedBy samber · original, unchanged Benchmarks a competitor's developer relations motion from publicly observable signals - documentation and quickstart quality, open-source repository health, community size and responsiveness, Q&A tag activity, content cadence by format, event presence, hiring signals - and returns a gap plan with a close, ignore or counter verdict per row. Use whenever the user asks for a devrel competitive benchmark, a developer experience comparison, "how do we compare to <competitor> for developers", "what is <competitor> doing in devrel", a community size or content cadence comparison, or a docs comparison against rivals - even if they only say "why do they get more developers". Not for measuring your own program alone - use samber/developer-relations-skills@devrel-metrics. MIT View devrel-competitor-analysis devrel-content-calendar SignedBy samber · original, unchanged Plans a quarter of developer-relations content as a dated slot plan with named owners and reviewers - fixed anchors (releases, launches, CFP deadlines, conferences), a surface, pillar, journey and shelf-life mix, and sizing against real writing and review capacity. Use whenever the user asks for a devrel content calendar, an editorial calendar or content plan for a developer audience, what to publish next quarter, how to balance evergreen against launch-tied content, how many pieces a small team can ship, or says their content plan keeps slipping - even if they only say "we publish randomly". Plans the quarter only; individual pieces go to the per-format skills such as samber/developer-relations-skills@engineering-blog-post. MIT View devrel-content-calendar devrel-strategy SignedBy samber · original, unchanged Designs a company's developer relations program from the top - the business driver that funds it, the two goals it is allowed to serve, the pillar mix (advocacy, marketing, enablement, community) for its stage, audience priority, build-vs-buy per bet, staffing sequence, and a written refused list. Use whenever someone asks whether to start doing DevRel, what a new devrel program should do first, why devrel work is busy but not landing, how to justify the program to an exec, which pillar deserves the next investment, who to hire next, or whether to outsource content, events or community - even if they never say "strategy". Not the first-90-days plan - use samber/developer-relations-skills@developer-relations-kickoff. Not metrics, org chart or budget math. MIT View devrel-strategy devrel-team-structure SignedBy samber · original, unchanged Designs the developer relations org - which function DevRel reports to (marketing, product, engineering, CEO, sales) and what that line starves, the shape (centralized, split, embedded, hub-and-spoke), the coverage map across advocacy, community, docs and education, the interlocks with product, docs, support and sales, and the trigger for the next re-org. Use whenever someone asks where DevRel should sit, who DevRel should report to, how to structure or restructure a devrel team, which devrel roles to staff at this size, whether to embed advocates in product teams, why devrel keeps getting pulled into other teams' work, or how devrel and docs divide ownership - even if they only say the team feels wrong. Not the budget split - use samber/developer-relations-skills@devrel-budget-allocation. MIT View devrel-team-structure devtools-business-model SignedBy samber · original, unchanged Chooses the business model for a developer tool - proprietary SaaS, open core, hosted open source, support and LTS subscription, dual licensing, source-available, consumption metering, marketplace take-rate, OEM licensing - and the go-to-market each one forces. Use whenever a founder or exec asks how a developer tool should make money, whether open core or a managed cloud fits better, where the line between free and paid belongs, whether to open-source the product at all, or why adoption is high and revenue flat, and on any monetization, revenue model or commercial open source question - even if they never say "business model". Not price points, packaging or free-tier limits - use samber/developer-relations-skills@devtools-pricing-strategy. MIT View devtools-business-model devtools-pricing-strategy SignedBy samber · original, unchanged Designs the pricing and packaging architecture of a developer tool - the value metric (seats, consumption, capacity, outcome, or a hybrid), free-tier limits, the tier ladder up to enterprise gating, price points bounded by a margin floor and the self-host and build-it ceilings, and a plan to change prices without a backlash. Use whenever someone asks what to charge for a developer tool, how to package tiers, where free ends and paid begins, whether to bill per seat or per usage, how to price against their own open-source edition, or how to raise prices safely - even if they only say the pricing page feels wrong. Not which business model to run - use samber/developer-relations-skills@devtools-business-model. Not pricing-page copy. MIT View devtools-pricing-strategy difficult-workplace-conversations SignedBy softaworks · original, unchanged Structured approach to workplace conflicts, performance discussions, and challenging feedback using preparation-delivery-followup framework. Use when preparing for tough conversations, addressing conflicts, giving critical feedback, or navigating sensitive workplace discussions. MIT View difficult-workplace-conversations digital-forensics SignedBy zhaoxuya520 · original, unchanged Use for authorized digital forensics including memory dumps, disk timelines, PCAP investigation, artifact triage, and IR evidence preservation. MIT View digital-forensics directory-submissions SignedBy coreyhaines31 · original, unchanged When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "publish my MCP server," "awesome list," "llms.txt directory," "Claude plugin directory," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo. MIT View directory-submissions docs-seo SignedBy samber · original, unchanged Runs on-page and technical SEO for a documentation site - indexability, canonicals and hreflang across versioned and translated pages, redirects, the generator's title and description templates, internal linking, and an owner-assigned fix list against an agreed pass threshold. Use whenever someone says "docs SEO", "our docs don't rank", "documentation search optimization", "the old version of our docs outranks the current one", "our docs pages aren't indexed", "fix the canonicals on our docs", "docs sitemap problems", "hreflang on our translated docs" or "preview docs got indexed" - even if they never say SEO. Covers versioned, translated and auto-generated reference docs. Not keyword research - use samber/developer-relations-skills@developer-keyword-research. MIT View docs-seo documentation-engineer SignedBy zhaono1 · original, unchanged Technical documentation expert for creating clear, comprehensive documentation. Use when user asks to write docs, create README, or document code. MIT View documentation-engineer domain-name-brainstormer SignedBy softaworks · original, unchanged Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking. MIT View domain-name-brainstormer echarts SignedBy sentimony · original, unchanged You MUST use this when building, styling, debugging, or optimizing Apache ECharts charts in JavaScript, React, or Vue - setup, lifecycle, responsive resizing, theming, large datasets, streaming, SSR, and symptoms like a blank chart or broken resize. Not for choosing chart types or for other charting libraries. MIT View echarts editor SignedBy diffusionstudio · original, unchanged Understand, generate, and edit footage with Diffusion Studio: analyze video/audio/images, generate them with AI, and compose video compositions. Use for any media analysis, media generation, or video editing task. MIT View editor educational-content-and-how-to SignedBy social-media-skills · original, unchanged The teach-to-grow content type -- pick a genuinely useful topic, teach ONE thing completely, structure it as a clear lesson, keep it accurate, and route it to the right format. Use when someone wants to teach their audience, make a how-to / tutorial / step-by-step / explainer / myth-buster, build authority content, or earn saves. Uses the TEACH framework. Reads brand-profile + audience-research + content-pillars first. Feeds the format writers (carousel-writer, reels-script, tiktok-script, thread-writer, caption-writer), hook-writer, the design/image tools, and lead-magnets/social-selling-and-dm; WoopSocial publishes + schedules the series. Accuracy is non-negotiable: cite sources, stay within real expertise, YMYL care, never fabricate steps or stats; measure saves/sends, not likes. Distinct from carousel-writer (the format it pairs with), reels-script/tiktok-script/thread-writer (other formats), storytelling-and-narrative (narrative vs didactic), and content-pillars (which topics). MIT View educational-content-and-how-to email-smtp-send SignedBy tiangong-ai · original, unchanged Send emails through SMTP with optional local attachments and optional IMAP APPEND sync to Sent mailbox. Use when tasks need reliable outbound email delivery, attachment sending, SMTP connectivity checks, or cross-client sent-mail visibility (for example appending to "Sent Items" after SMTP send). MIT View email-smtp-send engagement-routine SignedBy social-media-skills · original, unchanged Use to design a sustainable engagement routine — the operating system that turns the engagement craft into a daily/weekly habit. Run when the user asks how to keep up with comments/DMs, how much time to spend engaging, when to engage, how to build an engagement habit/system/cadence, or how to engage without burning out. Reads brand-profile/social-strategy. Covers time-boxed daily/weekly engagement windows built around the golden hour after posting, triage order, mapping engagement to a goal, and anti-burnout boundaries. The flywheel: batch and schedule content (scheduling-and-queue, batch-content-plan) to free the time, then spend it engaging. Advisory and honest — WoopSocial has no comment/DM/inbox surface and no analytics, so the human engages in-app and the agent drafts via reply-and-comment-writer; never automates or fakes engagement. Pairs with reply-and-comment-writer (the craft), the growth skills, community-management, and crisis-and-moderation. MIT View engagement-routine engineering-blog-post SignedBy samber · original, unchanged Writes or edits a technical blog post a skeptical developer audience will believe - the right post pattern, evidence behind every claim, published trade-offs and limitations, runnable snippets, and no marketing voice. Use whenever the user wants an engineering blog post, a technical article, a "how we built it" or "we rewrote it in X" story, a debugging write-up, a public postmortem, a benchmark post, or a product post that must not read as marketing, and when they ask to review, edit, de-jargon or de-market an existing technical draft - even if they only call it "the article". Not a teaching tutorial - use samber/developer-relations-skills@developer-tutorial. Not release notes, a migration guide, a case study or a talk. MIT View engineering-blog-post etl-connector-strategy SignedBy samber · original, unchanged Plan a SaaS vendor's presence as a source connector on third-party ETL/ELT platforms - demand validation before any build, platform selection from where customers' data stacks run, a build-path menu (platform-managed listing, vendor-maintained SDK connector, custom open-source tap) ranked by who absorbs the maintenance tax, an extraction-readiness audit of the product API, honest CDC scoping (API sources ship pseudo-CDC, never log-based), certification targets, and a funded maintenance plan. Use whenever the user mentions an ETL or ELT catalog listing, a source connector, data-pipeline integration, or adding CDC - even if they never say "connector strategy". Do NOT use for the vendor's own inbound marketplace - use samber/developer-platform-skills@connector-marketplace-strategy instead. MIT View etl-connector-strategy excalidraw SignedBy softaworks · original, unchanged Use when working with *.excalidraw or *.excalidraw.json files, user mentions diagrams/flowcharts, or requests architecture visualization - delegates all Excalidraw operations to subagents to prevent context exhaustion from verbose JSON (single files: 4k-22k tokens, can exceed read limits) MIT View excalidraw experimentation-and-ab-testing SignedBy social-media-skills · original, unchanged A/B testing and experimentation for social media content — evidence over opinion, at honest organic-scale rigor. Use when someone wants to "A/B test" or "split test" content, "test which version/hook/time/caption/thumbnail works," "set up an experiment," "what should I test," or to settle a content debate with evidence instead of opinion. Designs disciplined organic tests: one variable, controlled context, a decision rule set BEFORE publishing, enough duration and repetitions to separate signal from noise. Uses the TEST framework. Reads brand-profile + goals-and-kpis first. It DESIGNS the test and drafts variants; WoopSocial schedules them as controlled sequential posts (exception: YouTube's native Test & Compare); the result is read from native analytics via analytics-and-reporting. Organic can't reach true statistical significance; nothing is fabricated or p-hacked. Distinct from analytics-and-reporting (measures) and goals-and-kpis (sets targets). MIT View experimentation-and-ab-testing expression-language-injection SignedBy yaklang · original, unchanged Expression Language injection playbook. Use when Java EL, SpEL, OGNL, or MVEL expressions may evaluate attacker-controlled input in Spring, Struts2, Confluence, or similar frameworks. MIT View expression-language-injection facebook-groups SignedBy social-media-skills · original, unchanged The Facebook Groups strategy skill -- Groups as Facebook's real organic surface, deeper than what facebook-strategy routes to community-management. Use when someone wants to build/grow/run a Facebook Group, decide Group vs Page, or turn a community into leads. Groups reach 40-50% of members per post vs ~1.5% for Pages; Facebook deliberately favors Groups. Uses the TRIBE framework. Reads brand-profile + goals-and-kpis first. The agent designs the group strategy (niche, setup, content, growth, moderation, value-first monetization) and drafts group posts + the join-funnel content. CRUCIAL: WoopSocial does NOT post to Groups -- it publishes the Page + cross-channel content that funnels people to JOIN; in-group posting, admin, moderation, and Group analytics stay native/human, routed to community-management. No automation/spam or fake members; value-first, never fabricates metrics. Distinct from facebook-strategy (the Page play) and community-management (the engagement routine). MIT View facebook-groups facebook-strategy SignedBy social-media-skills · original, unchanged The Facebook strategy playbook for 2026. Use when someone wants to "grow on Facebook," "fix my Facebook reach," "a Facebook content/Page strategy," "Facebook Reels," or how the Facebook algorithm works now. Page feed broadcasting is effectively dead (~1.65% reach); Facebook is now an AI discovery engine plus a community platform. Play three surfaces: Reels for unconnected discovery, Feed for connected depth, Groups for community. Uses the REACH framework. Reads brand-profile + voice-builder first. The agent drafts Page posts/Reels + reply copy; WoopSocial schedules Page posts/Reels; comment replies are human/in-app; metrics come from native Meta Insights; nothing is fabricated. To BUILD/GROW/RUN a Facebook Group (the deep Groups strategy) use facebook-groups; distinct from reels-script (Reel craft), community-management (engagement routine), and instagram-growth (sibling). MIT View facebook-strategy feedback-mastery SignedBy softaworks · original, unchanged Navigate difficult conversations and deliver constructive feedback using structured frameworks. Covers the Preparation-Delivery-Follow-up model and Situation-Behavior-Impact (SBI) feedback technique. Use when preparing for difficult conversations, giving feedback, or managing conflicts. MIT View feedback-mastery figma-designer SignedBy zhaono1 · original, unchanged Analyzes Figma designs into implementation-ready visual evidence, tokens, component specifications, and interaction states for handoff to planning or development. MIT View figma-designer finetuning-method-selection SignedBy wshobson · original, unchanged Decide whether to fine-tune at all, and route to the right method (SFT, DPO/ORPO/KTO, GRPO/RLVR, continued pretraining) and base model. Use when starting any fine-tuning effort, when unsure whether RAG or prompting would suffice, or when choosing between preference-optimization and reinforcement methods. MIT View finetuning-method-selection frontend-accessibility-best-practices SignedBy sergiodxa · original, unchanged Accessibility (a11y) best practices for React components. Use when creating UI components, forms, interactive elements, or reviewing code for accessibility compliance. MIT View frontend-accessibility-best-practices frontend-testing-best-practices SignedBy sergiodxa · original, unchanged Testing best practices for the frontend. Emphasizes E2E tests over unit tests, minimal mocking, and testing behavior over implementation details. Use when writing tests or reviewing test code. MIT View frontend-testing-best-practices frontend-to-backend-requirements SignedBy softaworks · original, unchanged Document frontend data needs for backend developers. Use when frontend needs to communicate API requirements to backend, or user says 'backend requirements', 'what data do I need', 'API requirements', or is describing data needs for a UI. MIT View frontend-to-backend-requirements geo-llmstxt SignedBy zubair-trabzada · original, unchanged Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site. MIT View geo-llmstxt github-actions-docs SignedBy xixu-me · original, unchanged Use when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows, artifacts, caching, secrets, OIDC, deployments, custom actions, or Actions Runner Controller, especially when they need official GitHub documentation, exact links, or docs-grounded YAML guidance. MIT View github-actions-docs goals-and-kpis SignedBy social-media-skills · original, unchanged Set social media goals and KPIs — measurable targets and north-star metrics that aren't vanity numbers. Use when someone wants to "set social media goals," "define our KPIs," "what should we be aiming for," "what's our north-star metric," "OKRs for social," or to turn vague ambitions ("grow our following," "go viral") into measurable targets. Builds a cascade: business goal -> SMART objective -> North Star KPI (one per channel by its win condition) -> supporting metrics, with benchmark-set targets and action thresholds. Uses the NORTH framework. Reads brand-profile + social-strategy first. It SETS the targets; analytics-and-reporting MEASURES against them. Targets come from real benchmarks (never fabricated baselines), KPIs must be controllable and non-vanity, and guardrails prevent gaming. Distinct from analytics-and-reporting (measures) and social-strategy (the whole plan). MIT View goals-and-kpis graphql-and-hidden-parameters SignedBy yaklang · original, unchanged GraphQL and hidden parameter testing playbook. Use when exploring introspection, batching, undocumented fields, hidden parameters, schema abuse, and GraphQL authorization gaps. MIT View graphql-and-hidden-parameters grepai-config-reference SignedBy yoanbernabeu · original, unchanged Complete configuration reference for GrepAI. Use this skill when you need to understand all available configuration options. MIT View grepai-config-reference grill-me SignedBy satya-janghu · original, unchanged Interview the user relentlessly to expand context and surface intent, constraints, hidden assumptions, and unstated alternatives. Use whenever the user invokes `/grill-me`, says "grill me", "interview me", "pressure-test this", "help me think through", or whenever the user's first message is more decision than task — across coding, business, marketing, personal branding, SOPs, systems thinking, process design, and tough decisions. MIT View grill-me grpo-rlvr-training SignedBy wshobson · original, unchanged Train reasoning and verifiable-task behavior with GRPO and reinforcement learning from verifiable rewards (RLVR). Use when task success is algorithmically checkable (math, code, tool calls, structured output), when designing GRPO reward functions, or when a GRPO run diverges or reward-hacks. MIT View grpo-rlvr-training hack SignedBy yaklang · original, unchanged Entry P0 primary router and operating doctrine for HackSkills. Use when the task involves web application testing, API security assessment, recon, vulnerability triage, exploit path planning, authorized pentest, code audit, source-leak mining, middleware audit, SOC triage, detection engineering, incident response, or choosing the right next category skill before any deep topic skill. Also use when the user mentions 安全工程师, 渗透测试, 红队, 蓝队, 代码审计, 源码泄露, SRC. Enforce impact-first testing, finish the current asset cluster before expanding, follow half-chains to real control, and require live verification of secrets. MIT View hack hardware-security SignedBy zhaoxuya520 · original, unchanged Use for authorized hardware and embedded interface security research including UART/JTAG discovery, debug pad triage, secure boot overview, and offline firmware extraction support. MIT View hardware-security hashtag-strategy SignedBy social-media-skills · original, unchanged Use to build a hashtag and discoverability strategy for social posts — the modern (2026) approach, not the outdated "30 hashtags to go viral" playbook. Run when the user says "hashtags," "what hashtags should I use," "how many hashtags," "hashtag strategy," "help me get discovered/reach," asks "do hashtags still work / are hashtags dead," or asks how to tag a post. Reads brand-profile and audience first. Sets the keyword/social-SEO layer first (caption, on-screen text, spoken audio) because that — plus engagement and the content itself — drives discovery far more than hashtags now; then picks a tight, relevant, per-platform hashtag set (respecting caps like Instagram's enforced 5-tag limit), favors niche/mid-tier tags over generic mega-tags, and designs branded/campaign hashtags for community and tracking. Rotates sets rather than copy-pasting one block, and hands placement/publishing to scheduling-and-queue. Sets honest expectations: hashtags categorize and aid search; they are not a reach hack. MIT View hashtag-strategy http2-specific-attacks SignedBy yaklang · original, unchanged HTTP/2 protocol-specific attack playbook. Use when the target supports HTTP/2 and you need to exploit binary framing, HPACK compression, h2c upgrade smuggling, pseudo-header injection, stream multiplexing abuse, or H2→H1 downgrade translation flaws. MIT View http2-specific-attacks idea-generation-and-ideation SignedBy social-media-skills · original, unchanged The idea-system craft — never run out of content ideas by running a system instead of waiting for inspiration. Use when someone is out of ideas, stares at a blank calendar, asks where good ideas come from, wants an idea bank/backlog, feels their AI-generated ideas sound like everyone else's, or thinks their niche is "boring." Uses the SPARK framework. Reads brand-profile + social-strategy + content-pillars + audience-research first. The audience is the idea engine (comments/DMs/FAQs clustered into themes); AI expands real signals, it doesn't discover them; systems beat muses; trends are a timing filter, not a source. The agent clusters/expands/scores; the HUMAN supplies proprietary signals and decides; WoopSocial publishes the content, not ideas. Never rewords competitor posts, invents audience questions, or fabricates probe results. Distinct from social-strategy/content-pillars, audience-research, cross-platform-repurposing/ content-recycling, and the format skills. MIT View idea-generation-and-ideation idor-broken-object-authorization SignedBy yaklang · original, unchanged IDOR and broken object authorization testing playbook. Use when requests expose object identifiers, tenant boundaries, writable fields, or missing object-level authorization checks. MIT View idor-broken-object-authorization image-prompt SignedBy social-media-skills · original, unchanged Use as the foundation and router for any image a post needs — turn a social need into a clear image brief, describe it with model-agnostic prompt craft, and route to the right tool. Run when the user says "I need a visual/image for this post," "what image should I use," "make a graphic," "help me prompt an image," or is unsure which image tool/model to use. Reads brand-profile for the visual brand. Teaches the image brief, the universal anatomy of a strong prompt in natural language, and a tool router (typographic -> ideogram/nano-banana; photoreal -> nano-banana/flux; surreal -> Midjourney; editing -> nano-banana/flux; vector -> Recraft; video -> veo-3). Includes a "should this even be AI-generated?" gate (a real photo, screenshot, or chart often beats generic AI), accessibility, and honest scope (disclose AI, never real identifiable people or copyrighted IP, verify text/data). Hands off to the tool-specific mini-skills; WoopSocial publishes via Media and doesn't generate images. MIT View image-prompt image-to-ui SignedBy uizze · original, unchanged Recreate an image, screenshot, or mockup as a 1:1 UI implementation. Match the reference rather than redesigning it, then render and compare the result to correct visible differences. MIT View image-to-ui infographic-and-data-viz SignedBy social-media-skills · original, unchanged The craft of turning real data into honest, scannable, shareable infographics and charts. Use when someone wants to visualize data, make an infographic, build a chart/graph, turn a finding or stat into a visual, or fix a chart that's confusing or misleading. A great data viz makes one insight land in 3 seconds. Uses the CHART framework (chart choice, headline takeaway, honest scale, reduce to signal, tag source + accessibility). Reads brand-profile + design-and-templates first and pulls real data from data-and-original-research / analytics-and-reporting. The agent designs the spec; a design/chart tool renders it; the human approves; WoopSocial publishes the image (it does not generate media). NEVER distorts scales or fabricates a data point/source; cites source + date; accessibility required. Distinct from design-and-templates (brand design), quote-cards-and-text-graphics (a lone quote/number), data-and-original-research (originates the data), and analytics-and-reporting. MIT View infographic-and-data-viz insecure-source-code-management SignedBy yaklang · original, unchanged Source control and artifact exposure (.git, .svn, .hg, backups, .env). Use when recon finds VCS paths, 403 on hidden dirs, or backup/config leaks during authorized testing. MIT View insecure-source-code-management instagram-reels-publishing SignedBy social-media-skills · original, unchanged The Instagram Reels publish-mechanics skill -- distinct from reels-script (the script), instagram-seo (the keyword caption), and platform-specs-and-validation (cross-platform validation). Use when someone has a finished Reel and needs to publish it correctly: specs, cover, safe zone, publish settings. It gets the Reel OUT the way Instagram displays it: 9:16 spec-clean video, the safe zone that survives the feed and profile-grid crops, a custom grid-safe cover (chosen before publish, can't edit after), the keyword caption, and audio. Uses the FRAME framework. Reads brand-profile + the Reel asset first. The agent specs the publish settings, cover brief, and specs/safe-zone checklist, and advises audio/tags. WoopSocial publishes postType REEL + video + caption + cover on a schedule; trending audio, Share-to-Feed, tags, and Reel Insights stay native/in-app; the video/cover come from other tools. Remove other-platform watermarks; metrics never fabricated. MIT View instagram-reels-publishing instagram-seo SignedBy social-media-skills · original, unchanged The Instagram SEO / keyword-search skill -- IG-specific search depth, distinct from the cross-cutting social-seo. Use when someone wants an Instagram post/Reel to rank in search, needs IG keyword research, or wants a searchable caption/profile. Instagram shifted from hashtag-based discovery to keyword-based search (hashtags deprioritized to 3-5 topic labels). Search runs semantic analysis -> metadata matching -> visual recognition (checks alt text + visual MATCH the caption). Uses the MATCH framework. Reads brand-profile + the post's topic first. The agent researches the keyword cluster (never fabricates volume), writes the search-first caption (primary keyword first, no stuffing), specs on-screen text + spoken keyword, and advises profile fields/alt text. WoopSocial publishes the caption; profile fields, alt text, and IG Search/Insights stay native. No keyword stuffing; caption must match the visual. Distinct from social-seo, pinterest-seo, and hashtag-strategy. MIT View instagram-seo integration-error-observability SignedBy samber · original, unchanged Design how a platform surfaces integration failures to the external developers and partners who built against it - per-integration request/event/delivery logs with replay, correlation IDs that survive from response header to support ticket, error-rate aggregation per API key or app split by 4xx/5xx/429, proactive partner notification with cooldowns against alert fatigue, and a provider-side fleet view of which integrations are breaking. Use whenever the user mentions a developer-facing error dashboard, exposing request logs to integrators, alerting partners about broken integrations, or cutting integration support tickets - even if they never say "observability". Do NOT use for platform-wide incident comms - use samber/developer-platform-skills@api-status-communication instead. MIT View integration-error-observability integration-listing-optimization SignedBy samber · original, unchanged Optimize a B2B SaaS vendor's own listing on a third-party app marketplace - Salesforce AppExchange, HubSpot, Atlassian Marketplace, Shopify App Store, Slack, or comparable directories. Covers the view-to-install funnel, keyword placement in title and tagline, screenshot and demo-video ordering, category choice, compliant review-velocity programs (incentivized reviews are banned everywhere), badge pursuit ranked by confirmed ranking effect, and defending rank against listing decay. Use whenever the user mentions AppExchange, marketplace listing conversion, marketplace search rank, app installs, or app reviews - even if they never say "listing optimization". Do NOT use for the operator's own rulebook - use samber/developer-platform-skills@app-marketplace-listing-standards instead. MIT View integration-listing-optimization integration-partnership-strategy SignedBy samber · original, unchanged Select which technology partners a B2B SaaS vendor integrates with and how deep each partnership goes - demand-data partner prioritization (deal-attached revenue, retention lift, competitive necessity), the referral-to-OEM depth ladder with graduation gates, joint-roadmap and co-build governance, certification-program joins with budgeted renewals, sourced-vs-influenced pipeline attribution, and where the technology-partnerships function reports. Use whenever the user mentions integration partners, ISV alliances, technology partnerships, partner tiers, certification programs, or partner-pipeline attribution - even if they never say "partnership strategy". Strategy layer only. Do NOT use for ETL-platform listings - use samber/developer-platform-skills@etl-connector-strategy instead. MIT View integration-partnership-strategy interactive-content SignedBy social-media-skills · original, unchanged The participation content format — polls, quizzes, Q&A / scoped AMAs, this-or-that, emoji sliders, question boxes, caption-this, Add-Yours, and challenges. Use when someone wants interactive posts, Story stickers, a poll/quiz/AMA, a challenge or contest, or to turn passive scrollers into participants. Low-friction taps are high-value algorithmic signals, and every interaction doubles as audience research. Uses the REACT framework. Reads brand-profile + audience-research + voice-builder first. The agent designs the mechanic, questions, copy, and the close-the-loop plan; the HUMAN adds native interactive elements in-app — stickers and live AMAs are NATIVE-ONLY (WoopSocial cannot attach stickers or read results); WoopSocial publishes the feed-post versions. NEVER fabricates or rigs results or fakes participation; consent before sharing anyone's answer. Distinct from community-management, reply-and-comment-writer, livestream-and-realtime, and ugc-and-influencer. MIT View interactive-content interactive-input SignedBy sugarforever · original, unchanged Enables rich interactive UI components in chat responses. When presenting questions that require structured input (multiple choice, true/false, forms), embed interactive blocks that compatible clients render as native UI elements. Use when user asks for quizzes, exercises, surveys, or any structured input scenario. MIT View interactive-input ios-pentesting-tricks SignedBy yaklang · original, unchanged iOS pentesting playbook. Use when testing iOS applications for keychain extraction, URL scheme hijacking, Universal Links exploitation, runtime manipulation, binary protection analysis, data storage issues, and transport security bypass during authorized mobile security assessments. MIT View ios-pentesting-tricks jndi-injection SignedBy yaklang · original, unchanged JNDI injection playbook. Use when Java applications perform JNDI lookups with attacker-controlled names, especially via Log4j2, Spring, or any code path reaching InitialContext.lookup(). MIT View jndi-injection js-reverse SignedBy zhaoxuya520 · original, unchanged 在使用 js-reverse-mcp 做前端 JavaScript 逆向时使用,适用于签名链路定位、页面观察取证、运行时采样、本地补环境复现与证据化输出。优先适配当前环境里的 js-reverse_* 工具,需要更强的浏览器/CDP/Hook 面时联动 jshookmcp。 MIT View js-reverse kanchi-dividend-us-tax-accounting SignedBy tradermonty · original, unchanged Provide US dividend tax and account-location workflow for Kanchi-style income portfolios. Use when users ask about qualified vs ordinary dividends, 1099-DIV interpretation, REIT/BDC distribution treatment, holding-period checks, or taxable-vs-IRA account placement decisions for dividend assets. MIT View kanchi-dividend-us-tax-accounting lead-magnets-and-funnels SignedBy social-media-skills · original, unchanged Lead magnets and funnels — design offers that turn social traffic into subscribers, leads, and customers. Use when someone wants to "create a lead magnet," "build a funnel," "design a freebie/opt-in," "make a quiz/calculator/template to grow my list," or turn social traffic into qualified leads and customers. Designs the magnet the capture paths deliver PLUS the whole social->capture->nurture funnel, using the MAGNET framework. Reads brand-profile + goals-and-kpis first. WoopSocial has no landing/form/email/quiz builder: the agent designs the magnet + funnel and drafts the nurture and promo posts; WoopSocial publishes the promo posts; capture/delivery/nurture run in external tools; metrics from those + GA4, never fabricated; no dark patterns. Distinct from link-in-bio-and-traffic / social-selling-and-dm (the capture paths) and email-and-newsletter (the owned channel). MIT View lead-magnets-and-funnels link-in-bio-and-traffic SignedBy social-media-skills · original, unchanged Link-in-bio and traffic strategy — convert social reach into clicks, subscribers, and owned audience. Use when someone wants to "drive traffic from social," "optimize my link in bio," "get more clicks," "turn followers into email subscribers / leads / sales," "where do I put my link," or to convert reach into an owned audience. Turns rented reach into clicks and an OWNED audience: one clear action (not a link-dump), capture-before-sell, correct link placement per platform (in-post links are suppressed on X/LinkedIn/Facebook), and branded short links + UTM tracking. Uses the CLICK framework. Reads brand-profile + goals-and-kpis first. WoopSocial publishes the driving posts and places links where the API allows; the bio hub / landing page / email tool are external (3rd-party + human); clicks/conversions are read from those + GA4, never fabricated. Distinct from profile-optimization, social-selling-and-dm, email-and-newsletter, and lead-magnets-and-funnels. MIT View link-in-bio-and-traffic lora-qlora-recipes SignedBy wshobson · original, unchanged Configure LoRA and QLoRA supervised fine-tuning with current best-practice hyperparameters. Use when writing or reviewing a LoRA/QLoRA training configuration, choosing rank/alpha/target modules, or deciding between LoRA, QLoRA, and full fine-tuning. MIT View lora-qlora-recipes malware-analysis SignedBy zhaoxuya520 · original, unchanged Use when analyzing suspected malware through static, dynamic, and behavioral techniques, including IOC extraction, YARA or Sigma rules, sandboxing, and anti-analysis behavior. MIT View malware-analysis meme-and-culture SignedBy social-media-skills · original, unchanged The cultural-fluency + meme-craft skill -- participate in internet culture and meme formats as a brand without being cringe, tone-deaf, or legally exposed. Use when someone wants to make a meme, join a cultural moment, build a meme/humor pillar, or decide whether to jump on a format. Meme marketing done wrong is worse than none. Uses the VIBES framework. Reads brand-profile + the meme/moment first. Two hard gates: brand-fit (would it work without your logo?) and safety + IP (never tragedies/divisive/ appropriation/punching-down; original visuals only, no copyrighted characters or celebrity likeness). The agent advises fit/safety/IP and writes the copy/concept; the human/creator makes the asset and adds the final wit pass; WoopSocial publishes/schedules (reactive ones often post in the moment). Sitting a meme out is valid; never fabricates relevance or virality. Distinct from trend-jacking, image-prompt/design-and-templates, community-management, and ai-music-and-sound. MIT View meme-and-culture meme-factory SignedBy softaworks · original, unchanged Generate memes using the memegen.link API. Use when users request memes, want to add humor to content, or need visual aids for social media. Supports 100+ popular templates with custom text and styling. MIT View meme-factory mo-auth SignedBy mowenxd · original, unchanged 墨问 Auth 认证:墨问 API Key 的配置与更新、获取当前的配置信息、获取 API Key 对应的账户,在墨问平台上的 Profile(用户信息)。当用户操作 API Key 时触发。 MIT View mo-auth mobile-reverse SignedBy zhaoxuya520 · original, unchanged Use for authorized Android or iOS application reverse engineering and security testing, including APK or IPA analysis, runtime instrumentation, SSL pinning, and platform protection checks. MIT View mobile-reverse nano-banana SignedBy social-media-skills · original, unchanged Use to write great prompts for Nano Banana (Google's Gemini image model: Nano Banana Pro = Gemini 3 Pro Image) to generate or edit images for social media — the image-prompt-craft mini-skill. Run when the user wants a nano-banana / Gemini image prompt, an AI image for a post (quote graphic, carousel slide, thumbnail, infographic, product shot, ad creative), or conversational image editing. Reads brand-profile for brand colours/style. Strengths: best-in-class legible in-image text (route typography/layout-led design to ideogram), multi-image consistency, conversational editing, and Google's photoreal lane (Imagen deprecated); surreal art stays Midjourney's. Teaches prompt anatomy, the text-first approach, reference-image consistency, and per-platform aspect ratios. Honest: SynthID watermark + AI disclosure; never real identifiable people or copyrighted characters/logos; verify spelling/data. The API/connection and WoopSocial upload flow live in tools/integrations/nano-banana.md. MIT View nano-banana nansen-trading SignedBy nansen-ai · original, unchanged Execute DEX swaps on Solana or Base (including cross-chain bridges) and Hyperliquid perpetual trades. Use when buying or selling a token, getting a swap quote, executing a trade, or opening/closing/managing a perp position. MIT View nansen-trading network-security-groups SignedBy aj-geddes · original, unchanged Configure network security groups and firewall rules to control inbound/outbound traffic and implement network segmentation.
MIT View network-security-groups nextjs-app-router-fundamentals SignedBy wsimmonds · original, unchanged Guide for working with Next.js App Router (Next.js 13+). Use when migrating from Pages Router to App Router, creating layouts, implementing routing, handling metadata, or building Next.js 13+ applications. Activates for App Router migration, layout creation, routing patterns, or Next.js 13+ development tasks. MIT View nextjs-app-router-fundamentals note-it SignedBy smallnest · original, unchanged Capture implementation notes after code implementation and review/fix. Records design decisions, deviations, tradeoffs, and open questions to docs/issue#XXXX.html. Triggers on: /note-it, 记录笔记, implementation notes. MIT View note-it oauth-oidc-misconfiguration SignedBy yaklang · original, unchanged OAuth and OIDC misconfiguration testing playbook. Use when reviewing redirect URI handling, state and nonce validation, PKCE, token audience, callback binding, and identity-provider trust flaws. MIT View oauth-oidc-misconfiguration openapi-to-typescript SignedBy softaworks · original, unchanged Converts OpenAPI 3.0 JSON/YAML to TypeScript interfaces and type guards. This skill should be used when the user asks to generate types from OpenAPI, convert schema to TS, create API interfaces, or generate TypeScript types from an API specification. MIT View openapi-to-typescript open-source-company-strategy SignedBy samber · original, unchanged Decides what a company open-sources and what stays proprietary, names the strategic motive for each side of the line, says who owns the decision, and states what the company commits never to close. Use whenever someone asks "should we open source this?", "what should we open source", "where do we draw the open-core line", "which features stay paid", "who signs off on open sourcing this", or wants a company-level open source strategy rather than a plan for one project - even if they frame it as a licensing question. Produces an asset-by-asset open/closed verdict, a value-capture and irreversibility check, a public non-reversal commitment and a re-evaluation trigger. Not license selection - use samber/developer-relations-skills@oss-license-strategy. MIT View open-source-company-strategy opensource-guide-coach SignedBy xixu-me · original, unchanged Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption. MIT View opensource-guide-coach oss-contributor-onboarding SignedBy samber · original, unchanged Designs and verifies the path a stranger walks to their first merged contribution on an open-source project - the CONTRIBUTING file, the good-first-issue queue, a clone-to-passing-tests command that works cold, and the first-pull-request review and recognition loop, scored against a blocking-plus-weighted rubric. Use whenever someone says "nobody contributes to my project", "write a CONTRIBUTING.md", "our good first issues get no takers", "first-time contributors disappear", "contributor onboarding", "first pull request experience", or "how do we get more open-source contributors" - even if they only complain about a lonely repo. Not triage-system design - use samber/developer-relations-skills@oss-issue-triage. Not governance or CLA choice. MIT View oss-contributor-onboarding oss-distribution-strategy SignedBy samber · original, unchanged Designs an open-source project's ongoing distribution mix after the launch window - registry metadata, code-host discovery surfaces, curated lists, downstream packaging, extension and connector marketplaces, the release stream, dependency-graph position, creator seeding, and procurement trust signals - ranked against real maintainer capacity. Use whenever a maintainer asks how people will keep finding the project, which registries or awesome lists to target, why adoption flattened after launch, how often to release for visibility, or how to spend limited maintainer hours on distribution - even if they only say nobody is using it. Not the launch itself - use samber/developer-relations-skills@oss-launch. Not the build-in-public practice. MIT View oss-distribution-strategy oss-issue-triage SignedBy samber · original, unchanged Designs an issue and pull-request triage system a maintainer team can sustain - response targets sized against real capacity, the label taxonomy, intake cuts through structured forms and off-tracker routing, a separate security-report path, triage duty assignment, and the closing, staleness and volume-gating policy. Use whenever someone says "our issue tracker is out of control", "design an issue triage process", "set up labels for our repo", "we have 900 open issues", "should we run a stale bot", "PR backlog nobody reviews", "triage rotation", or "we are drowning in AI-generated reports" - even if they only say maintenance is overwhelming. Not good-first-issue curation - use samber/developer-relations-skills@oss-contributor-onboarding. MIT View oss-issue-triage oss-launch SignedBy samber · original, unchanged Plans and runs an open-source project launch end to end - name and license clearance, the readiness gate, positioning and one-liner, channel sequencing, the launch-day war room, star-velocity and GitHub Trending mechanics, and post-launch measurement. Use whenever someone is about to release, announce, open-source or "Show HN" a repository, asks how to reach GitHub Trending, wants the first real users or stars for a new library, is planning a Product Hunt post or a multi-day launch week, or asks why a launch fell flat (even if they only say they are pushing a repo public). Covers individual-developer and company adoption. Not ongoing distribution afterwards - use samber/developer-relations-skills@oss-distribution-strategy instead. MIT View oss-launch oss-sponsors-brand-strategy SignedBy samber · original, unchanged Builds a company's open-source sponsorship portfolio - which projects and maintainers to fund, through which allocation model, at what amount each, and how to prove it worked. Use whenever a company, OSPO, DevRel lead or engineering leader asks which open-source projects to sponsor, how much to budget for open-source funding, whether sponsoring maintainers is worth it, how to run an employee-nominated FOSS fund, how to fund dependencies at scale, how to pick a sponsorship tier on a maintainer's ladder, or how to measure the return on money paid to maintainers - even if they only say they want to give back. Not the maintainer side of raising sponsorship - use samber/developer-relations-skills@oss-sponsors-fundraising. Not event sponsorship. MIT View oss-sponsors-brand-strategy parallel-agents SignedBy sentimony · original, unchanged You MUST use this when several units of work might run concurrently through agents - independent investigations, specialist reviews, repository analyses, or plan tasks that look unrelated - covering whether they are genuinely independent, which mutable state needs isolation, how wide the wave should be, and how results are reconciled before integration. MIT View parallel-agents partner-app-onboarding SignedBy samber · original, unchanged Design the partner-developer onboarding journey on a B2B SaaS platform - from partner signup through dev-account and sandbox provisioning, docs, education and certification posture, and support channels, to the first submitted app. Use whenever the user mentions partner developer onboarding, developer program entry, self-service vs application-gated registration, sandbox tenancy for partners, certification gating submission, partner support channels, or time-to-first-submitted-app - even if they never say "onboarding". Journey design only. Do NOT use for review-gate mechanics (samber/developer-platform-skills@app-marketplace-review) or sandbox isolation architecture (samber/developer-platform-skills@api-test-mode-design). MIT View partner-app-onboarding patch-diff-exploit SignedBy zhaoxuya520 · original, unchanged N-day 补丁差分到利用。从厂商发布的补丁里反推漏洞点、写 PoC、做成可用的攻击模块。
适用场景:已知 CVE 编号但只有补丁没有 PoC、SRC/红队需要打击未及时更新的资产、N-day 武器化、Patch Tuesday 跟进。
核心方法:拿 before/after 二进制 → 对齐符号 → 二进制 diff → 看新增的安全检查反推 bug class → 写 PoC 触发漏洞。
触发关键词:N-day、Nday、补丁差分、patch diff、patch tuesday、1day、binary diff 漏洞、bindiff 利用、ghidriff、Diaphora、补丁分析、CVE 复现、漏洞还原、补丁反推、N-day 武器化。
MIT View patch-diff-exploit performance-regression-debugging SignedBy aj-geddes · original, unchanged Identify and debug performance regressions from code changes. Use comparison and profiling to locate what degraded performance and restore baseline metrics.
MIT View performance-regression-debugging pinterest-pin-design SignedBy social-media-skills · original, unchanged The Pinterest pin design skill -- the visual half that pairs with pinterest-seo's keyword layer. Use when someone wants to design a pin, a Pinterest pin image, a pin text overlay, fresh pin variations for an existing URL, or board covers. Designs and briefs the 2:3 (1000x1500) vertical pin: one focal point, a keyword text overlay readable at feed size, brand-consistent template, safe zones, and 3-5 visually distinct FRESH designs per destination URL. Uses the SAVED framework. Reads brand-profile + the destination + the pinterest-seo keyword first. A HUMAN or an image/design tool (ideogram/canva/nano-banana/a designer) creates the final raster; WoopSocial publishes the finished pin image + title + description + board + link. No misleading pins, no repin-as-fresh dupes, engagement never fabricated. Distinct from pinterest-seo (the keyword layer -- they PAIR), pinterest-growth (the strategy), design-and-templates (the template system), and ideogram/canva (render the raster this briefs). MIT View pinterest-pin-design platform-specs-and-validation SignedBy social-media-skills · original, unchanged Platform specs and publish validation — per-platform requirements and the validate-before-publish step for multi-platform fan-out. Use when fanning a post out to multiple platforms, when a post is getting rejected, when mapping per-platform postType/required fields, or to run the validate-before-publish step. Encodes the per-platform postType enums, required-field matrices, and media rules from the OpenAPI spec, and runs POST /posts/validate so a post lands correctly on every target. Uses the CHECK framework. The keystone the per-platform format skills point to. WoopSocial validates + publishes atomically and has no update endpoint; the agent maps fields and fixes spec violations, but human-judgment calls (disclosure truthfulness, privacy intent) stay with the person; metrics never fabricated. Distinct from the per-platform format skills (one platform's content) and scheduling-and-queue (timing). MIT View platform-specs-and-validation pptx-deck-context SignedBy wshobson · original, unchanged Use when preparing the narrative, sources, and design context for a new editable PPTX deck. MIT View pptx-deck-context pptx-slide-specification SignedBy wshobson · original, unchanged Use when authoring or repairing a coordinate-explicit JSON specification for an editable PPTX deck. MIT View pptx-slide-specification pptx-visual-assets SignedBy wshobson · original, unchanged Use when selecting and placing approved supporting icons, images, SVGs, diagrams, or infographics in an editable PPTX deck. MIT View pptx-visual-assets professional-communication SignedBy softaworks · original, unchanged Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication. MIT View professional-communication Page 1 of 14 Next Give your agent the ones it needs. Start free with five active skills for automatic loading and manual access to the whole library. Upgrade for automatic loading across the library.
Create a free key