skynet-site — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited skynet-site (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Goal: ship a client-ready demo + pitch in one session. Not template fill. Not generic. Niche-tuned, conversion-optimized, deploy-ready, SEO-safe.
Source patterns: 9 shipped builds. See case-studies.md for full table.
If brief missing → use AskUserQuestion. Don't proceed without niche + brief.
Launch 3 Agent calls in ONE message:
Output → docs/RESEARCH.md. Use it. Don't ignore it.
Pick palette + font pair from niche match table (see design-tokens.md). DO NOT default to navy+gold for everything — that's corporate, not luxury. Wedding = warm beige + claret + Instrument Serif. Medical = forest + mint + Cormorant Garamond. Premium health = bone + sage OR cobalt + acid yellow.
Output 1 design.md w/ tokens, never 5 random variants UNLESS budget ≥$1K AND brief unclear (then ship 5 variants like the health-brand play).
| Budget / scope | Stack |
|---|---|
| <$300, fast | Static HTML+Tailwind CDN+vanilla JS, Vercel |
| $300-1K, premium | Pure HTML/CSS/JS, Vercel, no build step (no-build premium pattern) |
| $1K+, hero anim | Next.js 15 + React 19 + Tailwind 3.4 + R3F v9 + Drei v10 + Framer Motion + Lenis |
| WordPress brief | Build Vercel demo first. Port to Divi/Kadence Phase 2 (coach-funnel pattern) |
Never ship raw template clone — always niche-tune palette + fonts + copy + photos.
ALWAYS ship 3 different landing-page variants per client. No exceptions. Client picks 1 → polish + ship. Pattern validated across a home brand (5 variants → V4 picked), a health brand (5 variants), a CPG brand (5 variants w/ floating switcher), a wedding brand (3 iterations).
Why: Client cannot articulate taste in advance. Showing 3 cuts the back-and-forth from 5+ revisions to 1 pick + 1 polish round. Doubles close rate vs single-variant pitches.
3 variants must differ on AXIS not detail:
| Variant | Axis | Example |
|---|---|---|
| V1 — Editorial | Magazine grid · serif display · whitespace-heavy | wedding-brand modern v3 |
| V2 — Cinematic | R3F 3D hero OR MP4 loop · dark · animation-forward | health-brand 3D helix |
| V3 — Bold / Minimal | Glassmorphic OR brutalist · single accent · type-driven | health-brand magazine OR Aesop |
Pick 3 axes that span the niche's taste range. NEVER 3 variants that look ~80% the same — defeats the point.
Every multi-variant build = sticky variant switcher visible to client. Default placement: top-right header OR floating top-right pill (per recipes/variant-switcher.md).
Spec:
position: fixed; top: 20px; right: 20px; z-index: 99#v1 #v2 #v3 so client can share specific variant linkLive examples:
example.vercel.app grid icon top-rightexample.vercel.app <VariantNav> topCode recipe: recipes/variant-switcher.md.
Order non-negotiable. Buyers expect this rhythm.
FAQPage schema.Plus: exit-intent modal (desktop, 1× session), sticky header CTA after hero scrolls past.
Wedding/luxury signatures — reusable:
→ Inquire — begin your vows)Skip if niche = HVAC/plumbing (overdesigned hurts conversion). Apply heavily if niche = wedding/luxury/wellness/photography.
tel:+1... w/ click trackingrobots.txt + sitemap.xml + vercel.json (cache headers + security)noindex,nofollow 90 days minimum (Feb 2026 SpamBrain)# 1. Repo
gh repo create <niche>-demo --public --license mit --description "..."
git init && git add . && git commit -m "feat: initial demo"
git push
# 2. Vercel
vercel --prod
# Confirm clean alias: <niche>-demo.vercel.appSend pitch using pitch-template.md. Always:
scope-questions.md per niche)GITHUB/<niche>-demo/
├── index.html (or app/ if Next.js)
├── docs/
│ ├── RESEARCH.md # Phase 1 output
│ ├── DESIGN-TOKENS.md # Phase 2 output
│ ├── CLIENT-PITCH.md # full pitch log + scope Qs
│ ├── CLIENT-MESSAGE.md # verbatim message sent
│ └── DIVI-PORT-MAP.md # if WP brief
├── public/
│ ├── og.png
│ ├── favicon.svg
│ └── photos/ # niche-real, NOT Picsum
├── README.md # MIT, "fork to use"
├── vercel.json
├── robots.txt
├── sitemap.xml
└── package.json (if Next.js)feedback-speculative-build-pitch. ~10× higher close rate vs cold proposal.feedback-no-fake-claims. Real builds, real wins, real photos only.python _pick-next.py from your images folder. Never by eye.case-studies.md — 9 shipped client builds, full table w/ stack + outcomedesign-tokens.md — niche → palette + font pair lookupscope-questions.md — 5-8 Qs per niche templatepitch-template.md — verbatim message structurecompetitor-research-template.md — parallel agent promptsFor those: skip skill, build direct.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.