Homepage Conversion Audit
BrianRWagner/ai-marketing-claude-code-skills
Audits a homepage or landing page for conversion in quick, standard or deep mode, scoring it by page type and ending with an impact-ranked action plan.
A skill your agent uses when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content.
Install Trust Signals
$ npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist trust-signals --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/trust-signals .claude/skills/trust-signals && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "trust-signals" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signals into .claude/skills/trust-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-signals", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signalsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist trust-signals --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/trust-signals .agents/skills/trust-signals && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trust-signals" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signals into .agents/skills/trust-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-signals", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist trust-signals --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/trust-signals .cursor/skills/trust-signals && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "trust-signals" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signals into .cursor/skills/trust-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-signals", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/trust-signals--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist trust-signals --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/trust-signals .gemini/skills/trust-signals && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "trust-signals" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signals into .gemini/skills/trust-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-signals", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist trust-signalsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/trust-signals .github/skills/trust-signals && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "trust-signals" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signals into .github/skills/trust-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-signals", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist trust-signals --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/trust-signals .opencode/skills/trust-signals && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "trust-signals" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/trust-signals into .opencode/skills/trust-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trust-signals", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
trust-signals- GitHub stars
- 74k
- Token cost
- ~619 tokens
- SKILL.md length
- 264 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content.
- Applies especially to e-commerce checkouts
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Contact/lead forms
What it does
Trust Signals is an agent skill from thedaviddias/Front-End-Checklist. Use when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content. Use when auditing E-E-A-T or conversion optimization.
Its SKILL.md is about 620 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
It sits in Sales & Support, covering Landing pages, Conversion rate optimization and E-commerce operations. The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Applies especially to e-commerce checkouts
- Contact/lead forms
- YMYL (Your Money
- Your Life) content
Example prompts
- “/trust-signals”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Trust Signals loads about 619 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 264 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 264 words, ~619 tokens.
Download SKILL.mdSave it as
.claude/skills/trust-signals/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- trust-signals
- description
- Use when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content. Use when auditing E-E-A-T or conversion optimization.
- metadata.category
- seo
- metadata.priority
- medium
- metadata.difficulty
- intermediate
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/seo/trust-signals
Show trust signals on key pages
Google's Quality Rater Guidelines explicitly evaluate trustworthiness as a core page quality signal; pages lacking visible trust evidence score lower in manual quality assessments that influence ranking systems.
Quick Reference
- Display trust signals (reviews, certifications, security badges, client logos) near calls-to-action on key pages
- Trust signals are a core component of Google's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness)
- For YMYL pages (health, finance, legal), trust signals are a critical quality signal in Google's Quality Rater Guidelines
- Fake or unverifiable trust badges actively harm credibility — only display genuine, verifiable credentials
Check
On key conversion pages (checkout, contact, pricing, landing pages), check for: security/SSL badges near forms, third-party review platform ratings (Google, Trustpilot), industry certifications, client/partner logos, testimonials with names and photos, money-back guarantee language. Verify all badges are genuine (not just images).
Fix
Add appropriate trust signals to each key page: embed real review widgets from Google/Trustpilot, display relevant certifications with verifiable links, add named testimonials with photos, include security badges near form submission areas. Ensure all trust elements are current and accurate.
Explain
Explain how trust signals affect both user conversion rates and Google's quality assessments, what E-E-A-T means for content quality, and why YMYL pages face higher trust scrutiny from Google's Quality Rater Guidelines.
Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Show trust signals on key pages. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/trust-signals
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/trust-signals of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
Trust Signals next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Trust Signals this skillthedaviddias/Front-End-Checklist | 74k | — | ~619 | Automated safety check: Pass | MIT | |
| Homepage Conversion AuditBrianRWagner/ai-marketing-claude-code-skills | 441 | — | ~1.8k | Automated safety check: Pass | None | |
| Scenario Product Shotsscenario-labs/skills | 946 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Etsy Shop Analyticsnexscope-ai/eCommerce-Skills | 1.1k | — | ~430 | Automated safety check: Pass | MIT | |
| Cro Optimizationognjengt/founder-skills | 447 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Landing Page Generatorbuildfastwithai/gen-ai-experiments | 785 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Scenario Product Shots
scenario-labs/skills
A skill your agent uses when producing product photography with Scenario from a real product photo: e-commerce packshots on white, transparent, or brand backgrounds, lifestyle scenes placing the…
Etsy Shop Analytics
nexscope-ai/eCommerce-Skills
Shop analytics — traffic sources, conversion rates, search terms, top listings performance
Cro Optimization
ognjengt/founder-skills
Analyzes landing pages and provides detailed CRO (Conversion Rate Optimization) recommendations.
Landing Page Generator
buildfastwithai/gen-ai-experiments
Builds a single self-contained HTML landing page from a template with copy frameworks, four themes and SEO meta, then runs bundled audit scripts for conversion and speed.
Cro
Nexus-JPF/note-companion
When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Related
Questions about Trust Signals
What does Trust Signals do?
A skill your agent uses when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content. Trust Signals is an agent skill from thedaviddias/Front-End-Checklist. Use when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content.
When should I use Trust Signals?
Trust Signals fits situations like: applies especially to e-commerce checkouts; contact/lead forms; YMYL (Your Money; your Life) content.
How do I install Trust Signals in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a claude-code`. Or copy the skill folder (skills/trust-signals in thedaviddias/Front-End-Checklist) into .claude/skills/trust-signals in your project. Claude Code loads it when a task matches its description.
How do I install Trust Signals in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a codex`. Or copy the skill folder (skills/trust-signals in thedaviddias/Front-End-Checklist) into .agents/skills/trust-signals in your project. Codex loads it when a task matches its description.
Can I use Trust Signals in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill trust-signals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trust-signals, .gemini/skills/trust-signals, .github/skills/trust-signals and .opencode/skills/trust-signals in your project.
What does Trust Signals need to run?
SKILL.md names no scripts, command-line tools or credentials: Trust Signals is instructions for the agent only.
Does Trust Signals access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is Trust Signals safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Trust Signals use?
Trust Signals is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Trust Signals use?
About 619 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Trust Signals?
Skills that share tags, products or a category with Trust Signals: Homepage Conversion Audit (BrianRWagner/ai-marketing-claude-code-skills, 441 stars), Scenario Product Shots (scenario-labs/skills, 946 stars), Etsy Shop Analytics (nexscope-ai/eCommerce-Skills, 1.1k stars) and Cro Optimization (ognjengt/founder-skills, 447 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trust Signals?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.