Cloudflare solutions architect. Use when the user says "I want to build / do X" and wants the best Cloudflare-native architecture — which primitives (Workers, KV, R2, D1, Durable Objects, Queues, Workflows, AI, Email, etc.), wired how, with free-tier and plan-limit awareness and a minimal starting implementation.…
Read-only investigator for the Cloudflare account. Use to answer "what is my current state", "what's misconfigured / what are my security findings", "who changed X and when", or to dig into a specific zone/record/setting — grounded in the latest snapshot, reports, audit log, and read-only Cloudflare MCP tools. Never…
Cloudflare maximization advisor. Use to find how to get MORE value from the account — underused or missing features, beta/early-access features that fit the stack, and security/performance/cost/deliverability improvements — delivered as a prioritized roadmap with effort and impact. Read-only.
Read-only web research worker for LeadAce skills. Fetches and searches pages and returns extracted structured findings; it holds no LeadAce write tools, so page content it reads cannot write to the LeadAce workspace (its DB records).
Reviews unpromoted journal entries and helps the owner promote them into curated context. Use when the owner says "promote journal", "review my journal", "update my context memory", or runs the promotion workflow. Read-and-suggest only: this agent NEVER writes curated files itself.
Smoke-tests the deployed context-kernel MCP server: auth gating, read tools, and write/journal round-trip. Use after a deploy or when the owner says "test the MCP", "check the connector", "is context-kernel up". Reports pass/fail; does not change server code or curated content.
Reviews changes for injection, XSS, secret leakage, broken authz, SSRF in the webhook delivery dialer, and PII/PHI in logs. Use proactively on changes touching ingestion, the delivery dialer, auth, logging, or data handling.
Reviews code comments, docstrings, and doc comments for accuracy against the actual code. Use proactively after changes that alter behavior, signatures, or invariants to catch stale, misleading, or redundant comments.
Reviews changes for swallowed errors, empty catch blocks, ignored return/rejection values, and inadequate logging that hides failures. Use proactively on changes touching ingestion, the delivery dialer, retries, signing/verification, or anything with error handling.
Use this agent when you need to create a new GitHub release for a project, including analyzing commits, determining version numbers, writing release notes, and publishing the release. This agent should be triggered after significant development work is completed and you're ready to package changes into a formal…
Use this agent when you need to run, create, or review tests for the project, particularly after new features have been introduced or changes have been made to the /src folder. This agent should be invoked to ensure code quality through automated testing, set up new test suites, or review existing test coverage and…
Designs component compositions and page layouts using UI Kit. Use when the user needs to architect a dashboard, form, settings page, or multi-component layout. Considers tier selection, responsive behavior, and Aurora Fluid design patterns.
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
Create or update the feature specification from a natural language feature description.
★not rated 0 6mo agoA13 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: