Composable agent architecture
Start with an evidence-linked composition instead of an unexplained bundle. Each stack exposes its intended data flow, component trust cards, permission risks, suggested controls, and alternatives.
7 editorial compositions
Curated means selected for a use case. It does not mean every component is certified or safe for every environment.
Curated agent stack
Read current technical documentation and compare capability metadata before changing code.
Best for
Library research, dependency selection, and implementation planning.
Curated agent stack
Combine capability discovery with GitHub repository workflows.
Best for
Issue triage, pull-request review, and repository maintenance.
Curated agent stack
Use trusted browser automation metadata and document-oriented skills for product QA.
Best for
Accessibility, responsive layout, and user-flow verification.
Curated agent stack
Reference architecture for a user-controlled OpenClaw gateway and one messaging channel.
Best for
Personal or single-organization messaging assistant deployments.
Curated agent stack
Combine documentation lookup, GitHub workflows, browser testing, and database access for end-to-end development tasks.
Best for
Feature development, bug investigation, and pull-request review across the full stack.
Curated agent stack
Plan programmatic SEO pages, audit analytics, and discover comparable tools for content strategy.
Best for
Content planning, keyword strategy, programmatic SEO page production, and measurement setup.
Curated agent stack
Query Sentry for production errors, look up relevant documentation, and reproduce issues with browser automation.
Best for
Production incident response, bug triage, and root-cause analysis.
