Create Website
wondelai/skills
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion.
Evaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis.
$ npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install curiositech/some_claude_skills product-appeal-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/product-appeal-analyzer .claude/skills/product-appeal-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "product-appeal-analyzer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzer into .claude/skills/product-appeal-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-appeal-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install curiositech/some_claude_skills product-appeal-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/product-appeal-analyzer .agents/skills/product-appeal-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "product-appeal-analyzer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzer into .agents/skills/product-appeal-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-appeal-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install curiositech/some_claude_skills product-appeal-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/product-appeal-analyzer .cursor/skills/product-appeal-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "product-appeal-analyzer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzer into .cursor/skills/product-appeal-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-appeal-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/curiositech/some_claude_skills.git --path .claude/skills/product-appeal-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install curiositech/some_claude_skills product-appeal-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/product-appeal-analyzer .gemini/skills/product-appeal-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "product-appeal-analyzer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzer into .gemini/skills/product-appeal-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-appeal-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install curiositech/some_claude_skills product-appeal-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/product-appeal-analyzer .github/skills/product-appeal-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "product-appeal-analyzer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzer into .github/skills/product-appeal-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-appeal-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install curiositech/some_claude_skills product-appeal-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/curiositech/some_claude_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/product-appeal-analyzer .opencode/skills/product-appeal-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "product-appeal-analyzer" agent skill from https://github.com/curiositech/some_claude_skills/tree/main/.claude/skills/product-appeal-analyzer into .opencode/skills/product-appeal-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "product-appeal-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
product-appeal-analyzerEvaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis.
Product Appeal Analyzer is an agent skill from curiositech/some_claude_skills. Evaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis. Assess whether users will WANT a product (not just use it), identity fit, trust signals, and value proposition clarity. Activate on "will they like it", "market positioning", "appeal analysis", "product desirability", "value proposition", "why would someone choose this", "landing page review", "conversion optimization", "messaging strategy". NOT for UX friction analysis (use ux-friction-analyzer)…
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts and reference files (for example `.claude-plugin/plugin.json`, `CHANGELOG.md` and `references/identity-signals.md`).
It sits in Frontend & Design, covering Positioning and messaging, Landing pages and UI design. The repository describes itself as: Claude skills that make my life easier. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6713fc7. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditWebFetchFrom allowed-tools in the SKILL.md frontmatter.
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Product Appeal Analyzer loads about 2.4k tokens when it runs, and up to ~9.4k if it reads all its reference files. Until then it costs about 159 tokens; SKILL.md has 886 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from curiositech/some_claude_skills at commit 6713fc7, republished under its MIT licence (© curiositech). 886 words, ~2,351 tokens.
.claude/skills/product-appeal-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.Evaluate whether users will want a product—not just use it. The complement to friction analysis.
Core insight: Users don't choose the best product—they choose the product that feels most like it was made for them.
✅ Use for:
❌ NOT for:
All three must be present. Missing any one kills conversion:
IDENTITY FIT
"This is for people like me"
/\
/ \
/ \
/ ★ \
/ DESIRE \
/ \
/______________\
PROBLEM TRUST
URGENCY SIGNALS
"I need this now" "This will actually work"| Missing Element | User Reaction |
|---|---|
| Identity Fit | "Seems useful, but not for me" |
| Problem Urgency | "Cool, maybe someday" |
| Trust Signals | "Looks sketchy / too good to be true" |
Decision tree: When analyzing, score each vertex 1-10. If any is <5, that's your priority fix.
Within 5 seconds of landing, a visitor should know:
How to run it:
Scoring:
| Result | Score | Action |
|---|---|---|
| All 4 clear in <3 sec | 9-10 | Ship it |
| All 4 clear in 3-5 sec | 7-8 | Minor polish |
| 3 of 4 clear | 5-6 | Fix the gap |
| 2 or fewer clear | 2-4 | Significant rework |
| Confusing/unclear | 0-1 | Start over |
For each persona, document:
For each persona:
PERSONA: [Name]
IDENTITY FIT [/10]
Visual identity match [/10] "Does this look like my kind of tool?"
Language resonance [/10] "Do they speak my language?"
Implied user match [/10] "Are people like me shown?"
PROBLEM URGENCY [/10]
Pain point acknowledged [/10] "They understand my problem"
Emotional resonance [/10] "They get how frustrating it is"
Solution clarity [/10] "I see how this fixes it"
TRUST SIGNALS [/10]
Professional execution [/10] "This looks legitimate"
Social proof [/10] "Others like me use it"
Risk reduction [/10] "What if it doesn't work?"
OVERALL APPEAL SCORE: [/90]| Objection | Type | How Addressed? |
|---|---|---|
| "Is this legit?" | Trust | [Answer] |
| "I've tried things before" | Skepticism | [Answer] |
| "Too expensive" | Value | [Answer] |
| "Too complicated" | Effort | [Answer] |
| "Not for people like me" | Identity | [Answer] |
| "What if it doesn't work?" | Risk | [Answer] |
| "I'll do it later" | Urgency | [Answer] |
Use priority formula: Impact = (Users Affected × Severity) / Fix Difficulty
Categorize into:
Novice thinking: "List all capabilities to show value"
Reality: Visitors scan for 2-3 seconds. Feature lists feel generic.
What to use instead:
| Bad | Good |
|---|---|
| "AI-Powered Recovery Planning Tool with Analytics" | "Know exactly what to do next in your recovery" |
| "Comprehensive Legal Document Platform" | "Find out in 2 minutes if your record can be expunged" |
Detection: Headline contains 3+ nouns or buzzwords like "AI-powered", "comprehensive", "platform"
Novice thinking: "Show the product interface so people know what they're getting"
Reality: Strangers don't understand your UI. They care about outcomes.
What to use instead:
Detection: Hero image is a product screenshot with no context
Novice thinking: "Get their email immediately, then convert them"
Reality: Trust builds in stages. Asking for too much too early kills conversion.
The Trust Ladder (each rung requires more trust):
Detection: Asking for account creation before demonstrating value
Novice thinking: "Broad appeal = more users"
Reality: When everyone is the target, no one feels targeted.
What to use instead:
| Signal Type | How It Works |
|---|---|
| Visual identity | Dark mode = "power user"; Soft pastels = "wellness" |
| Language/tone | "Crush your goals" vs "Find your balance" |
| Social proof | Company logos vs individual testimonials |
| Complexity | Minimal = simplicity-seeker; Feature-rich = power user |
Detection: Homepage tries to appeal to 3+ different personas
Run: python scripts/appeal_scorer.py <url>
Produces structured JSON output with scores and recommendations.
| File | When to Use |
|---|---|
references/scoring-templates.md | Full scoring matrices and templates |
references/trust-ladder.md | Deep dive on trust building stages |
references/identity-signals.md | Visual/verbal identity signal catalog |
references/objection-catalog.md | Common objections by product type |
When running this skill, produce:
Appeal + Friction = Complete picture
| This Skill Answers | ux-friction-analyzer Answers |
|---|---|
| "Do they want it?" | "Can they use it?" |
| Will they choose this over alternatives? | Can they complete the task? |
| Does it feel made for them? | Does the flow make sense? |
| Is the promise compelling? | Is the experience smooth? |
Run both: High appeal + high friction = frustrated users. Low friction + low appeal = abandoned product.
Philosophy: A product with low friction but low appeal gets abandoned. A product with high appeal but high friction gets frustrated users. You need both.
© curiositech, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files (scripts, references) in .claude/skills/product-appeal-analyzer of curiositech/some_claude_skills.
Open the folder on GitHubat commit 6713fc7
Product Appeal Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Product Appeal Analyzer this skillcuriositech/some_claude_skills | 244 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Create Websitewondelai/skills | 2.4k | — | ~5.7k | Automated safety check: Pass | MIT | |
| Landing CraftEliasOulkadi/shokunin | 114 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Landing Page Optimizerthatrebeccarae/claude-marketing | 161 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Page Croborghei/Claude-Skills | 891 | — | ~5.9k | Automated safety check: Pass | MIT | |
| Design-Led Website Builderliucongg/liucong-skills | 248 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
wondelai/skills
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion.
EliasOulkadi/shokunin
Build conversion-optimized landing pages with CRO frameworks (Conversion Research, LIFT Model), scroll effects, A/B testing, personalization, form optimization, and Core Web Vitals (INP, LCP, CLS).
thatrebeccarae/claude-marketing
Landing page audit and optimization for conversion. An agent skill from thatrebeccarae/claude-marketing.
borghei/Claude-Skills
Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and…
liucongg/liucong-skills
Turns a short brief into a researched, distinctive website: lock the intent with at most one question, research live reference sites, source materials, then build and verify.
syahiidkamil/Software-Engineer-AI-Agent-Atlas
Complete UI/UX design capability — a wiki-style knowledge map of design theory (UX laws, Nielsen heuristics, usability, visual hierarchy, typography, contrast/WCAG, design systems…
curiositech/some_claude_skills
Detect crisis signals in user content using NLP, mental health sentiment analysis, and safe intervention protocols.
curiositech/some_claude_skills
End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards.
curiositech/some_claude_skills
Build production CI/CD pipelines with GitHub Actions. An agent skill from curiositech/some_claude_skills.
curiositech/some_claude_skills
Expert in background job processing with Bull/BullMQ (Redis), Celery, and cloud queues.
curiositech/some_claude_skills
Strategic analyst that maps competitive landscapes, identifies white space opportunities, and provides positioning recommendations.
curiositech/some_claude_skills
Build production computer vision pipelines for object detection, tracking, and video analysis.
Categories
Evaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis. Product Appeal Analyzer is an agent skill from curiositech/some_claude_skills. Evaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis.
Product Appeal Analyzer fits situations like: tasks that involve Positioning and messaging; tasks that involve Landing pages; tasks that involve UI design.
Run `npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a claude-code`. Or copy the skill folder (.claude/skills/product-appeal-analyzer in curiositech/some_claude_skills) into .claude/skills/product-appeal-analyzer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a codex`. Or copy the skill folder (.claude/skills/product-appeal-analyzer in curiositech/some_claude_skills) into .agents/skills/product-appeal-analyzer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add curiositech/some_claude_skills --skill product-appeal-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-appeal-analyzer, .gemini/skills/product-appeal-analyzer, .github/skills/product-appeal-analyzer and .opencode/skills/product-appeal-analyzer in your project.
Going by SKILL.md and its folder, Product Appeal Analyzer needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, WebFetch.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Product Appeal Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.4k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Product Appeal Analyzer: Create Website (wondelai/skills, 2.4k stars), Landing Craft (EliasOulkadi/shokunin, 114 stars), Landing Page Optimizer (thatrebeccarae/claude-marketing, 161 stars) and Page Cro (borghei/Claude-Skills, 891 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
curiositech (a GitHub organization) maintains it in curiositech/some_claude_skills, which has 244 GitHub stars. The repository holds 95 skills in this directory. The repository was last updated on September 6, 2026.
Source: curiositech/some_claude_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.