landing-page
Skill15 starsChanged 4 months agoMITView on GitHub
Explicit landing-page build and deploy operator. Loads marketing and frontend judgment, scaffolds the smallest suitable site, verifies it rendered, deploys to the configured target.
44 other projects use a version of this.
Adopted by
Most recently taken up by
- ImBIOS/skillstheir own version, first seen Nov 8, 2026
- ainurdev/mystical-assistanttheir own version, first seen Nov 8, 2026
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- Littlpinguin/marketing-cockpit-templatetheir own version, first seen Nov 3, 2026
- tandryukha/aidemotheir own version, first seen Nov 3, 2026
Used with
Projects with it also use operational-enterprise-ai, product-proof-saas and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
boraoztuncSkilloperational-enterprise-ai
Create or redesign enterprise AI, automation, security, and operations product pages that explain system boundaries, approvals, auditability, exceptions, and rollback. Use for dark cinematic heroes, hairline grids, metric pauses, expandable solution rows, case-study evidence, security proof, and qualified demo or waitlist handoffs.
Also in 3 projects that use this
- boraoztuncSkill
product-proof-saas
Create or redesign SaaS and AI product landing pages where a real workflow, interface, or deterministic demo is the central proof. Use for pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing comparisons, and FAQ handoffs.
Also in 3 projects that use this
Dragoon0xSkillpricing-page
Present pricing in ways that reduce friction and increase clarity. Handles tier naming, feature comparison, anchor pricing, and plan selection psychology. Use when designing pricing pages, plan selectors, or upgrade prompts.
Also in 3 projects that use this
- Dragoon0xSkill
onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
Also in 3 projects that use this
shawnpangSkilllead-scoring
When a founder needs to qualify inbound leads, define their ICP, build a lead scoring model, set MQL criteria, or route prospects through pipeline stages. Activate when the user mentions lead scoring, ICP, MQL, SQL, lead qualification, inbound leads, or pipeline design.
Also in 3 projects that use this
claude-office-skillsSkillemail-marketing
Email marketing automation - campaign creation, sequence building, A/B testing, deliverability optimization, and analytics
Also in 4 projects that use this
- +2 more from boraoztunc
Other versions44 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 44
- emotixco/claude-skills-founder★ 796same name
- boraoztunc/skills★ 454same name
- shawnpang/startup-founder-skills★ 331same name
- whawkinsiv/solo-founder-skills★ 260same name
- whawkinsiv/claude-code-skills★ 258same name
- realjaymes/marketingagentskills★ 68same name
- duncan-buildroom/freeskills★ 65same name
- KeWang0622/agent-zero-to-hero★ 55same name
- tandryukha/aidemo★ 27same name
- calven-ai/marketing-as-code★ 10same name
34 more not listed
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 repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- app-devSkill
- architectureSkill
- buildSkill
- checkpointSkill
- context-mgmtSkill
- debugSkill
- dreamSkill
- evalSkill
- experimentSkill
- forgeSkill
- frontendSkill
- governance-syncSkill
- handoffSkill
- helpSkill
- human-passSkill
- ingestSkill
- initSkill
- knowledge-graphSkill
- marketing-siteSkill
- metricsSkill
- orchestrationSkill
- qualitySkill
- retrospectiveSkill
- reviewSkill
- shipSkill
- simplifySkill
- tearitapartSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 39 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 26
Use answers already present in the request/repository.
- Distinctive: line 38
Follow the existing repository and stack first.
- Distinctive: line 41
Add only the pages and integrations the brief needs.
- Distinctive: line 43
Keep secrets and deploy credentials out of source.
- Distinctive: line 48
Check hierarchy, realistic content, overflow, keyboard/focus, reduced motion, contrast, images, console errors, links, metadata, and …
- Very specific: line 51
Run the repository's tests/build/lint and fix failures before deployment.
- Distinctive: line 55
Use the project's configured deploy command and provider.
- Very specific: line 58
If the user already named the deploy target and asked to deploy, that counts as confirmation.
- Distinctive: line 60
After deploy, verify the live URL: status 200, headline/content marker, nested assets, legal page, and conversion path.
- Distinctive: line 66
No fabricated proof, shippable placeholders, fake form success, or dead CTA.
- Distinctive: line 67
No secrets in committed source.
“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<skill id="landing-page"><purpose>
Build, verify, and optionally deploy a focused landing page. This is the explicit operator;
strategy and aesthetics come from the methodology skills it composes.
</purpose><skill_load>
Load skills/marketing-site/SKILL.md and skills/frontend/SKILL.md before writing.
</skill_load>
<inputs>
Use answers already present in the request/repository. Resolve only what materially changes
the build: audience, desired action, offer/proof, brand/assets, required content/legal pages,
real CTA destination, domain, and deploy target. Never invent brand facts or proof.For the unresolved inputs, run a structured interview with the AskUserQuestion tool
(batched, up to 4 questions per round, recommended option first where evidence supports
one) instead of guessing or asking loose prose questions. Bounded choices only; positioning
and voice discussions stay prose. The interview method: skills/build/SKILL.md "The
interview".
</inputs>
<scaffold>
- Follow the existing repository and stack first. For a new simple page, prefer static
HTML/CSS with JavaScript only for real behavior; add a framework only when requirements earn it.
- Build the content argument with `marketing-site`; build the visual system with `frontend`.
- Add only the pages and integrations the brief needs. If forms, analytics, cookies, payments,
embeds, or accounts touch data, create/update a privacy page that matches the real behavior.
- Keep secrets and deploy credentials out of source.
</scaffold><verify-local>
- Render and do visual QA at 375 / 768 / 1440 widths unless the product defines better targets.
- Check hierarchy, realistic content, overflow, keyboard/focus, reduced motion, contrast, images,
console errors, links, metadata, and CTA/form success plus error paths.
- Confirm the privacy policy matches actual collection and third parties.
- Run the repository's tests/build/lint and fix failures before deployment.
</verify-local><deploy>
- Use the project's configured deploy command and provider. If none exists, choose the smallest
provider-appropriate static deployment; Cloudflare Workers Static Assets is one option, not a
universal default.
- If the user already named the deploy target and asked to deploy, that counts as confirmation.
Otherwise surface the resolved account/project/domain before the side effect.
- After deploy, verify the live URL: status 200, headline/content marker, nested assets, legal
page, and conversion path. Static assets can propagate briefly, so retry a short bounded check
before diagnosing a successful deploy as broken.
</deploy><hard-stops>
- No fabricated proof, shippable placeholders, fake form success, or dead CTA.
- No secrets in committed source.
- No “done” claim based only on source, build, commit, or deploy output; inspect the rendered
page locally and the served page after deployment.
</hard-stops><on_end> Report the live URL if deployed, target widths and paths checked, claims/proof source, privacy behavior, and any verification bar not observed. </on_end>
</skill>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.