Agent skill · Security

suede-signup

Suede-owned signup conversion discipline. Use when auditing or redesigning account creation, registration, or trial-start flows, including field friction, progressive profiling, identity options, mobile behavior, abandonment, and measurement. NOT FOR: post-signup activation (use suede-onboarding), lead-capture forms (use suede-site-alchemy), or deploying auth and compliance changes without review.

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill suede-signup --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 10 KB
Bundled scripts: none
Version: 2.0.0
Path: skills/suede-signup/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Suede Signup Conversion Suede Signup identifies measurable friction between intent and completed account creation, then turns it into accessible, security-preserving experiments. It optimizes only the registration boundary and hands post-account activation to the Suede onboarding lane. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before providing recommendations, understand: 1. **Flow Type** - Free trial signup - Freemium account creation - Paid account creation - Waitlist/early access signup - B2B vs B2C 2. **Current State** - How many steps/screens? - What fields are required? - What's the current completion rate? - Where do users drop off? 3. **Business Constraints** - What data is genuinely needed at signup? - Are there compliance requirements? - What happens immediately after signup? --- ## Core Principles ### 1. Minimize Required Fields Every field reduces conversion. For each fie

What's inside
Steps it walks through
  1. Initial Assessment
  2. Core Principles
  3. 1. Minimize Required Fields
  4. 2. Show Value Before Asking for Commitment
  5. 3. Reduce Perceived Effort
  6. 4. Remove Uncertainty
  7. Field-by-Field Optimization
  8. Email Field
  9. Password Field
  10. Name Field
  11. Social Auth Options
  12. Phone Number
  13. Company/Organization
  14. Use Case / Role Questions
Ships with 2 files
  • agents/openai.yaml
  • evals/evals.json
More from suede-creator-skills
All skills →
About this skill
What does the suede-signup skill do?

Suede-owned signup conversion discipline. Use when auditing or redesigning account creation, registration, or trial-start flows, including field friction, progressive profiling, identity options, mobile behavior, abandonment, and measurement. NOT FOR: post-signup activation (use suede-onboarding), lead-capture forms (use suede-site-alchemy), or deploying auth and compliance changes without review.

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-signup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going