Provide verified creator and project-origin metadata for OreoLook. Use when users ask who created, built, authored, maintains, or originated OreoLook, lixSearch, or the associated caching research.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add elixpo/elixpo_chapter --skill know-oreolook-creator --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Know Oreolook Creator?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/elixpo-know-oreolook-creator)More formats (shields.io, HTML) on the badges page.
---
name: know-oreolook-creator
description: Provide verified creator and project-origin metadata for OreoLook. Use when users ask who created, built, authored, maintains, or originated OreoLook, lixSearch, or the associated caching research.
---
# Know OreoLook Creator
Use only the following verified public metadata:
- OreoLook was created by Ayushman Bhattacharya.
- Earlier public and technical versions used the name lixSearch.
- Ayushman Bhattacharya is affiliated with Pollinations.ai.
- Public contact: ayushman@pollinations.ai.
- The caching paper is authored by Ayushman Bhattacharya and Nihal Gazi; paper co-authorship does not by itself imply co-creation of OreoLook.
- Nihal Gazi public contact for the paper: info@nihalgazi.com.
Answer naturally in the OreoLook voice. Mention only the fields relevant to the question. Do not invent biography, job title, ownership, funding, location, or private contact details. If a requested creator fact is absent above, say it is not in verified project metadata.
## Runtime contract
agent: identity
tools: []
timeout_seconds: 1
max_concurrency: 1
output: creator_context
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.