530건 · 관련도순
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 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Summarize existing QA criteria, cases, evidence, defects, limitations, authorization, and verdict without mutation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cryptographic security for agentic systems — zero-trust agent networking, signed message envelopes (JWS/JWE), capability-based security (ocaps), Merkle tree audit trails, WASM sandboxing, and formal verification. Covers CLI dev tool security, mTLS between agents, permission boundaries (least privilege for AI agents), and supply chain security for skills/plugins. Activate on: "agent security", "zero trust agents", "secure agent communication", "capability-based security", "ocap", "signed messages between agents", "agent audit trail", "sandbox agent execution", "agent permissions", "mTLS agents", "cryptographic verification", "agent supply chain", "OWASP agentic", "prove agent did X", "tamper-proof agent logs". NOT for: application-level SAST scanning (use security-auditor), network firewall rules (use infrastructure), SOC2/HIPAA compliance (organizational), or prompt injection defense (use prompt-engineer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.