How to use the Disclaimers for Sensitive Content agent skill

What the disclaimers skill makes the agent do

Agent skills are folders of instructions that an AI agent loads when a task matches them. This one comes from the Front-End Checklist project and is licensed under MIT. Its description says it is used for auditing YMYL content pages (Google's term for 'Your Money or Your Life' topics such as health, finance, legal and safety) for trust signals, generating disclaimer copy for medical or financial content, and reviewing affiliate disclosure requirements under FTC or ASA guidelines.

In practice the agent checks three things on each sensitive page: whether a visible disclaimer says the content is not professional advice, whether an affiliate disclosure appears before the first affiliate link, and whether the disclaimer sits prominently rather than in a footer or after long content. It can also suggest sample wording for medical, financial, legal and affiliate pages.

Install the disclaimers skill

Download the ZIP for this skill from the page where you found it, then unzip it. You can install it in one of two places. For a personal setup, put the unzipped folder in ~/.claude/skills/. For a single project, put it in that project's .claude/skills/ folder.

If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.

• Personal: ~/.claude/skills/disclaimers
• Project only: .claude/skills/disclaimers inside your project folder
• Claude apps: Settings → Capabilities → Skills, then upload the skill

Check what the folder contains

The skill folder holds two files. SKILL.md contains the instructions and the metadata that tells the agent when to use the skill. references/rule.md holds the longer implementation notes, including code examples, which the agent can read when it needs more detail.

Look at both files before relying on the skill for a client project, so you know exactly what guidance the agent is working from.

• SKILL.md: the main instructions and trigger description
• references/rule.md: extended guidance and HTML examples

Trigger the skill with natural requests

You do not need a special command. Describe the task in ordinary language and mention the content type. The skill's description covers auditing YMYL pages, generating disclaimer copy for medical or financial content, and reviewing affiliate disclosures under FTC or ASA rules, so requests along those lines should match it.

• Audit this health article for trust signals and visible disclaimers.
• Write a disclaimer for our financial education article.
• Check whether our affiliate post discloses links before the first affiliate link.
• Review this legal information page for a disclaimer near the top.
• Suggest disclaimer wording for a safety guide and where to place it in the template.

Use it in a real audit

Point the agent at a page or template and ask for the checks. The source's checklist asks three questions for each sensitive page: is there a visible non-advice disclaimer, is an FTC-compliant affiliate disclosure placed before the first affiliate link, and is the disclaimer placed prominently. The fix list then covers adding a disclaimer block near the top, marking it with an ARIA role or a distinctive style, and using the sample wording as a starting point.

For developers, the code review step scans page content for YMYL keywords and checks that a disclaimer element sits near the top of the main or article element, and that affiliate pages disclose before the first link with a referral parameter or affiliate domain.

• Confirm the disclaimer appears above the sensitive material, not in the footer.
• Confirm affiliate disclosure text comes before the first affiliate link.
• Mark the disclaimer with an ARIA role or a visually distinctive style.
• Replace the sample wording with text reviewed for your own business.

Safety, requirements and limits

The skill lists no required tools or packages. It does not run scripts and does not use the network, so it works by reading and writing text in your project. Treat its output as a checklist and draft copy based on Google's quality guidelines and FTC/ASA disclosure rules, not as legal advice. The sample disclaimers are generic, and the skill cannot know your jurisdiction or obligations, so have a qualified lawyer review anything you publish.

The skill also does not guarantee ranking results. It links disclaimers to Google's E-E-A-T framework, but no outcome is promised.

• Requires: nothing listed
• Runs scripts: no
• Uses network: no
• Not legal advice; have a qualified lawyer review final wording
• No ranking gains are guaranteed