agentleFS
Sign inStart free
Starlight-IntelligenceStarlight-Intelligence/starlight-agent-skills/skills/substrate/affiliate-audit/SKILL.md

affiliate-audit

Skill1 starsChanged 4 months agoMITView on GitHub

Map which content mentions paying tools but lacks affiliate links, and which programs to join first. Use when monetizing tool-comparison content, choosing affiliate programs, or auditing a passive-income site's link coverage. Portable and brand-neutral. Trigger phrases: affiliate audit, affiliate link, affiliate program, monetization gap, link coverage, which programs to join, missing affiliate links, audit my content, program catalog.

3 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    If no runtime is wired, the audit can also be run as a reasoning pass: read the catalog, scan the content for tool mentions, …

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

affiliate-audit

Connect the affiliate catalog to a site's content and surface monetization gaps. The monetization loop's engine: catalog × content × traffic → ranked gaps.

Run

node scripts/affiliate-audit.mjs --content=<site>/content --traffic=<traffic.json> --write

Reads the program catalog (data/programs.json or operator equivalent, expecting fields like status and disclosure) + the content dir + optional traffic → ranks (1) programs to join first, (2) posts to add links to. Writes AUDIT.md.

If no runtime is wired, the audit can also be run as a reasoning pass: read the catalog, scan the content for tool mentions, cross-reference against which mentions carry a live program link, and rank the gaps by traffic × payer value.

Strategy rules (apply when recommending or placing links)

  1. Frontier names rank, adjacents pay. The largest foundation-model and generative leaders usually have NO affiliate program. Capture their traffic; monetize via the recurring payers the post recommends.
  2. Highest-ticket recurring tool the operator actually uses, first. Then the recurring spine of subscription payers. Authenticity beats commission rate.
  3. Recurring > one-time. Passive income compounds on subscriptions, not flat bounties.
  4. One disclosure per page. FTC + trust. Use the catalog's disclosure string.
  5. Never link a tool you can't vouch for, and never let a link override the honest pick — say what's actually best, then point to the payer you'd actually buy.
  6. Ignore dead-ends/closed (status in the catalog): frontier tools with no program, programs closed to new affiliates, deprecated tools.

The loop

Audit → join top program → set the program link in the catalog → add link + disclosure to the named posts → re-audit (gap clears).

Compose

  • agentic-income — the operating brain that decides what to do with the gaps this audit surfaces.

How SIS consumes this

The Affiliate stream queen runs this on the weekly monetization-loop cadence. The audit produces recommendations only; placing links and joining programs runs through the queen's gate, and any revenue that flows downstream into settlement is handled by payments-mandate, never here.

Built on SIP — Starlight Intelligence Protocol Substrate: starlightintelligence.org/protocol v1.1.0 Layers used: [file-contract, attestation, sovereignty] Vertical: starlight-agent-skills · portable capability layer

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