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 writing the SKILL.md frontmatter description for a new or modified skill.
THENWrite a 'pushy' description that includes both what the skill does and specific contexts for when to use it. Claude tends to undertrigger skills, so include explicit examples of when to trigger (e.g., 'Make sure to use this skill whenever the user mentions X, Y, or Z, even if they don't explicitly ask for it'). Do not put 'when to use' information in the body—it all goes in the description.
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