agentleFS
Sign inStart free
y-a-v-ay-a-v-a/skills/attribution/SKILL.md

attribution

Skill0 starsChanged 18 days agoMITView on GitHub

Use this skill when the user wants to add author attribution to a project, for example to a README.md or as a footer on a website. Handles bare invocation (falls back to git config), explicit name/email/website arguments, and free-form placement instructions.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use conversion-tracking, influencer-marketing and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • coreyhaines31Skill

    conversion-tracking

    Set up, audit, verify, or fix website conversion tracking. Use when the conversion is a form submission, booked meeting, chat, phone call, signup, or purchase; when conversions must reach Google Ads, Meta, GA4, LinkedIn, TikTok, or Microsoft Ads; when the work involves GTM tags and dataLayer events, pixels, the Conversions API (CAPI), Enhanced Conversions, server-side tagging, or gclid and fbclid capture; or when the user reports conversion problems like "conversions stopped", "double counting", "spend but no conversions", "GA4 and Google Ads don't match", or an Unverified or Inactive status. Covers lead gen and ecommerce. Always fire on confirmed success, never the submit click; verify a test conversion arrives; diagnose before changing anything; offer free and native paths alongside paid ones and disclose partner tools. For tracking plans and UTMs, see analytics. For attribution models, see attribution. For campaigns and bidding, see ads. For CRM lead-stage design, see revops.

    Also in 3 projects that use this

  • aiunlocked1412Skill

    influencer-marketing

    Influencer marketing AI — brief, pitch, rate evaluation, performance review แบบ data-driven

    Also in 5 projects that use this

  • coreyhaines31Skill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'weekly ads check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'run my SEO,' 'SEO operator,' 'daily SEO agent,' 'run my outbound,' 'AI SDR,' 'reply triage,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 5 projects that use this

  • CesarjoquinSkill

    offers

    When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement.

    Also in 6 projects that use this

  • CesarjoquinSkill

    co-marketing

    When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

    Also in 5 projects that use this

  • YepAPISkill

    link-building

    Outreach tracking, backlink monitoring, DR/DA scoring, and competitor link analysis using YepAPI.

    Also in 3 projects that use this

  • +1 more from coreyhaines31
  • +2 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Add an author attribution to the project.

    line 12
  2. Distinctive:

    No arguments: use the local git configuration for identity.

    line 20
  3. Distinctive:

    Use judgement to split identity from instruction.

    line 34
  4. Distinctive:

    If the arguments contain a placement instruction, follow it.

    line 41
  5. Distinctive:

    Default to a copyright-style credit including the current year:

    line 53
  6. Distinctive:

    Use the actual current year, not a hardcoded one.

    line 60
  7. Distinctive:

    Before writing, check whether the target file already contains an attribution (a copyright line, "Created by", "Author", an existing footer …

    line 71

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Attribution

Add an author attribution to the project.

Arguments

Arguments provided: $ARGUMENTS

Parse the arguments as follows:

  • No arguments: use the local git configuration for identity. Run git config user.name to get the author's name. Do NOT include the email address from git config user.email — emails in public files attract spam scrapers and must only appear when the user explicitly provides one.
  • Identity arguments: arguments may contain any combination of a name (e.g. Vincent Bruijn), an email address, and/or a website URL. Recognize email addresses by the @/domain shape and websites by http(s):// or a bare domain. Anything explicitly provided this way IS meant to be published, including an email address.
  • Instructive arguments: arguments may also (or instead) contain a free-form instruction, e.g. add name to html page footer or put it in CONTRIBUTORS.md. Identity and instruction can be combined, typically separated by a comma: /attribution Vincent Bruijn, add name to html page footer. Use judgement to split identity from instruction.
  • Any identity field not given as an argument and not needed can simply be omitted; only fall back to git config for the name when no name was given at all.

Where to add the attribution

  1. If the arguments contain a placement instruction, follow it. Use the project context to resolve vague targets: "the html page footer" means locate the site's main page/template (e.g. index.html, a layout or footer partial) and add the attribution inside its <footer> — create a minimal <footer> element at the end of <body> if none exists.
  2. Without a placement instruction, add the attribution to README.md in the project root. Place it at the very end of the file as a final section or line, matching the document's existing style. Create README.md if it does not exist, after confirming with the user.

Format

Default to a copyright-style credit including the current year:

  • Markdown: © 2026 Vincent Bruijn · [vincentbruijn.nl](https://www.vincentbruijn.nl)
  • HTML: <p>&copy; 2026 Vincent Bruijn &middot; <a href="https://www.vincentbruijn.nl">vincentbruijn.nl</a></p>

Rules:

  • Use the actual current year, not a hardcoded one.
  • Include only the identity fields that are available: name always; website and email only when provided. Link emails with mailto: in HTML, render the website as a link with the bare domain as link text.
  • Adapt the markup to the target file type (Markdown, HTML, plain text), and match surrounding indentation and style.
  • In Markdown, separate the attribution from preceding content with a horizontal rule (---) unless the file already ends with one.

Existing attribution

Before writing, check whether the target file already contains an attribution (a copyright line, "Created by", "Author", an existing footer credit, etc.). If one exists, do NOT silently replace or duplicate it — show the user what is there and ask whether to replace it, add alongside it, or leave it untouched.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free