Meta-Pattern Recognition — quality + safety report
In the Skillier index (superpowers-skills__meta-pattern-recognition) · scanned 2026-06-03 · engine: builtin+triage
✓ Clean — no heuristic safety flags surfaced.
Heuristic flags from the builtin scanner, which is known to over-flag (it trips on legitimate env-reading integrations, security skills, and library .eval calls). This is NOT an authoritative malicious verdict — re-scan with SkillSpector for the authoritative result. Run the authoritative scan →
📇 This skill is in the Skillier index (curated · deduped · quality-filtered). Install Skillier to route & load it into your AI client.
Quality notes
About this skill
Spot patterns appearing in 3+ domains to find universal principles
📄 Read the SKILL.md
--- name: Meta-Pattern Recognition description: Spot patterns appearing in 3+ domains to find universal principles when_to_use: when noticing the same pattern across 3+ different domains or experiencing déjà vu in problem-solving version: 1.1.0 --- # Meta-Pattern Recognition ## Overview When the same pattern appears in 3+ domains, it's probably a universal principle worth extracting. **Core principle:** Find patterns in how patterns emerge. ## Quick Reference | Pattern Appears In | Abstract Form | Where Else? | |-------------------|---------------|-------------| | CPU/DB/HTTP/DNS caching | Store frequently-accessed data closer | LLM prompt caching, CDN | | Layering (network/storage/compute) | Separate concerns into abstraction levels | Architecture, organization | | Queuing (message/task/request) | Decouple producer from consumer with buffer | Event systems, async processing | | Pooling (connection/thread/object) | Reuse expensive resources | Memory management, resource governance | ## Process 1. **Spot repetition** - See same shape in 3+ places 2. **Extract abstract form** - Describe independent of any domain 3. **Identify variations** - How does it adapt per domain? 4. **Check applicability** - Where else might this help? ## Example **Pattern spotted:** Rate limiting in API throttling, traffic shaping, circuit breakers, admission control **Abstract form:** Bound resource consumption to prevent exhaustion **Variation points:** What resource, what limit, what happens when exceeded **New application:** LLM token budgets (same pattern - prevent context window exhaustion) ## Red Flags You're Missing Meta-Patterns - "This problem is unique" (probably not) - Multiple teams independently solving "different" problems identically - Reinventing wheels across domains - "Haven't we done something like this?" (yes, find it) ## Remember - 3+ domains = likely universal - Abstract form reveals new applications - Variations show adaptation points - Universal patterns are battle-tested
Want a live grade + an embeddable README badge? Run your skill through the free scanner.
Graded independently by Skillproof — nothing to sell the author. Quality is mechanical + corpus-grounded; safety flags are heuristic (builtin+triage), not a malicious verdict.