/disclosure
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
$ npx -y skills add kostja94/marketing-skills --skill disclosure --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/disclosure
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
disclosure.SKILL.mdname: disclosure-page-generator
description: 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.
metadata:
version: 1.0.1
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: 1. **Type**: Affiliate, sponsored, paid partnership, referral 2. **Scope**: Site-wide, specific pages, or both 3. **Regions**: US (FTC), EU, other 4. **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)
Related Skills
- **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
Read more
name: disclosure-page-generator description: 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. metadata: version: 1.0.1
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: 1. **Type**: Affiliate, sponsored, paid partnership, referral 2. **Scope**: Site-wide, specific pages, or both 3. **Regions**: US (FTC), EU, other 4. **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)
Related Skills
- **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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill