Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
中文简介正在准备中。当前显示原文说明。
531 个 · 按相关度排序
Deploy a Software-Defined Perimeter using the CSA v2.0 specification with Single Packet Authorization, mutual TLS, and SDP controller/gateway configuration to enforce zero trust network access.
中文简介正在准备中。当前显示原文说明。
Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting.
中文简介正在准备中。当前显示原文说明。
Stellar Assets (classic) + trustlines + Stellar Asset Contract (SAC) bridge to smart contracts. Covers asset issuance, distribution, authorization flags, clawback, regulated assets, trustline management, and the SAC interop layer that exposes classic assets as SEP-41 contract tokens. Use when tokenizing real-world assets, issuing stablecoins, managing trustlines, or bridging classic assets to smart contracts.
中文简介正在准备中。当前显示原文说明。
Stellar smart contract development (Rust, soroban-sdk). Entry point with project setup, contract anatomy, and build/deploy workflow, routing to three companion files in this directory — development.md (storage/TTL, authorization, cross-contract calls, tokens, events, errors, upgrades, fees, troubleshooting), testing.md (unit, fuzz, property, fork, mutation, integration), and security.md (vulnerability classes, checklists, tooling, audits). Use when writing, testing, reviewing, securing, debugging, or shipping Stellar smart contracts, including anything the user calls "Soroban" — Soroban contracts, soroban-sdk, Soroban auth/storage/TTL errors, SEP-41 tokens, or SAC integration from contract code.
中文简介正在准备中。当前显示原文说明。
Run the authorized defensive security workflow — domain security-* skills, authorization gate, risk-based routing, hardening, and review.
中文简介正在准备中。当前显示原文说明。
Use when implementing authentication, authorization, JWT tokens, security filters, password encoding, or any Spring Security configuration. Covers stateless JWT auth, token rotation, RBAC, and method-level security.
中文简介正在准备中。当前显示原文说明。
Use when configuring Spring Boot as an OAuth2 resource server, validating JWTs from an external auth provider (Keycloak, Auth0, Okta, Cognito), extracting claims, or implementing scope-based authorization.
中文简介正在准备中。当前显示原文说明。
Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.
中文简介正在准备中。当前显示原文说明。
API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.
中文简介正在准备中。当前显示原文说明。
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
中文简介正在准备中。当前显示原文说明。
Summarize existing QA criteria, cases, evidence, defects, limitations, authorization, and verdict without mutation.
中文简介正在准备中。当前显示原文说明。
Design bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.
中文简介正在准备中。当前显示原文说明。
Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.
中文简介正在准备中。当前显示原文说明。
Produce a traceable risk-based QA strategy without executing tests or expanding authorization.
中文简介正在准备中。当前显示原文说明。
Implement comprehensive security patterns to protect applications against OWASP Top 10 vulnerabilities including XSS, CSRF, SQL injection, authentication bypass, and data exposure. Use when handling user data, implementing authentication and authorization, validating input, encrypting sensitive data, preventing injection attacks, securing API endpoints, managing sessions and tokens, implementing rate limiting, configuring security headers, or building security-critical features that require defense-in-depth protection.
中文简介正在准备中。当前显示原文说明。
This skill ensures all code follows security best practices and identifies potential vulnerabilities. Use when implementing authentication or authorization, handling user input or file uploads, or creating new API endpoints.
中文简介正在准备中。当前显示原文说明。
Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.
中文简介正在准备中。当前显示原文说明。
API security testing workflow for REST and GraphQL APIs covering authentication, authorization, rate limiting, input validation, and security best practices.
中文简介正在准备中。当前显示原文说明。
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
中文简介正在准备中。当前显示原文说明。
Use when a carrier asks about fuel-card vendor selection (Comdata, EFS, WEX, RTS, Pilot Flying J, Love's Connect), discount levels, fraud control, driver authorization PINs, IFTA reporting features, cash advance, money codes, or how the card fits into payroll/settlement workflows.
中文简介正在准备中。当前显示原文说明。
Interpret and design bounded FIPA communicative-act exchanges using XC00037H semantics while keeping delivery, authority, and external effects separate. NOT for proving delivery, task authorization, or external effect completion.
中文简介正在准备中。当前显示原文说明。
Plan and diagnose FIPA-style ontology-service interactions while keeping declared ontology relations, provider capability, and application authorization separate. NOT for treating an ontology mapping as provider authority or guaranteed interoperability.
中文简介正在准备中。当前显示原文说明。
Ranks eligible skill candidates with explicit retrieval evidence, capability coverage, and uncertainty. NOT for discovery, authorization, or execution planning.
中文简介正在准备中。当前显示原文说明。
Design a bounded FIPA-style conversation and map it cautiously to JADE behavior APIs. NOT for treating a JADE API example as protocol delivery or application authorization proof.
中文简介正在准备中。当前显示原文说明。