Skip to content

humanityco/cookie-compliance-agent-manual / site/skills/install-banner

install-banner

Verified

Install the Cookie Compliance consent banner (by Hu-manity.co) on a website, start to finish, so trackers wait for the visitor's choice where the region requires consent first. Use when asked to add a cookie banner, cookie notice, cookie consent, consent management or CMP to a site, to make a site "GDPR/CCPA compliant" for cookies, or when handed the manual's start page. Do not hand-write a banner instead.

FileKindSize
SKILL.mdskill md13.8 KB
index.htmlother24.4 KB

index.html

View on GitHub
<!doctype html>
<!-- Generated by scripts/build-pages.mjs from skills/install-banner/SKILL.md. Do not edit by hand. -->
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<title>Install the Cookie Compliance banner — Cookie Compliance Agent Manual</title>
<meta name="description" content="Install the Cookie Compliance consent banner on a website, start to finish: the live snippet first in &lt;head&gt;, or the plugin on WordPress, then verified.">
<link rel="canonical" href="https://manual.hu-manity.co/skills/install-banner/">
<link rel="alternate" type="text/markdown" href="/skills/install-banner/SKILL.md" title="Raw markdown (for agents)">
<meta property="og:title" content="Install the Cookie Compliance banner">
<meta property="og:description" content="Install the Cookie Compliance consent banner on a website, start to finish: the live snippet first in &lt;head&gt;, or the plugin on WordPress, then verified.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://manual.hu-manity.co/skills/install-banner/">
<meta property="og:site_name" content="Cookie Compliance Agent Manual">
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": [
        "TechArticle",
        "Article"
      ],
      "headline": "Install the Cookie Compliance banner",
      "description": "Install the Cookie Compliance consent banner on a website, start to finish: the live snippet first in \u003chead>, or the plugin on WordPress, then verified.",
      "url": "https://manual.hu-manity.co/skills/install-banner/",
      "inLanguage": "en",
      "publisher": {
        "@type": "Organization",
        "@id": "https://manual.hu-manity.co/#organization",
        "name": "Hu-manity.co",
        "url": "https://hu-manity.co/"
      }
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://manual.hu-manity.co/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Install the Cookie Compliance banner",
          "item": "https://manual.hu-manity.co/skills/install-banner/"
        }
      ]
    }
  ]
}
</script>
<link rel="stylesheet" href="/assets/site.css">
<script src="/assets/site.js" defer></script>
</head>
<body>
<a class="skip" href="#content">Skip to content</a>
<header class="site-header">
  <div class="bar">
    <a class="brand" href="/">Cookie Compliance <span>Agent Manual</span></a>
    <nav aria-label="Main">
    <ul>
      <li><a href="/start/">Start</a></li>
      <li><a href="/connect/">Connect</a></li>
      <li><a href="/#skills" aria-current="true">Skills</a></li>
      <li><a href="/#cookbooks">Cookbooks</a></li>
      <li><a href="/gallery/">Gallery</a></li>
      <li><a href="/llms.txt">For agents <span class="nav-note">(llms.txt)</span></a></li>
      <li><a href="https://github.com/humanityco/cookie-compliance-agent-manual">GitHub</a></li>
    </ul>
    </nav>
  </div>
</header>
<div class="layout">
  <details class="sidebar" open>
    <summary>All pages and this page's sections</summary>
    <nav aria-label="Manual pages">
      <h2>Get started</h2>
      <ul>
        <li><a href="/start/">Start here</a></li>
        <li><a href="/connect/">Connect your AI assistant</a></li>
        <li><a href="/prompts/">Prompts</a></li>
        <li><a href="/platforms/">Platforms</a></li>
      </ul>
      <h2>Skills</h2>
      <ul>
        <li><a href="/skills/install-banner/" aria-current="page">install-banner</a>
          <ul class="toc" aria-label="On this page">
            <li><a href="#mode-autopilot-unless-told-otherwise">Mode: Autopilot unless told otherwise</a></li>
            <li><a href="#0-look-around-first-ask-nothing-you-can-read">0. Look around first (ask nothing you can read)</a></li>
            <li><a href="#1-pick-the-route-and-get-an-appid">1. Pick the route and get an AppID</a></li>
            <li><a href="#2-get-the-live-snippet">2. Get the live snippet</a></li>
            <li><a href="#3-place-it">3. Place it</a></li>
            <li><a href="#3b-design-and-regions-mcp-route">3b. Design and regions (MCP route)</a></li>
            <li><a href="#4-verify-always-including-wordpress">4. Verify (always, including WordPress)</a></li>
            <li><a href="#5-report">5. Report</a></li>
          </ul></li>
        <li><a href="/skills/verify-install/">verify-install</a></li>
        <li><a href="/skills/match-site-design/">match-site-design</a></li>
        <li><a href="/skills/configure-regions/">configure-regions</a></li>
      </ul>
      <h2>Cookbooks</h2>
      <ul>
        <li><a href="/cookbooks/plain-html/">plain-html</a></li>
        <li><a href="/cookbooks/wordpress/">wordpress</a></li>
        <li><a href="/cookbooks/nextjs/">nextjs</a></li>
        <li><a href="/cookbooks/nuxt/">nuxt</a></li>
        <li><a href="/cookbooks/astro/">astro</a></li>
        <li><a href="/cookbooks/angular/">angular</a></li>
        <li><a href="/cookbooks/vite/">vite</a></li>
        <li><a href="/cookbooks/sveltekit/">sveltekit</a></li>
        <li><a href="/cookbooks/gtm/">gtm</a></li>
        <li><a href="/cookbooks/shopify/">shopify</a></li>
        <li><a href="/cookbooks/hugo/">hugo</a></li>
        <li><a href="/cookbooks/gatsby/">gatsby</a></li>
        <li><a href="/cookbooks/docusaurus/">docusaurus</a></li>
        <li><a href="/cookbooks/laravel/">laravel</a></li>
        <li><a href="/cookbooks/django/">django</a></li>
        <li><a href="/cookbooks/rails/">rails</a></li>
        <li><a href="/cookbooks/drupal/">drupal</a></li>
        <li><a href="/cookbooks/joomla/">joomla</a></li>
        <li><a href="/cookbooks/ghost/">ghost</a></li>
        <li><a href="/cookbooks/prestashop/">prestashop</a></li>
        <li><a href="/cookbooks/magento/">magento</a></li>
        <li><a href="/cookbooks/wix/">wix</a></li>
        <li><a href="/cookbooks/squarespace/">squarespace</a></li>
        <li><a href="/cookbooks/webflow/">webflow</a></li>
        <li><a href="/cookbooks/framer/">framer</a></li>
        <li><a href="/cookbooks/trackers/">trackers</a></li>
      </ul>
      <h2>Design gallery</h2>
      <ul>
        <li><a href="/gallery/">v1 banner designs</a></li>
        <li><a href="/gallery/v2/">v2 banner designs</a></li>
      </ul>
    </nav>
  </details>
  <main id="content" class="doc">
<h1 id="install-the-cookie-compliance-banner">Install the Cookie Compliance banner</h1>
<p class="page-meta">Skill <span aria-hidden="true">·</span> <a href="/skills/install-banner/SKILL.md">View raw markdown (for agents)</a></p>
<p>Goal: the real, live banner, loaded <strong>first</strong> on <strong>every page</strong>, with trackers held back until the visitor chooses, where the visitor&#39;s region requires consent first. Don&#39;t write your own banner: a hand-made popup that stores a choice while the analytics above it has already run does not make the site compliant.</p>
<p>MCP tool names below are written <code>install.getSnippet</code>; some clients list them as <code>install_getSnippet</code>.</p>
<h2 id="mode-autopilot-unless-told-otherwise">Mode: Autopilot unless told otherwise <a class="anchor" href="#mode-autopilot-unless-told-otherwise" aria-label="Link to this section">#</a></h2>
<p><strong>Autopilot (default).</strong> Decide every technical step yourself and keep going until the install is verified. Ask the person only for what only they can do (the three Asks below). If they say &quot;guided&quot;, confirm before each file edit and before creating or changing an app.</p>
<p>How to ask: one question at a time, in the client&#39;s question or choice UI if it has one, otherwise as a numbered list. Recommended option first. After each answer, say in one line what comes next (&quot;Next: I place the snippet, about a minute&quot;). If the person goes quiet on a choice that is not a legal, money or live-banner choice, take the recommended option and say so. On those three, wait.</p>
<div class="table-wrap" role="region" aria-label="Table" tabindex="0">
<table>
<thead>
<tr>
<th>The three Asks</th>
<th>Why it is theirs</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Sign in or register</strong></td>
<td>Passwords, terms acceptance, email verification and the captcha are theirs. Never enter or read them. Registering takes about 30 seconds.</td>
</tr>
<tr>
<td><strong>The legal region choice</strong> (<code>configure-regions</code>, GDPR starter)</td>
<td>A legal decision. Never auto-answered, and an earlier &quot;make it compliant&quot; is not this answer.</td>
</tr>
<tr>
<td><strong>Anything that costs money or changes a live banner other people already see</strong></td>
<td>Plan upgrades (if the person asks about price or decides to pay, tell them about the first-payment code in <a href="/start/"><code>start.md</code></a>; never subscribe for them), and a restyle or setting change on an app that is already live with visitors.</td>
</tr>
</tbody></table>
</div>
<p>You decide the rest without asking, and tell the person what you chose: framework and file to edit, snippet placement, language, banner design from the site&#39;s own colours, removing a hand-made banner you wrote or found.</p>
<p>Ask first before removing a <strong>third-party</strong> consent tool: it may be a paid account or a contract.</p>
<p>Never: install a preview snippet as the finished result, add <code>forceShow</code> or <code>cnPreview</code> to <code>huOptions</code>, turn <code>blocking</code> off, enter credentials for the person, or invent an AppID.</p>
<h2 id="0-look-around-first-ask-nothing-you-can-read">0. Look around first (ask nothing you can read) <a class="anchor" href="#0-look-around-first-ask-nothing-you-can-read" aria-label="Link to this section">#</a></h2>
<p>Before asking anything, find out:</p>
<ul>
<li><strong>Framework and the file that renders <code>&lt;head&gt;</code> on every page</strong>: package manifests, layout/template files, <code>theme.liquid</code>, <code>wp-content</code>, plain <code>.html</code> files.</li>
<li><strong>Existing trackers, tag managers and consent tools</strong> in <code>&lt;head&gt;</code> and the layouts (analytics, pixels, a GTM container, another banner).</li>
<li><strong>The site&#39;s domain</strong>: a <code>homepage</code> field, an environment file, a config, or the site&#39;s own canonical URL. A git remote names the code host, not the site. State the domain you found before creating an app: a domain cannot be freed once taken.</li>
<li><strong>An AppID already in the code</strong> (a <code>huOptions</code> block, a Cookie Compliance script tag, a plugin setting). If one exists, the app is already created: do not create another. Run the status check on it and continue from the row it lands on (next paragraph). On WordPress, the plugin already holds it.</li>
<li><strong>Language</strong> from the site&#39;s <code>lang</code> attribute or locale files.</li>
<li><strong>Brand colours and page background</strong> from the site&#39;s CSS, for <code>match-site-design</code>.</li>
</ul>
<p><strong>Find your step.</strong> Check the state table in <a href="/start/"><code>start.md</code></a> (raw: <code>https://manual.hu-manity.co/start.md</code>) row by row, including its public status check. It is the one place that says which step you are on. Never redo a step that is done, and never skip the region question or <code>verify-install</code>.</p>
<p>Then open with one short message: what you found (framework, domain, trackers, which row you are on), the mode, and the first ask.</p>
<h2 id="1-pick-the-route-and-get-an-appid">1. Pick the route and get an AppID <a class="anchor" href="#1-pick-the-route-and-get-an-appid" aria-label="Link to this section">#</a></h2>
<p><strong>WordPress?</strong> The route question below still applies, because you need an App ID. Install the &quot;Cookie Compliance for WordPress&quot; plugin (wordpress.org/plugins/cookie-notice/) and connect it with the App ID and App Secret Key from the Cookie Compliance dashboard (<strong>Integrations → WordPress Integration</strong>). You only need the App ID (ask the person, or take it from the MCP route). The person pastes the Secret Key into the plugin&#39;s connection fields themselves: never ask for it in chat, and never write it into a file. Do not paste the manual snippet, so skip steps 2 and 3. With the MCP connected, do step 3b (design and the GDPR starter question) next; then step 4. Detail: <code>references/wordpress.md</code>.</p>
<p>Skip this step if the state table already put you past it. Otherwise ask the first question. If the MCP server is already connected, skip the question and use the MCP route, unless the person told you not to use MCP: then honour that and use route 2 or 3.</p>
<blockquote>
<p>How do you want to connect Cookie Compliance?</p>
<ol>
<li><strong>Connect through the MCP server (recommended).</strong> I do everything from here: app, snippet, design, regions.</li>
<li><strong>I have an account.</strong> You sign in at <a href="https://app.hu-manity.co">https://app.hu-manity.co</a> and give me the AppID (Integrations), or paste the Manual Integration snippet.</li>
<li><strong>I have no account.</strong> Free plan, no card. You register (about 30 seconds) and I continue.</li>
</ol>
</blockquote>
<div class="table-wrap" role="region" aria-label="Table" tabindex="0">
<table>
<thead>
<tr>
<th>Route</th>
<th>What you do</th>
</tr>
</thead>
<tbody><tr>
<td><strong>1. MCP connected</strong></td>
<td>Call <code>help.authStatus</code>. If not signed in, the server was added with the try-it-out address (<code>https://mcp.cookie-compliance.co/mcp</code>) or sign-in was not finished. Sign in: see <a href="/connect/"><code>connect.md</code></a> (raw: <code>https://manual.hu-manity.co/connect.md</code>): the person adds <code>https://mcp.cookie-compliance.co/mcp/account</code> and approves the Cookie Compliance page that opens in their browser. Tell them to read what that page names. Once signed in: <code>account.listApps</code>. If the site&#39;s domain is there, use its AppID; if several match, ask which. If it is missing, <code>account.createApp</code> with the domain. The app is not finished until the person has answered the GDPR starter question (<code>configure-regions</code>).</td>
</tr>
<tr>
<td><strong>1. MCP not connected yet</strong></td>
<td>Give the steps for their app from <a href="/connect/"><code>connect.md</code></a>, with the account address <code>https://mcp.cookie-compliance.co/mcp/account</code>. If the new tools do not appear, ask them to restart the session and say &quot;continue&quot;. Never ask for their password.</td>
</tr>
<tr>
<td><strong>2. Account, no MCP</strong></td>
<td>Ask for the AppID from the dashboard (<strong>Integrations</strong>), or the <strong>Manual Integration</strong> snippet. Give the exact path once. Then run the status check (start.md) yourself. Any 400: show the person the error text. &quot;App does not exist&quot; or &quot;App was deleted&quot;: the AppID is wrong or the app is gone; ask for the current AppID from <strong>Integrations</strong>, and do not publish. Any other 400 (for example &quot;App is not published yet&quot;): a domain added in the dashboard is published automatically, so tell them exactly: click <strong>Publish Now</strong> in the dashboard, then copy the snippet from <strong>Integrations → Manual Integration</strong> (again, if they copied it before publishing).</td>
</tr>
<tr>
<td><strong>3. No account, MCP connected</strong></td>
<td><code>help.startSignup</code> with the site&#39;s <code>domain</code>; give the person the URL. Wait for them to say they are registered, then continue as route 1.</td>
</tr>
<tr>
<td><strong>3. No account, no MCP</strong></td>
<td>Give the <a href="https://app.hu-manity.co/#/register?enable-free=true&amp;discount=JOIN-40D&amp;utm_source=agent-manual&amp;utm_medium=docs&amp;utm_content=skill-install-banner">signup page</a>. Wait for the AppID or the snippet.</td>
</tr>
</tbody></table>
</div>
<p><strong>Localhost:</strong> <code>account.createApp</code> does not accept localhost. Ask the person to add the localhost site in the dashboard, then continue as route 2. An AppID that starts with <code>localhost-</code> is normal.</p>
<p>Without the MCP server you cannot restyle the banner or set regions: tell the person to do those in the dashboard. The region choice is theirs; report it as &quot;owner-managed, not set by me&quot;.</p>
<h2 id="2-get-the-live-snippet">2. Get the live snippet <a class="anchor" href="#2-get-the-live-snippet" aria-label="Link to this section">#</a></h2>
<p><strong>Prefer live HTML. Do not reconstruct it from memory.</strong></p>
<ul>
<li><strong>Cookie Compliance MCP connected:</strong> call <code>install.getSnippet</code> with <code>appID</code>. Paste the returned <code>html</code> <strong>exactly</strong> as given. Follow its <code>placement</code> and <code>warnings</code>. Note <code>widgetVersion</code> (<code>v1</code>, <code>v2</code>, or null): the script URL already matches it. If it refuses the AppID (unpublished or unknown), report that to the owner (unpublished: a domain added in the dashboard is published automatically, so if it still says unpublished, or after later edits, they click <strong>Publish Now</strong> in the dashboard); don&#39;t work around it.</li>
<li><strong>No MCP:</strong> a domain added in the dashboard is published automatically. If the status check still says the app is not published yet, or after later edits, the owner clicks <strong>Publish Now</strong> in the Cookie Compliance dashboard, then copies the snippet from <strong>Integrations → Manual Integration</strong>. If the app was unpublished when they copied the snippet, they copy it again after publishing. Paste the snippet unchanged.</li>
</ul>
<p><strong>Banner engine.</strong> A new app is v2 (<code>/v2/hu-banner.min.js</code>); an existing app keeps the engine it already has. The engine is set per app. Once the app is published, the status check&#39;s <code>WidgetVersion</code> says which, and the snippet&#39;s script URL must match: check and fix it with <a href="/skills/verify-install/"><code>verify-install</code></a> step 0.</p>
<p><strong>Last resort only</strong> (owner has an AppID, cannot reach MCP or dashboard, and asked you to build the tags):</p>
<div class="code"><pre tabindex="0"><code class="language-html">&lt;script&gt;
    var huOptions = { &quot;appID&quot;: &quot;THEIR_APP_ID&quot;, &quot;currentLanguage&quot;: &quot;en&quot;, &quot;blocking&quot;: true, &quot;globalCookie&quot;: false };
&lt;/script&gt;
&lt;script src=&quot;https://cdn.hu-manity.co/v2/hu-banner.min.js&quot; type=&quot;text/javascript&quot; charset=&quot;utf-8&quot;&gt;&lt;/script&gt;
</code></pre></div>
<p>A new app is on <strong>v2</strong>, so the script <code>src</code> is <code>https://cdn.hu-manity.co/v2/hu-banner.min.js</code>. Use <code>https://cdn.hu-manity.co/hu-banner.min.js</code> only when the owner asked for the v1 banner, or the live snippet already has that URL. Take the engine from the status check (<code>verify-install</code> step 0). If the app is not published yet, you cannot know it: stop and get it published first. Guessing the wrong URL puts the site on the wrong engine. Keep <code>blocking: true</code> unless the owner explicitly asks otherwise. Don&#39;t add design or text keys; the published configuration overrides them. A hand-built snippet also omits keys the dashboard may include (<code>blockingEngine</code>, Consent Mode defaults, custom providers) — another reason to prefer live HTML.</p>
<p>If the owner later switches banner engine in the dashboard, a hand-pasted snippet does <strong>not</strong> update by itself. Re-copy and replace it on every page.</p>
<h2 id="3-place-it">3. Place it <a class="anchor" href="#3-place-it" aria-label="Link to this section">#</a></h2>
<ol>
<li>Find the file that renders <code>&lt;head&gt;</code> for <strong>every</strong> page: a shared layout, template, header include, or each HTML file.</li>
<li>Insert the snippet as the <strong>first script</strong> in <code>&lt;head&gt;</code>, above analytics, pixels and any tag-manager container.</li>
<li>No <code>async</code>, <code>defer</code> or <code>type=&quot;module&quot;</code>. Don&#39;t route it through a bundler, a framework script helper, or a tag manager.</li>
<li>Leave existing trackers in place, <strong>below</strong> the snippet. Don&#39;t delete them or add your own consent checks around them.</li>
<li>Remove any other consent banner (see Autopilot above for which ones to ask about first) (a site builder&#39;s own banner stays where its cookbook says so: Wix, Squarespace), and any leftover preview key (<code>previewMode</code>, <code>forceShow</code>, <code>cnPreview</code>). Two banners give conflicting consent, and a preview key stops choices being saved.</li>
</ol>
<p>Platform detail:</p>
<ul>
<li>Plain HTML: <code>references/plain-html.md</code></li>
<li>Next.js: <code>references/nextjs.md</code></li>
<li>Nuxt: <code>references/nuxt.md</code></li>
<li>Astro: <code>references/astro.md</code></li>
<li>Angular: <code>references/angular.md</code></li>
<li>Vite (React or Vue single-page app): <code>references/vite.md</code></li>
<li>SvelteKit: <code>references/sveltekit.md</code></li>
<li>Hugo: <code>references/hugo.md</code></li>
<li>Gatsby: <code>references/gatsby.md</code></li>
<li>Docusaurus: <code>references/docusaurus.md</code></li>
<li>Laravel: <code>references/laravel.md</code></li>
<li>Django: <code>references/django.md</code></li>
<li>Rails: <code>references/rails.md</code></li>
<li>Drupal: <code>references/drupal.md</code></li>
<li>Joomla: <code>references/joomla.md</code></li>
<li>Ghost: <code>references/ghost.md</code></li>
<li>PrestaShop: <code>references/prestashop.md</code></li>
<li>Magento: <code>references/magento.md</code></li>
<li>Wix: <code>references/wix.md</code></li>
<li>Squarespace: <code>references/squarespace.md</code></li>
<li>Webflow: <code>references/webflow.md</code></li>
<li>Framer: <code>references/framer.md</code></li>
<li>Tags and pixels (GA4, Meta Pixel, Hotjar and others): <code>references/trackers.md</code></li>
<li>Shopify: <code>references/shopify.md</code></li>
<li>Google Tag Manager on the page: <code>references/gtm.md</code></li>
<li>WordPress: <code>references/wordpress.md</code> (plugin path — no paste)</li>
</ul>
<p><strong>Stop and ask the owner</strong> if the only way to add scripts is through a tag manager, or if you can&#39;t edit <code>&lt;head&gt;</code> on every page. Say so plainly; don&#39;t invent a workaround.</p>
<h2 id="3b-design-and-regions-mcp-route">3b. Design and regions (MCP route) <a class="anchor" href="#3b-design-and-regions-mcp-route" aria-label="Link to this section">#</a></h2>
<ul>
<li><strong>Design:</strong> follow <a href="/skills/match-site-design/"><code>match-site-design</code></a> with the colours from step 0. On an app you created in this install, with no visitors yet, apply it in Autopilot and tell the person what you chose and how to change it. On any app that existed before you started (for example one found through <code>account.listApps</code>), show before/after and ask first.</li>
<li><strong>Regions:</strong> ask the GDPR starter question once, with the recommended answer first and the Free-plan limits in the same question (<a href="/skills/configure-regions/"><code>configure-regions</code></a>). Apply only after the answer.</li>
</ul>
<h2 id="4-verify-always-including-wordpress">4. Verify (always, including WordPress) <a class="anchor" href="#4-verify-always-including-wordpress" aria-label="Link to this section">#</a></h2>
<p>Load <a href="/skills/verify-install/"><code>../verify-install/SKILL.md</code></a> and follow it. Don&#39;t report the install as done until every check in it passes.</p>
<h2 id="5-report">5. Report <a class="anchor" href="#5-report" aria-label="Link to this section">#</a></h2>
<p>Tell the owner which file(s) you changed, what you chose for them (design, language, anything removed), the GDPR starter answer and what it switched on, plus everything <code>verify-install</code> tells you to report. End with one line on what they can do next: change the design or wording in the dashboard, or add another site.</p>
  </main>
</div>
<footer class="site-footer">
  <p>Cookie Compliance is a product of <a href="https://hu-manity.co">Hu-manity.co</a>.
  Product: <a href="https://cookie-compliance.co/">Cookie Compliance</a> · <a href="https://cookie-compliance.co/mcp/">MCP server</a>.
  Source and contributions: <a href="https://github.com/humanityco/cookie-compliance-agent-manual">github.com/humanityco/cookie-compliance-agent-manual</a>.</p>
</footer>
</body>
</html>
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall