Internal downstream skill for ctf-sandbox-orchestrator.
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule"…
Performs comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and platform-specific…
Create and manage sandboxed WASM agents for isolated code execution
Parses API Gateway access logs (AWS API Gateway, Kong, Nginx) to detect
Systematically evaluate cyber-campaign evidence to attribute an operation to a threat actor, using the Diamond Model and Analysis of…
Cancel active UltraQA cycling workflow
Understand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere.
Migrate authentication systems with credential migration, OAuth2/OIDC setup, and identity provider integration
Deploy Microsoft Sentinel as a cloud-native SIEM/SOAR by configuring multi-cloud data connectors (AWS, Azure, GCP), writing KQL detection…
Multi-language code coverage analysis, reporting, and quality gate enforcement
Internal downstream skill for ctf-sandbox-orchestrator.
Internal downstream skill for ctf-sandbox-orchestrator.
Runs a budget-aware agent-assisted engineering health audit for instruction/config drift, hooks/MCP, verifier surfaces, and AI…
Migrate an MSTest v3 test project to MSTest v4.
Scaffold, write, debug, and enhance enterprise-grade Playwright E2E tests in Java using Page Object Model, JUnit 5, Allure reporting, and…
Strict RED-GREEN-REFACTOR cycle enforcement.
Automate Abuselpdb tasks via Rube MCP (Composio).
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
Lists available make commands for Streamlit development.
Security & Testing agent skills on mcprush sequence security work correctly — rotate the credential before rewriting the history, sketch the trust boundary before building the feature. The kinds are workflow, expertise, output format, voice & style and guardrail, and the one a skill belongs to, where its author declared it, is the fastest way to guess what it will do to your prompt.
What to look at before installing one is what it costs in context and what it takes away: a guardrail that refuses an action and a voice that rewrites a sentence are both skills, and only one of them will stop the agent doing something. Every skill here says what it costs in context, which kind it is where its author declared one, what it needs beside it to work and the licence it is published under, next to the publisher it came from and whether that publisher has been verified. The filters on the left narrow it further and the sort at the top decides what comes first.
A skill is not connected to anything: there is no endpoint to authorise and nothing routed through the gateway. Installing one drops a folder of instructions into the client’s own skill folder, and uninstalling it is deleting that folder. The exact line for each client is on the skill’s own page, because it differs by client rather than by skill.