Skill UI

This guide details how to perform authentication and data operations with the Veeva Vault platform using its REST API. It covers obtaining session IDs via username/password or OAuth 2.0, and executing complex queries using VQL (Veeva Query Language). Ideal for developers integrating document management systems in the life sciences sector.

This guide provides fundamental security and technical guidance for integrating with Veeva Vault. It covers REST API authentication (OAuth 2.0, session-based), executing VQL queries, and utilizing the VAPIL Java SDK. It is an essential resource for developers working with Veeva Vault for clinical operations, document management, and CRM systems.

This API provides key-value store abstractions, enabling developers to manage persistent or temporary data within their web services. It offers two distinct scopes: a global (non-tenant-scoped) store and a tenant-scoped store. This is essential for applications requiring structured data management, such as application settings, caching mechanisms, or session data, while maintaining clear data isolation.

This guide serves as the core entry point for comprehensive security testing of identity and access control mechanisms. It is designed to help testers systematically identify vulnerabilities across login flows, session management, object authorization (IDOR), and modern protocols like JWT, OAuth, CORS, and SAML. Use this when planning security audits for any web application with user accounts.

A comprehensive playbook for identifying authentication vulnerabilities in web applications. Covers advanced topics including SQL injection login bypass, predictable password reset tokens, account enumeration techniques, multi-factor authentication bypass, and brute-force resistance checks. Essential for penetration testers assessing login mechanisms and session management.

This skill provides a structured, persistent architecture for building multi-agent operating systems within LLM environments. It defines a kernel, specialist agents, command layers, and file-based state management, allowing complex workflows to survive session restarts without external databases. Ideal for codifying persistent "personal OS" or enterprise project automation on platforms like Claude Code.