Loading...
Loading...
Found 4,123 Skills
LaTeX Injection is a type of injection attack where malicious content is injected into LaTeX documents. LaTeX is widely used for document preparation and typesetting, particularly in academia, for producing high-quality scientific and mathematical documents. Due to its powerful scripting capabilities, LaTeX can be exploited by attackers to execute arbitrary commands if proper safeguards are not...
Sign-in, sessions, bearer tokens, API keys and permissions in a NestJS application with the first-party @nestjs/authentication and @nestjs/authorization packages - timing-safe password checks, a global guard with @Public(), policies with @Can(), and what to do when a task fixes the JWT secret or token format. Use when adding or changing authentication or authorization in a NestJS application.
Comprehensive pull request review using specialized agents
SQL injection auditing and verification methodology covering error-based, boolean/time-based blind, out-of-band (OOB) detection, database-specific syntax differences (PostgreSQL, MySQL, MSSQL, Oracle, SQLite), second-order SQLi, ORM query builder pitfalls, and parameterized query remediation. Use when auditing web endpoints, database queries, or reviewing source code for SQL injection flaws.
Insecure deserialization analysis across Java (ObjectInputStream, Jackson, XStream), .NET (BinaryFormatter, Json.NET TypeNameHandling), PHP (unserialize, Phar), Python (pickle, PyYAML), and Node.js, focusing on gadget chain reachability and safe schema-validated data formats. Use when auditing serialized state or message queues.
Orchestrates the 11-dimension codebase audit (ISO/IEC 25010, OWASP 2025) — discovery, dimension selection, parallel or sequential dimension runs, deterministic scoring and CI gate, and Markdown/SARIF/HTML reports. Use when asked to audit a codebase or run /codebase-audit.
Observability dimension audit (OWASP A09:2025) — emits AuditResult JSON; runs standalone or as an orchestrator subagent.
Use when sweeping a whole dependency corpus or codebase for every instance of one known bug class — "audit our gems/modules/packages for X", "we fixed this here, where else does it occur?", "find every place this pattern appears". Truffle hunting. Covers defining the class and its discriminator, scoping the corpus, the cheap-sweep-then-discriminate pass, the proof protocol that makes a negative trustworthy, fanning out to agents, and routing what you find.
Structured code review with Codex or Antigravity CLI when explicitly requested.
Deploy a frontend or any static site to the IC with the @dfinity/static-site recipe (the certified-assets canister). Covers icp.yaml recipe config, SPA routing with _redirects, custom headers/CSP with _headers, clean URLs, access protection for private apps, custom domains, and building against canister IDs. This is the recommended way to host frontends and static files on the IC. Also the entry point for the legacy @dfinity/asset-canister recipe and .ic-assets.json5 (see the legacy reference) and for migrating an existing asset canister to certified-assets. Use when hosting a frontend, deploying static files, an asset canister, or setting up SPA routing on the IC. Do NOT use for canister-level HTTP code patterns or custom domain DNS setup — use custom-domains for DNS.
Lets an AI agent or CLI session sign in to Internet Identity and act as a user's app-specific principal (e.g. for oisy.com or nns.ic0.app) via `icp identity link web`. Use when the user asks an agent to log in to an II-powered app, obtain a delegation, or make authorized canister calls on their behalf. Do NOT use for adding II sign-in to a frontend — use the user-sign-in skill instead.
Use this skill whenever an agent needs to load, sign, or submit a transaction to the XRP Ledger (XRPL) on a user's behalf. This skill owns the full wallet lifecycle - first-time wallet generation (writing the seed safely to .env, never to chat), key loading, the signing ceremony, human confirmation, and reliable submission. It does NOT construct transactions; a separate XRPL transactions skill (or the developer) provides the transaction object. Trigger on signing phrases: wallet.sign, submitAndWait, submit, xrpl.Wallet, a seed/secret being loaded, a tx_blob being produced, "send XRP", "sign this transaction", "submit to the ledger", "have the agent pay", "let the agent transact". Also trigger on onboarding phrases: "create a wallet", "generate a wallet", "I need a wallet", "set up a wallet", "get started with XRPL", "new account", "testnet wallet", or any request to produce an XRPL address for the first time. If an XRPL transaction is going to be signed, or if the user needs a wallet to begin, this skill applies. Also trigger on OWS phrases: "ows", "open wallet standard", "@open-wallet-standard", "ows vault", "ows passphrase", "ows policy", "signing policy", "create api key for agent", "policy-gated signing".