cc-skill:leadflow-earned-trust

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill ensures all LeadFlow marketing messaging correctly explains how the Earned Trust System works. It enforces that trust tiers (Verified, Trusted, Top Rated) are never sold, keeps them separate from paid visibility products, and uses the Yelp contrast to position LeadFlow as anti-pay-to-play.

who it is for

Marketing teams, copywriters, and product managers writing LeadFlow landing pages, FAQs, positioning materials, or any messaging that mentions the trust system.

when it fires

When you mention earned trust, LeadFlow trust tiers, verification systems, review integrity, FTC compliance, the Yelp problem, or any positioning work comparing LeadFlow to pay-to-play platforms.

say something like

"Write a landing page explaining LeadFlow's Verified tier"
"How do we position Top Rated against Yelp's model?"
"Draft FAQ answers about whether trust badges can be purchased"

what you might get back

Top Rated isn't a badge they bought. It's one we can revoke. A business earns this tier by maintaining trusted status for 12 months, hitting the top 10% in review quality, and completing at least 25 verified jobs. If their performance slips, they lose it. Unlike platforms where paid plans hide negative reviews, every review stays public here. That's why the rating actually means something.

how to know it worked

You'll know it fired correctly because the output clearly separates trust tiers from paid plans (Featured Listing and Premium Profile), never suggests tiers can be purchased, and uses direct language about the pay-to-play rejection.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/leadflow-earned-trust/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when generating LeadFlow content, marketing copy, landing pages, FAQ entries, or any messaging that touches the Earned Trust System (Verified, Trusted, Top Rated tiers). Triggers on "earned trust", "LeadFlow trust", "verification syste

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/leadflow-earned-trust/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when generating LeadFlow content, marketing copy, landing pages, FAQ entries, or any messaging that touches the Earned Trust System (Verified, Trusted, Top Rated tiers). Triggers on \"earned trust\", \"LeadFlow trust\", \"verification system\", \"review integrity\", \"FTC compliance\", \"Yelp problem\", \"pay-to-play\", or any LeadFlow positioning work."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/leadflow-earned-trust/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.