SkillAgentSearch skills...

codiris-agentizer

This skill should be used when the user asks to "agentize a website", "transform a website", "create an agentfront", "build a WWA app", "make an agent-first website", "turn a website into an agent experience", "agentizer", "wwa transform", or mentions "agentfront" in context of building one from a U…

Install / Use

npx skills add hashgraph-online/awesome-codex-plugins --skill wwa-transform

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Supported Platforms

Universal

Tags

Our assessment of codiris-agentizer

codiris-agentizer scores 84/100 on our quality scale, 2923rd of 4,698 Development & Engineering skills we index.

Its SKILL.md is 103 KB long, well organised into 87 sections with 31 code examples: long enough that it reads more like full documentation than a focused instruction file, which agents can find harder to follow.

With 1,075 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
21/30
Structure
20/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so codiris-agentizer is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

Review

Our scan of the first 100 KB of the file found 1 pattern worth reviewing before you install codiris-agentizer. An AI review of the same text found nothing harmful.

  • mediumSends the output of a local command to a remote serverline 481
    - `curl https://wwa.{slug}.codiris.app/mcp -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_products","arguments":…

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

codiris-agentizer compared with similar skills

All 4 of these similar skills score higher than codiris-agentizer; compare them before choosing.

SkillScoreStarsUpdatedFormat
codiris-agentizer (this skill)by hashgraph-online841.1k53d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install codiris-agentizer?
Run npx skills add hashgraph-online/awesome-codex-plugins --skill codiris-agentizer. The install tabs above show the steps for each supported agent.
Which AI agents does codiris-agentizer work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is codiris-agentizer safe to use?
Our scan of the first 100 KB of the file found 1 pattern worth reviewing before you install codiris-agentizer. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is codiris-agentizer still maintained?
The repository was last updated about 2 months ago, so codiris-agentizer is actively maintained.

name: codiris-agentizer description: >- This skill should be used when the user asks to "agentize a website", "transform a website", "create an agentfront", "build a WWA app", "make an agent-first website", "turn a website into an agent experience", "agentizer", "wwa transform", or mentions "agentfront" in context of building one from a URL. version: 2.0.0 allowed-tools:

  • Read
  • Write
  • Edit
  • Bash
  • Glob
  • Grep
  • Agent
  • WebFetch
  • WebSearch argument-hint: <website-url>

Codiris Agentizer v2 — Intelligent Website-to-Agentfront

Transform any website into a custom AI-powered agentfront. The skill deeply analyzes the company — its market, products, value proposition, customers — then builds a tailored experience. NOT a template copy-paste.

Core Principle

Understand the company first, build second. Every company is different:

  • Stripe sells APIs to developers → show API products, code examples, pricing tiers
  • Nike sells shoes to consumers → show product catalog, categories, shopping
  • Visa sells payment cards → show card tiers, comparisons, benefits
  • Salesforce sells enterprise SaaS → show solutions by industry, case studies, demos

The agentfront must reflect what the company ACTUALLY is, not what Visa is.

Template Location

./template/ relative to this SKILL.md — the skill directory (typically ~/.claude/skills/agentizer/ after install) contains the Next.js template. Content is generated custom per company. After cp -R, run the template's npx next build once to confirm nothing regressed in the template itself.

Reference Implementation

https://wwa.visa.codiris.app — live demo of a finished agentfront (payment card company). Source for the template is at https://github.com/Humiris/wwa-transform/tree/main/template.

If any template file looks incomplete or broken, inspect the live demo via WebFetch for visual reference, then apply the visaCards → productItems / VisaCard → ProductItem / annualFee → price renames — don't try to fix the template stub in place.


PHASE 1: Deep Company Intelligence

Step 1.1: Crawl Multiple Pages

Use WebFetch on at minimum:

  1. Homepage — hero, value prop, main CTAs, navigation
  2. Products/Features page — what they actually sell
  3. Pricing page (if exists) — how they charge, what tiers
  4. About page — company story, mission, stats

For EACH page, ask WebFetch:

Extract everything: brand name, tagline, ALL image URLs (full absolute), 
colors (hex from buttons/headers/CSS), navigation items, products/features 
with descriptions, pricing tiers, stats/numbers, customer logos, 
testimonials, CTAs, form fields. Be exhaustive.

Step 1.2: AI Company Analysis

After crawling, THINK deeply about the company. Answer these questions BEFORE writing any code:

Market Understanding:

  • What industry is this company in? (Fintech, SaaS, E-commerce, Healthcare, etc.)
  • Who are their customers? (Developers, Enterprises, Consumers, SMBs)
  • What problem do they solve?
  • Who are their competitors?

Product Understanding:

  • What do they sell? (APIs, Physical products, Subscriptions, Services, Cards)
  • How many products/tiers do they have?
  • How do they charge? (Per-transaction, Subscription, One-time, Usage-based, Free)
  • Do they have a free tier or trial?

Content Structure:

  • What sections make sense for THIS company's homepage?
  • What navigation items should exist?
  • What categories should products be organized by?
  • Should there be a "cards" section? (Only if they sell cards/plans/tiers)
  • Should there be a pricing grid? A product catalog? Case studies?

Value Proposition:

  • What's their main headline?
  • What stats are impressive? (Users, revenue, uptime, countries)
  • What social proof do they have? (Customer logos, testimonials)

Typography (CRITICAL — match brand aesthetic):

The template uses Geist by default. You MUST change fonts to match the brand:

| Brand Type | Fonts to Use | Implementation | |------------|--------------|----------------| | Luxury fashion (Dior, Hermès, Chanel) | Playfair Display + Inter | Serif headings, clean body | | Tech/SaaS (Stripe, Notion, Linear) | Inter or Geist | Modern sans-serif | | Premium/Editorial (Apple, Aesop) | SF Pro / Helvetica Neue / system fonts | Clean, minimal | | Fintech (Visa, Chase) | Geist / Inter | Professional sans | | E-commerce (Amazon, Walmart) | Inter / Roboto | Readable, utilitarian |

Update src/app/layout.tsx:

import { Playfair_Display, Inter } from "next/font/google";

const serif = Playfair_Display({ variable: "--font-serif", subsets: ["latin"] });
const sans = Inter({ variable: "--font-sans", subsets: ["latin"] });

// In body: className={`${serif.variable} ${sans.variable} font-sans`}

Update src/app/globals.css:

:root {
  --brand-primary: #000000;    /* match brand color */
  --brand-secondary: #C9A96E;
  --font-serif-brand: var(--font-serif), "Didot", "Bodoni MT", "Georgia", serif;
}

h1, h2, .font-serif {
  font-family: var(--font-serif-brand);
  letter-spacing: -0.01em;
}

User Intent (CRITICAL — drives CTAs and modals): Analyze what users ACTUALLY do on this site. Map to correct CTA:

| Company Type | Primary Intent | CTA Text | Modal Type | |--------------|---------------|----------|------------| | E-commerce (Dior, Nike, Apple) | Shop / Buy products | "Shop Now" | Cart / Product detail | | SaaS/API (Stripe, Notion) | Try / Book demo | "Start Free" or "Book a Demo" | Demo booking form | | Enterprise (Salesforce) | Contact sales | "Contact Sales" | Sales form | | Financial (Visa, banks) | Apply / Get card | "Apply Now" | Application form | | Marketplace — Listings (Airbnb, Booking, Uber) | Search / Book | "Start Searching" | Search UI | | Marketplace — C2C (Vinted, Depop, Etsy, eBay) | Sell AND Browse (dual intent) | "Sell Now" + "Start Browsing" | Seller signup modal (personal / pro) | | Services (Consulting) | Contact / Meeting | "Book a Call" | Calendar booking | | Content (Netflix, Spotify) | Subscribe / Try | "Start Free Trial" | Signup form |

NEVER use "Book a Demo" for e-commerce. E-commerce brands want you to SHOP, not schedule a meeting.

Update these files based on intent:

  • brand-config.ts → ctaPrimary and ctaSecondary
  • hero-section.tsx → button text
  • solution-detail-panel.tsx → button text
  • book-demo-modal.tsx → rename, change fields to match intent (e-commerce = Contact Client Services, Cart, or remove entirely)
  • actions.ts system prompt → what the agent offers users

Step 1.3: Define the Page Architecture

Based on your analysis, decide which sections the homepage should have. Choose from:

| Section | Use When | Example | |---------|----------|---------| | Hero Carousel | Always | Rotating through top products/features | | Stats Bar | Company has impressive numbers | "$1.9T processed", "99.999% uptime" | | Product Grid | 3+ distinct products | API products, SaaS modules | | Pricing Tiers | Clear pricing tiers exist | Free/Pro/Enterprise | | Feature Showcase | Key differentiators | With images and descriptions | | Customer Logos | Has notable customers | "Trusted by Amazon, Shopify..." | | Solution Categories | Products grouped by use case | "For Startups", "For Enterprise" | | Code Example | Developer-focused company | Interactive code snippet | | Card Catalog | Sells cards/plans consumers browse | Credit cards, subscription plans | | CTA Banner | Always | "Book a Demo" / "Get Started" / "Start Free" | | World Map | Company has global presence story | Payment networks, logistics, international SaaS |

DO NOT include sections that don't apply:

  • API company → NO credit card tiers, NO card comparison
  • E-commerce → NO API docs, NO code examples
  • SaaS without global story → NO world map (make handleShowMap a no-op in page.tsx)
  • Company without browsable products → leave productItems array empty, the browse section won't render

PHASE 2: Download Assets

Step 2.1: Download ALL Images

MANDATORY. The agentfront is useless without real images.

❗ The single biggest bug in past transforms is shipping images from the wrong brand — a generic "sneaker" photo from Unsplash that happens to show a Nike Swoosh on an adidas site, or a "handbag" photo that's clearly Chanel on a Dior site. Mis-branded imagery destroys credibility instantly.

Rule: Every image that represents a specific named product or franchise (e.g. "Samba OG", "Air Max 90", "Lady Dior") MUST come from a source that lets you verify it shows the correct brand. Generic-category Unsplash photos are banned for these slots. They are OK only for brand-agnostic shots (lifestyle hero, category tiles with no named product, abstract backgrounds).

And every image MUST pass visual verification (Step 2.3) before you write its path into cards.ts / solutions.ts.

mkdir -p ~/wwa.{domain}/public/images/cards

# Use browser headers to bypass CDN blocks
curl -L -o "public/images/{name}.jpg" "{url}" \
  -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36" \
  -H "Referer: https://{domain}/" \
  -H "Accept: image/*"

Download at minimum:

  • Logo (SVG preferred, PNG fallback)
  • Hero/banner image
  • 1 image per product/solution (6-10 total)
  • 2-4 lifestyle/feature images
  • Customer logos if available
  • Product screenshots/UI images

Image Source Priority (USE IN THIS ORDER)

For e-commerce catalogs (fashion retailers, beauty retailers, online-only fashion), always try method 0 FIRST:

0. Scrape the brand's SSR catalog JSON via Chrome MCP — modern e-commerce sites (Zara, H&M, ASOS, Nordstrom, Sephora, etc.) ship the full product grid as a JSON blob inside a <script> tag on every category page. Server-side curl gets WAF-blocked, but Chrome MCP with an organic-looking tab has no trouble reading the DOM.

Two flavors to look for:

  • JSON-LD <script type="application/ld+json"> (cleanest — H&M, many schemas). Has @type: Product entries with name, image[], offers.price ready to JSON.parse.
  • Raw hydration JSON (Zara, ASOS — biggest <script> that contains the brand's CDN hostname). Not always valid JSON; regex out the image URL pattern (e.g. /static\.zara\.net\/photos\/[^"'\s]+\.jpg/g or /products\/[a-z0-9-]+\/\d+-\d+[a-z0-9-]*/gi) and dedupe by product id.

Pattern that works today (verified on Zara 259 · H&M 216 · ASOS 365 · Uniqlo 54 scrapes):

// In Chrome MCP, navigate to e.g. https://www.zara.com/uk/en/woman-dresses-l1066.html, then:
(() => {
  const scripts = Array.from(document.querySelectorAll('script'));
  // JSON-LD path (H&M-style): cleanest
  const ld = document.querySelector('script[type="application/ld+json"]');
  if (ld && ld.textContent.includes('"@type":"Product"')) {
    return JSON.parse(ld.textContent);
  }
  // Raw-hydration path (Zara/ASOS): regex
  const big = scripts.find(s => (s.textContent || '').includes('<brand-cdn-hostname>'));
  const text = big.textContent;
  // Adjust regex per brand URL shape
  const urls = [...new Set((text.match(/https:\/\/static\.zara\.net\/[^"'\s]+\.jpg/g) || []))];
  return urls;
})();

Then get the result out of Chrome via a Blob download:

const blob = new Blob([JSON.stringify(catalog)], { type: 'application/json' });
const a = Object.assign(document.createElement('a'), { href: URL.createObjectURL(blob), download: 'catalog.json' });
document.body.appendChild(a); a.click();
// File lands in ~/Downloads/catalog.json — move to project, feed to cards.ts rewrite

Hotlink don't download. Once you have the URLs, put them directly in cards.ts's image field — the browser will load them via <img src> (no CORS issue on img tags). No local copy needed. Server-side curl typically fails with 403 / 000 (WAF), but that doesn't matter because production serves from users' browsers.

For named products/franchises (Samba, Air Jordan 1, Stan Smith, Lady Dior,

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryDevelopment
Updated1mo ago
Forks294

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions