Implement an accepted change in bounded dependency-ordered increments when the user requests implementation and the scope benefits from multiple coherent slices; do not trigger merely because work touches multiple files, changes behavior, or is over an arbitrary line count.
The English summary is being prepared. Showing the original description.
Rosetears520/aili-workflows☆ 2Updated Sep 27, 2026
Build or modify production UI components, layouts, client state, responsive behavior, accessibility, or UX inside an app when that frontend surface is the primary deliverable; do not trigger for rich campaign/media pages, backend integration, every user-facing text change, delegated browser QA, or review alone.
The English summary is being prepared. Showing the original description.
Rosetears520/aili-workflows☆ 2Updated Sep 27, 2026
Creates load and performance tests with k6, Artillery, or autocannon to validate system behavior under stress. Use when users request "load testing", "performance testing", "stress testing", "k6 setup", or "benchmark API".
The English summary is being prepared. Showing the original description.
sathishssj3/Stereix-Engine☆ 2Updated Oct 4, 2026
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.
The English summary is being prepared. Showing the original description.
sathishssj3/Stereix-Engine☆ 2Updated Oct 4, 2026
The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2 experimental), which is a substantial rewrite. Use this v1 install name only if you need exact backward compatibility.
The English summary is being prepared. Showing the original description.
sathishssj3/Stereix-Engine☆ 2Updated Oct 4, 2026
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
The English summary is being prepared. Showing the original description.
sathishssj3/Stereix-Engine☆ 2Updated Oct 4, 2026
Use when a working Spark implementation should be simplified without changing its observed behavior, ownership, compatibility, or public contract.
The English summary is being prepared. Showing the original description.
zendev-lab/spark☆ 2Updated Oct 19, 2026
Discover a single-page-app's hidden backend API from its public JS bundle, then test that API for broken access control / missing authentication. One of the highest-yield web plays in modern recon — SPAs ship their entire backend route map to the browser, and the API behind them is frequently missing the auth middleware the login page implies. Built from an authorized engagement where this play found an unauthenticated financial API that an ASM scan reporting hundreds of 'Criticals' completely missed. Use whenever a target serves a JS-heavy SPA (React/Vue/Angular/Next), an 'app'/'console'/'dashboard'/'portal' subdomain, or any `*api*` host shows up in recon. Leaked build artifacts (source maps / .env / .git / asset-manifest) are owned by hunt-source-leak; API version-inventory and behavioral diffing by hunt-shadow-api; this skill owns mapping a live SPA's backend routes from its JS bundle and testing them for broken access control / missing auth.
The English summary is being prepared. Showing the original description.
ajtazer/heckit☆ 2Updated Oct 7, 2026
EDR evasion offensive checklist: hook unhooking (user/kernel), direct syscalls, PPID spoofing, process injection variants, AMSI bypass, ETW patching, memory encryption, and behavior-based evasion. Use when planning EDR bypass during red team engagements or researching AV/EDR evasion techniques.
The English summary is being prepared. Showing the original description.
ajtazer/heckit☆ 2Updated Oct 7, 2026
NTLM info disclosure is a Medium-severity finding when chained to context — the leak itself is intentional protocol behavior (RFC-compliant NTLMSSP challenge), but on internet-exposed enterprise infrastructure it provides exact reconnaissance for the next stage of an attack. Highest-value targets:
The English summary is being prepared. Showing the original description.
ajtazer/heckit☆ 2Updated Oct 7, 2026
Connect a Feishu (Lark) bot to Clawdbot via WebSocket long-connection. No public server, domain, or ngrok required. Use when setting up Feishu/Lark as a messaging channel, troubleshooting the Feishu bridge, or managing the bridge service (start/stop/logs). Covers bot creation on Feishu Open Platform, credential setup, bridge startup, macOS launchd auto-restart, and group chat behavior tuning.
The English summary is being prepared. Showing the original description.
danstrem2/clawdbot-skill-master-pack☆ 2Updated Feb 1, 2026
Mandatory skills, conventions, and behavioral rules for Avalonia UI development using the Zafiro toolkit.
The English summary is being prepared. Showing the original description.
danstrem2/clawdbot-skill-master-pack☆ 2Updated Feb 1, 2026
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
The English summary is being prepared. Showing the original description.
danstrem2/clawdbot-skill-master-pack☆ 2Updated Feb 1, 2026
Testing and benchmarking LLM agents including behavioral testing, capability assessment, reliability metrics, and production monitoring—where even top agents achieve less than 50% on real-world benchmarks Use when: agent testing, agent evaluation, benchmark agents, agent reliability, test agent.
The English summary is being prepared. Showing the original description.
danstrem2/clawdbot-skill-master-pack☆ 2Updated Feb 1, 2026
Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.
The English summary is being prepared. Showing the original description.
johnalbertini14-glitch/openclaw-skills☆ 2Updated Feb 26, 2026
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
The English summary is being prepared. Showing the original description.
Scoheart/agentskills☆ 2Updated Aug 4, 2026
Multi-dimensional lead qualification scoring. Evaluates leads against BANT criteria, firmographic fit, behavioral signals, and intent indicators. Outputs qualified/disqualified verdict with detailed reasoning.
The English summary is being prepared. Showing the original description.
ekatasingh1107/b2b-gtm-skills☆ 2Updated Apr 12, 2026
Add automatic CI/CD environment detection using ci-info package. Generic pattern for any CLI tool that needs to adapt behavior (prompts, output, integrations) based on whether it's running in CI.
The English summary is being prepared. Showing the original description.
krafteq/infraglue☆ 2Updated Jul 8, 2026
Add new capabilities or modify NanoClaw behavior. Use when user wants to add channels (Telegram, Slack, email input), change triggers, add integrations, modify the router, or make any other customizations. This is an interactive skill that asks questions to understand what the user wants.
The English summary is being prepared. Showing the original description.
nanocoai/nanoclaw-gmail☆ 2Updated Apr 3, 2026
Gates whether a new test should exist and forces it to be efficient, protecting CI from low-value test bloat. Use before any change to what a pytest, Jest, or Playwright test asserts or sets up, down to one fixture or one assertion added to an existing block. Front-loads the value bar (every test must catch a realistic regression no existing test already catches; extend the nearest existing test before writing a new standalone one; test behavior through the public interface, not implementation details; collapse near-duplicates into parameterized cases) and the efficiency bar (deterministic, isolated, fast; pick the cheapest test level; Django TestCase over TransactionTestCase; no sleeps, no real network; no time bombs from absolute dates left to age against the real clock; no database a test never uses). Includes a "don't write it" decision tree. For fixing an existing flaky test use `/fixing-flaky-tests`; after this gate says a Playwright test is warranted, use `/playwright-test` for mechanics.
The English summary is being prepared. Showing the original description.
amplifthq/opentag☆ 0Updated Oct 14, 2026