End-to-end methodology for reproducing AND patching publicly disclosed, already-fixed vulnerabilities: sourcing the advisory and the fix commit, reading the patch diff, rebuilding a pinned offline lab, building a vulnerable-vs-patched contrast harness with proper controls, minimizing the trigger, designing and validating the fix, and writing it up as a blog post or whitepaper. Use this skill whenever the user wants to reproduce, demonstrate, understand, teach, or write about a known vulnerability or security incident: "reproduce this CVE", "build a repro for", "how did EchoLeak / Log4Shell / the postmark-mcp package actually work", "show me how this exploit worked", "write a blog post about this vulnerability", "set up a lab for CVE-XXXX", "pull the NVD/CVE/OSV details", or "make a PoC I can publish". Use it just as eagerly for the patching half: "how should this be fixed", "is this patch correct", "what would have caught this", "review this security fix", "write a regression test for this CVE", "how do I backport this", or "what's the right fix for this bug class" - even when the user never says the word "reproduce". Reach for it on vague asks like "help me understand this security advisory", "I want to write about this incident", or "can we test whether we were vulnerable" when a disclosed vulnerability is in play. This skill only handles ALREADY-PATCHED, publicly disclosed issues and refuses zero-day discovery, live targets, and weaponization.
日本語の概要は準備中です。原文の説明を表示しています。
Leanmcp/gateway-skills☆ 2,1102026年10月8日 更新
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
日本語の概要は準備中です。原文の説明を表示しています。
MemTensor/memmy-agent☆ 2,1072026年10月16日 更新
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal hold. Use this to configure a tenant, tighten sharing, investigate a mail delivery or phishing problem, or work out who can see a file and why.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Buys well — specifying need, running competitive sourcing, negotiating, and category strategy before a contract exists. Use this to run an RFP or vendor selection, negotiate a purchase, consolidate spend across a category, decide between single and multiple suppliers, or bring uncontrolled spending under management.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get control of sprawling SaaS, cut a cloud bill, work out who owns an application nobody admits to buying, or decide what corporate workloads belong in cloud at all.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Identifies which regulations apply and builds the program that keeps you inside them — obligation mapping, controls, monitoring, and responding to regulators. Use this to work out what applies to your business, stand up a compliance program, prepare for a regulatory exam or certification, respond to a finding, or assess exposure before entering a new market.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.
日本語の概要は準備中です。原文の説明を表示しています。
cbrock84/headcount☆ 2,0632026年9月18日 更新
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
日本語の概要は準備中です。原文の説明を表示しています。
backnotprop/pstack☆ 2,0212026年10月15日 更新
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
日本語の概要は準備中です。原文の説明を表示しています。
backnotprop/pstack☆ 2,0212026年10月15日 更新
Configure Benny and prepare its triage and repro automations. Use when installing Benny or changing its Slack, tracker, repository, routing, control, model, or budget settings.
日本語の概要は準備中です。原文の説明を表示しています。
backnotprop/pstack☆ 2,0212026年10月15日 更新
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
日本語の概要は準備中です。原文の説明を表示しています。
backnotprop/pstack☆ 2,0212026年10月15日 更新
Control deep thinking mode. Default enabled. For very simple tasks (simple reminders, greetings, quick queries), can temporarily disable to speed up response. Auto-restores to enabled after completion.
日本語の概要は準備中です。原文の説明を表示しています。
openakita/openakita☆ 1,9992026年9月24日 更新
Control desktop software (GIMP, Blender, LibreOffice, etc.) through CLI-Anything generated command-line interfaces. Calls real application backends — much more reliable than GUI automation via desktop_* tools.
日本語の概要は準備中です。原文の説明を表示しています。
openakita/openakita☆ 1,9992026年9月24日 更新
NetEase Cloud Music skill for searching songs, managing playlists, getting personalized recommendations, and controlling playback via ncm-cli. Use when user wants to search music, play songs, manage playlists, or get music recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
openakita/openakita☆ 1,9992026年9月24日 更新
Process CRISPR screening data to identify essential genes and hit candidates. Performs quality control, statistical analysis (RRA), and hit calling for pooled CRISPR screens including viability screens and drug resistance/sensitivity studies.
日本語の概要は準備中です。原文の説明を表示しています。
aipoch/medical-research-skills☆ 1,9652026年9月17日 更新
Generate forest plots for meta-analysis of continuous data. Input a CSV file containing study names, means, standard deviations, and sample sizes for experimental and control groups. Output forest plot PNG and data table CSV.
日本語の概要は準備中です。原文の説明を表示しています。
aipoch/medical-research-skills☆ 1,9652026年9月17日 更新