saas-landing-pages
Skill68 starsChanged 25 days agoMITView on GitHub
Creates complete SaaS landing page drafts using 7 framework templates. Use when the user wants to create a "homepage," "product page," "pricing page," "comparison page," "integration page," "use case page," or "solution page.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- jonbishop1/saas-marketing-skillstheir own version, first seen Oct 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jonbishop1/saas-marketing-skills★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- ad-creativeSkill
- agent-skill-builderSkill
- ai-content-generationSkill
- ai-humanizerSkill
- case-study-builderSkill
- clay-gtm-outboundSkill
- competitive-intelligenceSkill
- copy-anatomySkill
- customer-segmentsSkill
- domain-healthSkill
- experimentationSkill
- icp-personaSkill
- landing-pageSkill
- lifecycle-marketing-campaignsSkill
- marketing-advantagesSkill
- marketing-product-ideasSkill
- n8n-automationSkill
- obsidian-opsSkill
- outbound-engineSkill
- performance-marketingSkill
- portfolio-positioningSkill
- press-releaseSkill
- product-launch-gtmSkill
- product-marketing-metricsSkill
- product-messagingSkill
- product-onboarding-activationSkill
- product-positioningSkill
- prospect-scraperSkill
- remotionSkill
- seo-auditSkill
- skill-to-promptSkill
- storytelling-frameworkSkill
- vibe-codingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Brand detection: Ask which brand or client this page is for, and save it under that brand's or client's folder.
- Distinctive: line 44
Confirm page type: before writing
- Distinctive: line 47
Ask clarifying questions: if info missing
- Distinctive: line 97
Follow framework structure exactly
- Distinctive: line 98
No generic filler text
- Distinctive: line 99
Use [Product Name] placeholders if info missing
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SaaS Landing Pages Assistant
Generate complete, section-by-section landing page drafts using James Praise's Landing Page Framework System for SaaS products.
Output Protocol
This skill saves drafts to your notes or vault as markdown before any export.
- Draft destination:
[your-drafts-folder]/[Brand]/YYYY-MM-DD - [page-slug]/ - Hub file:
00 - [Page Title].mdwithtype: creative-asset,asset_type: landing-page,skill: /saas-landing-pages - Draft file:
01 - Draft.mdwithtype: creative-draft - Default export format:
docx - Export triggers: "export to docx", "export to pdf", "export both", "ready for delivery"
Brand detection: Ask which brand or client this page is for, and save it under that brand's or client's folder.
Document integrity. Write every draft this skill saves as a current-state document. When feedback or new facts arrive, rewrite the affected section in place and fix anything elsewhere in the file (and in related files) that the change contradicts. Never append dated addenda, update blocks, or change narration to a draft. Record each revision as one short line in the hub, and before finishing, reread every file you touched and remove stale claims, duplicate sections, and change narration.
No .docx or .pdf is produced on first pass. Present the draft in chat for refinement, write the approved version to your notes as markdown, and only export to .docx/.pdf when explicitly triggered.
When to Use
- User wants any type of SaaS landing page
- User mentions: homepage, product page, feature page, pricing page, comparison page, vs page, integration page, use case page, solution page, persona page
Page Types
- Homepage / Main Landing Page: Primary brand and product page
- Product / Feature Page: Single feature or product deep-dive
- Solution / Persona Page: Industry, team, or persona-specific
- Use Case Page: Specific workflow or job-to-be-done
- Comparison Page: Competitor differentiation (vs pages)
- Integration Page: Partner/tool integration showcase
- Pricing Page: Plans, tiers, and conversion
Instructions
- Confirm page type before writing
- Collect inputs based on page type
- Generate complete draft following framework structure
- Ask clarifying questions if info missing
General Inputs (All Pages)
- Product/Brand Name
- Product Description (1-2 lines)
- Target Audience / Primary User
- Key Benefits or Value Proposition
- Visual/Product Type (software, app, tool, platform)
- Tone Preference (professional, friendly, bold, premium)
- Primary CTA (Start Free, Book Demo, Get Started)
Page-Specific Inputs
| Page Type | Additional Inputs |
| Product/Feature | Main feature name, 3-5 sub-features, core outcomes |
| Solution/Persona | Persona/industry/team, main pain points, key benefits for group |
| Use Case | Specific workflow, main steps, expected results |
| Comparison | Competitor name, differentiators, switching proof |
| Integration | Partner name, what integration enables, key use cases |
| Pricing | Pricing tiers, highlights, proof of value, billing info |
Output Format
Generate as Markdown with:
- Bold section headers
- Each section: Headline, Description, CTA (if applicable)
- Bullet points for features/benefits
- Bold key phrases and product names
- Clear spacing between sections
Section Structure
Each section must include:
- Heading: Clear and action-driven
- Description/Subtext: 2-4 lines max
- Visual note: Where relevant
- CTA: Where applicable
Style Guidelines
- Clear, direct, outcome-oriented
- Conversational but professional
- Short sentences, persuasive rhythm
- Include social proof and data
- Adapt tone to page type (aspirational for Homepage, factual for Comparison)
Constraints
- Follow framework structure exactly
- No generic filler text
- Use [Product Name] placeholders if info missing
- Pause and ask if user input incomplete
- Final output must be design-layout ready
- Hyphen rules: Hyphens connect words; en dashes for ranges; em dashes for thought breaks
Reference
See references/page-frameworks.md for detailed templates per page type.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.