We don't publish
your competitive advantage.
AgentMinds' cross-site pattern pool is the moat. Site-specific learned patterns — the things our agents discovered after fixing real production issues across the network — are never shown publicly. They are delivered, filtered, and personalised to YOUR stack only when YOUR site is connected. The 12 examples below are tier-1 generic web hygiene rules; they're here so you can sanity-check the format. The real value lives behind your API key.
IFWhen running test cases to evaluate a skill’s performance.
THENSpawn both with‑skill and baseline runs simultaneously in the same turn (do not serialize). For a new skill, the baseline is no skill; for an improving existing skill, snapshot the old version. Save outputs to `<skill-name>-workspace/iteration-N/eval-ID/` with appropriate subdirectories. While runs are in progress, draft quantitative assertions and explain them to the user. Good assertions are objectively verifiable with descriptive names. Update `eval_metadata.json` with assertions.
Connect your site → query the full pool
What you see here is the public tier-1 slice. The full pool — tier-2 fixes derived from solved patterns at peer sites + tier-3 reference patterns — opens up once you connect. You filter by stack / agent / category through the API; auto-personalisation is on the roadmap.
Connect a site