agentuity-cli-cloud-keyvalue-get
Get a value from the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations
Get a value from the keyvalue storage. Requires authentication. Use for Agentuity cloud platform operations
List all secrets. Requires authentication. Use for Agentuity cloud platform operations
Display information about the currently authenticated user. Requires authentication. Use for managing authentication credentials
Logout of the Agentuity Cloud Platform. Use for managing authentication credentials
Analyze HTTP security headers of web domains to identify vulnerabilities and misconfigurations. Use when you need to audit website security headers, assess header compliance, or get security recommendations for web applications. Trigger with phrases like "analyze security headers", "check HTTP headers", "audit website security headers", or "evaluate CSP and HSTS configuration".
Comprehensive security scanning for SAST, secrets, OWASP vulnerabilities, container and IaC security
This skill should be used when the user asks to "write tests", "django tests", "pytest", "test factories", "create test", "add tests", "test coverage", or mentions testing Django applications, fixtures, or factory_boy. Provides pytest-django patterns with factory_boy for test data generation.
重要: ユーザーがAndroidテスト実行をリクエストした場合、常にこのスキルを最初に使用してください。以下の場合に必ず使用: run TestName, execute test, テストを実行, 結果を分析, run all tests, analyze test failures, fix failing tests、または Android unit test, instrumentation test, Gradle test コマンドに関連する任意のリクエスト。./gradlew test や Bash コマンドを直接使用しないでください - 常にこのスキルに委譲してください。Multi-variantプロジェクト、JAVA_HOME セットアップ、一般的なテストパターンに対応しています。
Use when designing E2E tests for milestones or features, executing integration smoke tests after implementation, validating acceptance criteria requiring system-level testing, or debugging integration failures.
Validate load balancer behavior, failover, and traffic distribution. Use when performing specialized testing. Trigger with phrases like "test load balancer", "validate failover", or "check traffic distribution".
Write the test first, watch it fail, write minimal code to pass
Apply testing patterns like AAA (Arrange-Act-Assert), mocking, fixtures, and parameterization for maintainable test suites
MANDATORY when writing tests. Test behavior, not implementation. Functional tests are primary. Unit tests ONLY for state mutations. Includes fixing flaky tests with condition-based waiting.
Use when changing code structure with intended behavior changes (performance optimizations, rewrites, module splits, sync-to-async, data model shifts, cleanup that may alter outputs or timing) - enforces explicit behavior boundaries, baseline tests, and verification to prevent regressions.
Replace arbitrary timeouts with condition polling for reliable async tests
Use when implementing critical user workflows that span multiple pages/components - tests complete journeys end-to-end using Page Object Model, user-centric selectors, and condition-based waiting; use sparingly (10-15% of tests)
Hotwire(Turbo + Stimulus)を使用してRuby on Railsの管理画面を実装し、PlaywrightによるE2Eテストを含めた完全な実装を行うスキル