productivity▌

A rule has three parts: conditions (what to detect), schedule (how often to check), and actions (what happens when conditions are met). When conditions are met, the rule creates alerts, which trigger actions via connectors.

Enable and configure security audit logging for Elasticsearch via the cluster settings API. Audit logs record security events such as authentication attempts, access grants and denials, role changes, and API key operations — essential for compliance and incident investigation.

You are an expert ASO keyword researcher with deep knowledge of App Store search behavior, keyword indexing, and ranking algorithms. Your goal is to help the user discover high-value keywords and build a prioritized keyword strategy.

Default to execution, not instruction. When the user expresses execution intent, carry the change through directly: run the needed shell commands, edit the real files, and verify the result instead of only replying with example commands. Treat requests like "configure", "set up", "wire", "change", "add", "fix", "migrate", "deploy", "run", or "make this use Xget" as execution intent unless the user clearly asks for explanation only.

Connectors store connection information for Elastic services and third-party systems. Alerting rules use connectors to route actions (notifications) when rule conditions are met. Connectors are managed per Kibana Space and can be shared across all rules within that space.

Build agent-facing web experiences with ATXP authentication and cookie-based browser access. \n \n Implements cookie-based authentication bridging MCP tools and browser automation, with agents obtaining auth cookies via MCP then using them for web requests \n Provides complete Node.js stack templates using Express, SQLite, @longrun/turtle for MCP, and @atxp packages for agent identity and optional payments \n Includes query-string cookie bootstrap pattern for agent browsers that cannot set HTTP-

$22

Automated code review for local changes and remote pull requests with structured analysis across correctness, maintainability, and security. \n \n Supports both local file system changes (staged and unstaged) and remote PRs (by number or URL) with automatic GitHub CLI checkout \n Analyzes code across seven dimensions: correctness, maintainability, readability, efficiency, security, edge case handling, and test coverage \n Runs optional preflight verification suites (e.g., npm run preflight ) to

ln-627-observability-auditor

Investigate a reported problem, find its root cause, and create a GitHub issue with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user.