- 📁 references/
- 📄 README.md
- 📄 SKILL.md
Strategic research framework that compresses months of market/competitive research into hours through structured power questions. Extracts unspoken industry insights, fragile market assumptions, and strategic attack surfaces from competitor data, reviews, and industry sources using parallel Exa-powered intelligence gathering. Use when user says "attack surface", "research the market", "competitive analysis", "analyze competitors", "find market opportunity", "stress-test this idea", "market research", "evaluate opportunity", "find blind spots", "market entry", or when they want to deeply understand a market, evaluate a new direction, find industry blind spots, assess a partnership, or analyze opportunities. Do NOT use for code review, testing, deployment, bug fixing, or implementation tasks. --- # Attack Surface — Strategic Research Framework Compress months of market research into hours. The difference between 3 hours and 3 months isn't the amount of information — it's knowing which questions actually matter. Instead of "summarize these" or "analyze the competition", this framework extracts: - **UNSPOKEN INSIGHTS** — what successful players understand that customers never say out loud - **FRAGILE ASSUMPTIONS** — beliefs the entire market is built on, and how they break - **ATTACK SURFACES** — the blind spots, the fragile consensus, the opening nobody is talking about ## When to Use - Entering a new market or vertical - Evaluating a new feature direction for an existing project - Assessing a partnership or platform opportunity - Stress-testing a business idea before committing - Finding competitive blind spots and underserved niches - Any strategic question that benefits from deep evidence-based analysis ## Workflow Overview 7 phases, alternating between automated intelligence gathering and user-guided analysis: | Phase | Name | Mode | Output | |-------|------|------|--------| | 1 | Briefing | Interactive | Research brief | | 2 | Source Collection | Automated (parall
- 📁 agents/
- 📁 references/
- 📄 SKILL.md
Use `chilly` to operate chill.institute from the terminal. Start here for shared agent-safe defaults, then load the nested reference docs for auth, reads, mutations, or contract discovery only when that workflow is relevant.
Use when you have a spec or requirements for a multi-step task, before touching code
Expert diagnosis for Tokio/async Rust issues including deadlocks, task leaks, performance bottlenecks, and cancellation safety
>-
Guide for MEV concepts, common attacks, mitigations, and how to organize MEV-related resources in README.md.
- 📁 assets/
- 📁 campaigns/
- 📁 data/
- 📄 .gitignore
- 📄 AGENTS.md
- 📄 BACKLOG.md
Local-only multi-agent orchestrator with token optimization, 6-signal composite routing, and persistent memory. Routes all tasks through local executor bridges (Claude Code, Hermes, Gemini, Codex) with DAG dependencies, auto-episode creation, and cognitive profiles.
- 📁 templates/
- 📄 LICENSE.txt
- 📄 SKILL.md
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
- 📄 example-corpus.md
- 📄 prompt-template.md
- 📄 README.md
Run a critic agent conditioned on the user's own past edits to catch voice and tone problems in a draft. Use when user says 'run voice-critic', 'voice check', 'does this sound like me', or wants a pass on a draft that has already been fact-checked and style-checked but still reads wrong. Do NOT use for fact-checking (claims verification is a separate agent) or for style-guide enforcement (also a separate agent). This skill specifically catches the gap between 'correct' and 'sounds like the author'.
Calculate the hash of a given text.
Accessibility audit: WCAG 2.1 AA — forms, icons, HTMX, Alpine, semantic HTML
Reads recent session context, infers what you were working on, and proposes the specific next action. Use when resuming after a break, or say "act" / "what should we do next" / "pick up where we left off". Executes immediately on confirmation.
