mcpbeat Sign in

Webfluence Agent Skill

Content web architecture framework. Use when diagnosing offer doc usage, content-to-conversion pathways, or why someone isn't getting sales despite traffic.

21k tokens
context cost
the whole folder, loaded on every use
10
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
275
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/nicepkg/ai-workflow --skill webfluence

The instruction itself

22 sections, as written by the author

Webfluence

What This Does

Provides the Webfluence framework for architecting a content web that builds belief before asking for the sale. Use this to diagnose and fix content-to-conversion pathway problems.

The Core Problem This Solves

People send prospects directly to offer docs, VSLs, or sales pages without warming them up first. The offer doc is a closing tool, not a selling tool. Without sufficient "time on brand," conversion fails.

The Golden Rule

Nobody sees the offer doc without seeing content and a warming-up VSL before it, or they've come through a paid workshop or event.

The proper sequence is:

Content → VSL → Offer Doc
    OR
Workshop/Event → Offer Doc

Skipping steps = asking the offer doc to do work it wasn't built for.

The 47-Minute Rule

Research showed buyers consumed approximately 47 minutes of content before saying yes. Use this as a filter: "Is my web architected to deliver enough time on brand before asking for the sale?"

The Core Principle

> When marketing builds belief, persuasion becomes unnecessary.

If your content does the heavy lifting, sales calls become easy (or unnecessary). Prospects arrive pre-sold, feeling like hot referrals.

The Five Layers of a Content Web

Layer 1: CORE (Center)

  • Purpose: Converts belief into buying intent
  • Example: VSL, paid workshop
  • Function: Your 24/7 salesperson that sells while you sleep

Layer 2: MIDDLE RING

  • Purpose: Builds authority and connection
  • Example: YouTube long-form, podcast, in-depth email sequences
  • Function: Deepens belief and establishes expertise

Layer 3: OUTER RING

  • Purpose: Drives reach and awareness
  • Example: Short-form content (Instagram Reels, LinkedIn posts)
  • Function: Entry points that create reach and recall

Layer 4: CONNECTORS

  • Purpose: Links everything together
  • Examples: ManyChat automations, GPT tools, email campaigns
  • Function: Qualifies and nurtures leads, moves traffic between layers

Layer 5: COMPOUNDER

  • Purpose: Keeps everything evergreen
  • Example: YouTube channel as long-tail belief machine
  • Function: When someone discovers one video, they binge the entire channel

Scoring a Content Web (Out of 5)

| Layer | Question |

|-------|----------|

| Coverage | Do you have content for cold, warm, and hot audiences? |

| Consistency | Do you show up rhythmically? (Not frequency, consistency) |

| Conversion | Does every piece of content have a clear CTA leading somewhere? |

| Connection | Does every piece physically link to another? |

| Belief Flow | Does your content build belief, not just awareness? |

The two lowest-scoring areas are usually where the problem lives.

Common Diagnostic Patterns

Pattern: "Sent to offer doc, no sales"

Diagnosis: Skipping steps. Email → Offer doc bypasses content and VSL.

Fix: Content → VSL → Offer doc. The email's job is to get them to content, not the offer doc.

Pattern: "High opens, low clicks, no sales"

Diagnosis: Missing connectors + possible list-offer mismatch.

Fix: Check if CTAs drive to content that builds belief. Check if audience matches offer.

Pattern: "They watched the VSL but didn't apply"

Diagnosis: Insufficient belief-building before VSL, or VSL itself needs work.

Fix: More content touchpoints before VSL. Review VSL for belief-building elements.

Pattern: "I don't have long-form content"

Response: You don't need all layers immediately. Start with what you have:

  • At minimum: Short-form + Email + Chat automation
  • YouTube/podcast can come later
  • Focus on connecting existing content before creating new

Implementation Priority

Don't try to build everything at once. Million Dollar Coach built this over 18+ months:

  • Brand Width first - Repurpose existing content, extend indoctrination sequences
  • Email consistency - Daily or regular rhythm (first cycles will be rough, that's normal)
  • Short-form content - With clear CTAs to tools or longer content
  • Paid workshop - Eliminates freebie chasers, builds belief
  • VSL - Your 24/7 salesperson
  • Long-form (YouTube) - The compounder that creates binge behavior

Key Mindset Shifts

  • From volume to connection: Goal isn't more content, it's connecting what you have
  • From linear to web: Accept that buyers won't follow your planned path
  • From attribution to attention: Stop obsessing over tracking; measure time on brand
  • From perfect to consistent: First attempts will suck; keep exercising the muscle

Point members to these for deeper dives:

  • Brand Width - The foundational concept of time on brand
  • Salesless Experiment - Proof that marketing can replace sales calls
  • The System 2025 - The tactical ladder showing all the pieces
  • 80-20 Content Strategy - Content pillars and structure
  • The Social System - How to turn stories into content
  • VSL Training - How to create your video sales letter

When Answering Questions

  • Identify where they are in the web architecture
  • Diagnose which layer or connection is broken
  • Prescribe the specific fix (not the whole system)
  • Point to relevant training if they need to go deeper

Remember: The offer doc is a closing tool. If someone's sending cold traffic directly to it, that's the problem.

Other skills for the same job

different authors, same section of the catalogue
Internal Comms
by anthropics
vendor ×13

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

6k tokens
Competitive Ads Extractor
by frostant
×10

Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.

2k tokens
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Developer Growth Analysis
by frostant
×6

Analyzes your recent Claude Code chat history to identify coding patterns, development gaps, and areas for improvement, curates relevant learning resources from HackerNews, and automatically sends a personalized growth report to your Slack DMs.

4k tokens
App Store Optimization
by alirezarezvani
×3

Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store

55k tokens scripts
Deeptools
by christophacham
×3

NGS analysis toolkit. BAM to bigWig conversion, QC (correlation, PCA, fingerprints), heatmaps/profiles (TSS, peaks), for ChIP-seq, RNA-seq, ATAC-seq visualization.

21k tokens scripts
Pymatgen
by christophacham
×3

Materials science toolkit. Crystal structures (CIF, POSCAR), phase diagrams, band structure, DOS, Materials Project integration, format conversion, for computational materials science.

26k tokens scripts
Enhance Prompt
by google-labs-code
vendor ×2

Transforms vague UI ideas into polished, Stitch-optimized prompts. Enhances specificity, adds UI/UX keywords, injects design system context, and structures output for better generation results.

3k tokens

How to use it

Copy the folder

Take nicepkg/webfluence from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.