mcpbeat

Disclosure Page Generator

kostja94/disclosure-page-generator

When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.

663 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
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/kostja94/marketing-skills --skill disclosure-page-generator

The instruction itself

9 sections, as written by the author

Pages: Disclosure

Guides disclosure pages for affiliate links, sponsored content, and paid partnerships. Required for FTC compliance (US) and similar regulations. Builds trust and reduces legal risk.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for affiliate/partnership model.

Identify:

  • Type: Affiliate, sponsored, paid partnership, referral
  • Scope: Site-wide, specific pages, or both
  • Regions: US (FTC), EU, other
  • Placement: Standalone page; link from footer, near affiliate content

Page Structure

| Section | Purpose |

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

| Headline | "Disclosure" or "Affiliate Disclosure" |

| Summary | We may earn from qualifying purchases; links may be affiliate |

| Details | How it works; what we recommend; no extra cost to you |

| Transparency | We only recommend products we believe in |

| Contact | Questions; link to contact |

Best Practices

FTC Compliance (US)

  • Clear and conspicuous: Not buried; visible near affiliate content
  • Before the click: Disclosure before user clicks affiliate link
  • Plain language: "We may earn a commission" not legalese

Placement

  • Footer link: "Disclosure" in every page footer
  • Near content: Short disclosure above/below affiliate sections
  • Standalone page: Full disclosure at /disclosure

Content

  • Honest: Explain relationship; no misleading claims
  • Concise: One page; avoid excessive length
  • Update: When model changes

Output Format

  • Headline and summary
  • Full disclosure copy
  • Placement guidance (footer, in-content)
  • Legal note (consult lawyer for jurisdiction)
  • affiliate-page-generator: Affiliate program page; link to disclosure
  • terms-page-generator: Terms may reference disclosure
  • privacy-page-generator: Privacy for data; disclosure for commercial
  • landing-page-generator: Disclosure near affiliate LPs

How to use it

Copy the folder

Take kostja94/disclosure-page-generator 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.